Mobile device management
Built, not provenAndroid Enterprise through the Android Management API, and Apple MDM through a self-hosted NanoMDM stack, with per-organisation push certificates.
What it does
- Android Enterprise enrolment and policy, with a platform-owned service account so each client does not need its own Google project.
- Apple MDM: push certificates requested from inside Atlas, with the private key generated and held encrypted so it cannot be lost.
- Lost Mode, OS update enforcement, and Activation Lock bypass codes escrowed while a device is still enrolled.
- Non-compliance split into what a technician can fix and what is structural, so a policy that cannot apply to a device says so.
What it does not do
- ONE DEVICE has enrolled in production. The Android path has a granted 500-device quota and the Apple path is built end to end, but neither has met a real fleet.
- The Apple side needs infrastructure stood up per deployment: DNS, a SCEP CA and the MDM sidecars. It is not a checkbox.
- Apple’s push certificate must be RENEWED, never re-created. A new certificate carries a new Topic and silently orphans every enrolled device; Atlas warns, it cannot undo it.
What it replaces
- A separate MDM subscription
Included in the single per-user price. No per-module or per-endpoint add-ons.