
NanoMDM
Mobile Device Management
Alternative Vendors
Commercial Alternatives
Key Features
Apple MDM protocol core
Handles device check-ins, the MDM command queue and APNs pushes for macOS, iOS and iPadOS enrollments, including ADE (DEP) enrollments.
API-driven commands
HTTP API to queue raw Plist MDM commands and send pushes, with multi-command targeting of many enrollments at once.
Pluggable storage
Enrollment and command data in a built-in file key-value store, MySQL or PostgreSQL, so the server itself keeps almost no state and scales horizontally.
Multiple APNs topics
One server can serve several APNs push topics, which makes multi-tenant setups possible.
MicroMDM-compatible webhook
Sends device responses to a webhook in the same format as MicroMDM, so existing MicroMDM integrations keep working.
Migration endpoint
Moves MDM enrollments between storage backends or from supported MDM servers; micro2nano helps migrate from MicroMDM.
Pros and Cons
Pros
Free and open source
MIT licensed with no license cost; source on GitHub.
Actively maintained successor
The MicroMDM maintainers name NanoMDM and the Nano suite as the supported path after MicroMDM v1 support ended in 2025.
Scales horizontally
Minimal local state with MySQL or PostgreSQL storage lets you run several instances behind a load balancer.
Composable
Combine with NanoDEP, NanoCMD, KMFDDM or NanoHUB to add only the pieces you need.
Easy migration from MicroMDM
MicroMDM-compatible webhook, a migration endpoint and the micro2nano tools.
Cons
Not a complete MDM
You must supply SCEP, TLS termination and enrollment profiles; there is no VPP and no ADE (DEP) API access.
No web UI
Management is through the HTTP API and raw Plist commands; there is no graphical console.
Apple only
Manages macOS, iOS and iPadOS devices only.
Needs engineering skills
Best suited to teams that build their own tooling; no commercial support.
Feature Comparison
Comments
No reviews yet. Be the first to share your experience with NanoMDM.
Frequently Asked Questions
/vendor/nanomdm