MicroMDM

MicroMDM is an open-source, self-hosted MDM server for Apple hardware in enterprise and education. It fits administrators who are comfortable with APIs and command-line operations; organizations seeking a maintained graphical console should consider alternatives. The zero-cost license and broad core controls are compelling, but its v1 maintenance status and recommended migration path materially affect long-term adoption.

Overview

MicroMDM puts device administration behind an API and the mdmctl utility, not a built-in web administrator interface. The API schedules commands, reads device data and manages the server, making it suitable for scripting and repeatable operational workflows. That same design raises the bar for teams whose administrators expect point-and-click policy management.

Deployment is a self-hosted exercise: run the server binary with a server URL, API key, and TLS certificate and key. The API key authenticates requests and protects access. TLS can be handled by MicroMDM or terminated at a load balancer. Apple Push Notification service requires an Apple-issued MDM push certificate. Apple Business Manager Device Enrollment Program integration is supported but optional. A file repository is needed only for custom packages uploaded with mdmctl apply app and pushed through InstallApplication commands.

Key features

• Apple management controls: Automated enrollment, app deployment, FileVault management and remote commands are included at no subscription cost. These cover the central tasks of an Apple fleet, provided the operator can administer them through the command line.
• API-driven administration: Scheduling, device-data access and server management support automation and integration with existing tooling. It is a strength for technically staffed operations, but not a substitute for a graphical dashboard.
• Enrollment and notifications: Apple Business Manager enrollment can streamline corporate provisioning without being mandatory, while Apple Push Notification service connects the server to Apple’s MDM command channel.
• Deployment flexibility: TLS may terminate behind a load balancer, and the package repository is optional when custom application packages are not required. Those choices help fit MicroMDM into an existing infrastructure.
• Migration support: The project points users toward NanoMDM and/or the Nano-suite and says micro2nano tools can migrate existing enrollments transparently. This makes an exit route practical, but also signals that new deployments should be assessed with transition work in mind.

Pricing

Free — free, forever. MicroMDM is free, open source and permissively licensed. There are no seat quotas, paid tiers or trial conversion terms stated for this plan. The trade-off is operational rather than financial: you run and secure the service yourself, including API authentication, certificates, push-certificate integration and any package repository you need.

Platforms

MicroMDM supports iOS and macOS devices. The server is self-hosted and exposes an API, so it belongs in an infrastructure environment rather than as a hosted web-only service.

Who it's for

MicroMDM is a strong fit for enterprise and education teams managing Apple fleets with in-house technical skills, self-hosting requirements or a need to automate MDM actions through an API. It is especially reasonable when a free, permissively licensed server matters more than a polished administrative interface.

It is a poor choice for organizations that need a vendor-maintained product roadmap, a graphical console for routine administration, or minimal server and certificate responsibilities. The project places v1 in maintenance mode, with no new feature work planned and security and bug fixes on an available-effort basis through the end of 2025; its migration recommendation therefore deserves attention before committing a new fleet.

Pros and cons

Pros

• Free and permissively licensed: There is no subscription expense or published device cap.
• Core Apple controls included: Enrollment, applications, FileVault and remote commands address essential fleet operations.
• Automation-friendly API: Scheduling and server-management endpoints suit scripted workflows.
• Self-hosting control: Teams choose their server placement and can terminate TLS at a load balancer.

Cons

• No administrator web interface: Routine work depends on mdmctl and API knowledge.
• Infrastructure burden: Operators must configure URLs, API keys, TLS and Apple push certificates.
• Maintenance uncertainty: v1 has no planned feature development and only available-effort fixes through the stated period.
• Migration may be necessary: The project recommends NanoMDM or the Nano-suite for currently supported, generally maintained deployments.

Alternatives

For a broader shortlist, see Mac Management Software.

• FileWave is the better choice when you need a paid product spanning Apple, Windows, Linux, Android and web management, with a free Community Edition capped at 15 computers, 15 tablets and 15 Chrome devices.
• Fleet suits teams wanting public source code, cross-platform coverage and a free version that is promised to remain free.
• Relution is preferable for a small deployment needing up to five devices free, either in shared cloud or on premises.
• ManageEngine Mobile Device Manager Plus fits organizations wanting a fully featured free edition for up to 25 devices, plus cloud and other deployment options.
• SureAsset is an alternative when asset lifecycle and license tracking, rather than MDM administration, are the priority.
• Jamf Now offers a hosted Apple-focused option with a free three-device tier and a $4.00-per-month plan.
• Mosyle Manager is worth considering for unlimited-device free management configured for either iOS/iPadOS or macOS.
• Munki is a narrower macOS software-management toolkit rather than a full MDM server.

Verdict

Choose MicroMDM if you need a free, open-source Apple MDM server and have the expertise to operate an API-first, self-hosted system. Its core controls and automation potential are substantial. Look elsewhere if you require a graphical administrator experience or a forward-looking maintenance commitment; the project’s migration guidance makes NanoMDM and the Nano-suite important options for a new long-term deployment.