# Why not MDM

MDM (Mobile Device Management) is designed to manage devices — push software, enforce configurations, and maintain control over hardware. Peig is designed to secure access. That is an important distinction, and it drives very different deployment experiences.

## When MDM is the right choice

MDM makes sense when you need to:

* Manage **corporate-owned hardware** — enforce OS versions, push software, remotely wipe devices
* Maintain **compliance over the device itself** — disk encryption, patch status, configuration baselines
* Run **highly regulated environments** — healthcare, financial services, government
* Centrally manage a **large fleet** of company-issued devices

## When Peig is a better fit

Peig is purpose-built for situations where MDM is too heavy or simply does not apply:

* Your team uses **personal or mixed devices** (BYOD) and MDM enrollment is impractical or unwelcome
* You need to **onboard contractors or external contributors** quickly, without corporate device enrollment
* You are working toward **SOC 2 compliance** and need demonstrable access controls without a full MDM rollout
* You are a **cloud-first company** where device management infrastructure does not exist

{% hint style="info" %}
The key difference: Peig secures **access**, not devices. It does not inspect the device, push software to it, or give IT any visibility into the device itself. It only verifies that the access request is coming from a registered, authorised device.
{% endhint %}

## When Peig and MDM work together

Peig and MDM are not mutually exclusive. In environments where MDM is already deployed, Peig complements it:

* **MDM** manages the corporate device fleet and enforces device-level policies
* **Peig** handles access layer authentication — ensuring access to applications is device-bound and passwordless

This is particularly relevant for **Microsoft Entra Joined** environments, where Peig can act as the Web Sign-In identity provider for managed Windows devices — with or without Windows Hello for Business enabled.

## Summary

|                                   | MDM       | Peig |
| --------------------------------- | --------- | ---- |
| Manages device configuration      | ✅         | ❌    |
| Requires corporate-owned devices  | Often     | ❌    |
| Works on personal / BYOD devices  | ❌         | ✅    |
| Secures application access        | Partially | ✅    |
| Eliminates passwords              | ❌         | ✅    |
| Deploys without IT infrastructure | ❌         | ✅    |


---

# 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/why-not-mdm.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.