# What is Peig?

Peig is a **device-bound access security platform**. It ensures that access to your business applications — whether SaaS, private cloud, or on personal devices — is tied to a specific, authorised device.

Instead of proving who you are with a username and password, your device proves it for you. Access is cryptographically bound to the device itself. Even if someone steals your credentials, they cannot get in from an unregistered device.

***

## The problem Peig solves

Most businesses secure access with passwords — and increasingly with MFA on top. But this model has a fundamental weakness: **credentials can be stolen, shared, or phished** without ever touching a device.

As teams have moved to remote and hybrid work, the attack surface has grown. Employees use personal laptops, phones, and tablets to access company tools. Rolling out traditional device management for every employee and contractor is expensive, slow, and often impractical.

Peig solves this by shifting the security anchor from credentials to devices. When access is bound to a device, stolen passwords become useless. There is nothing to phish, nothing to brute-force, and nothing to leak.

***

## What Peig is not

{% hint style="info" %}
Understanding what Peig is **not** is just as important as understanding what it is.
{% endhint %}

**Not an MDM tool.**\
Peig does not manage devices, push software, or give IT visibility into device contents. It only verifies that an access request comes from a registered, authorised device. See [Why Not MDM?](/welcome-to-peig-documentation/what-is-peig/why-not-mdm.md) for a full comparison.

**Not just passwordless.**\
Most passwordless solutions still rely on usernames and shared secrets in some form. Peig eliminates both. The device *is* the credential — bound cryptographically, not transferable.

**Not a bolt-on to your existing SSO.**\
Peig does not sit on top of Okta or Azure AD as an add-on layer. It replaces the credential-based model at the access layer itself.

***

## How it works in practice

For **end users**, Peig is an app they download once. After a simple one-time setup, they access company resources through the Peig workspace — no passwords, no MFA codes, no friction.

For **administrators**, Peig provides a central dashboard to approve devices, manage user access, and review activity — without needing to manage the devices themselves.

{% hint style="success" %}
Ready to go deeper? See [Key Concepts](/welcome-to-peig-documentation/what-is-peig/key-concepts.md) for how device-bound access works under the hood, or jump straight to a [Deployment Guide](/welcome-to-peig-documentation/deployment-guides.md) to get started.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.peig.io/welcome-to-peig-documentation/what-is-peig.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.