Headwind MDM 7 Rebuilds Open-Source Android Device Management for Self-Hosted Fleets

Headwind MDM released version 7 of its open-source Android device management platform on October 13, 2026, and the headline is not a feature list. It is the foundation. The server now runs on OpenJDK 21, requires Tomcat 10 or later, and the entire web console has been rebuilt in Angular, a sweeping modernization aimed squarely at the organizations that manage Android fleets on their own servers, including closed networks with no internet access.

Version 7.03.1 is available now for self-hosted installations of the Community, Premium, and Enterprise editions. It follows a beta program that began in August 2026, and it carries an implicit message that self-hosters should appreciate: device management is infrastructure, and infrastructure you cannot update is infrastructure you cannot trust.

What actually changed in version 7

The biggest shift is the stack. The web console has been rebuilt in Angular and redesigned around current admin console practices, replacing whatever legacy framework the project had accumulated over years of service. Underneath, the server moves to Java with OpenJDK 21 and requires Tomcat 10 or later, with the migration tooling installing Tomcat 11. The recommended platform is Ubuntu 24.04 LTS, the long-term-support release most self-hosters already run.

The console also gains live backend alerts. Backend events now travel over WebSockets and surface instantly as pop-up notifications in the admin interface, so an administrator watching the dashboard sees device alerts as they happen rather than on the next poll or refresh. It is the kind of small operational improvement that matters when you manage hundreds of handsets across warehouses, clinics, or field crews.

There is also a quiet efficiency win. Most of the libraries Headwind MDM uses now deploy to the shared Tomcat lib directory instead of being bundled inside the web application archive. That separation significantly reduces the size of each web application update, which makes upgrades faster and cheaper to push, a real consideration for air-gapped deployments where every byte crosses the gap by hand.

The plugin rework is the real story

The change most likely to reshape the project over time is the reworked plugin system. Plugins can now be developed and packaged as standalone WAR files, which means developers no longer have to rebuild the entire project to ship a custom plugin. Previously, extending the platform meant wrestling with the full codebase. Now a plugin is a self-contained artifact you drop in.

Two policy decisions make this interesting. First, plugins built on the free Community Edition can be distributed to Enterprise customers, which lowers the barrier for consultants and in-house teams to build once and deploy everywhere. Second, plugin updates no longer depend on the core product release cycle, so a custom integration can ship on its own schedule instead of waiting for the next platform version.

Headwind MDM 7 treats plugins as first-class citizens: standalone WAR files, their own release cadence, and no full-project rebuild to ship an extension.

That is how ecosystems form. An open-source MDM platform with a frictionless plugin model becomes a base that systems integrators can build businesses on, which in turn funds more development. The Apache 2.0 license on the new server repository keeps the terms permissive for exactly that kind of commercial participation.

Why self-hosted MDM still matters

Mobile device management is one of the software categories most naturally suited to self-hosting, and the least forgiving of vendor dependence. An MDM server can wipe phones, install applications silently, track device locations, collect logs, and read photos from managed devices. In the Enterprise edition, Headwind MDM does all of that, plus remote control and screen mirroring, kiosk mode, and URL filtering. That is a great deal of power to hand to a vendor cloud, especially for the hospitals, government agencies, and banks the platform targets.

Running the control plane on your own infrastructure answers the question before it is asked. Devices check in with a server inside the organization, policies are enforced locally, and the telemetry stays within the network. Headwind MDM explicitly supports closed, air-gapped networks, which matters for industrial sites, defense-adjacent operations, and regions where external connectivity is unreliable or politically complicated. When the announcement lists air-gapped operation as a design goal rather than an afterthought, that tells you who this release is for.

There is also a cost and sovereignty angle that resonates with the broader self-hosting movement. Commercial MDM suites are typically priced per device per month, and costs scale brutally with fleet size. An open-source, self-hosted platform replaces that subscription with commodity hardware and your own maintenance labor. The trade is explicit: you own the backups, the updates, and the security posture. For organizations that already run their own infrastructure, that trade usually wins.

What to know before you upgrade

If you are running a legacy 5.x installation, migration is handled by a migrate.sh script bundled with the new installer, which installs Tomcat 11 and updates the web console and shell scripts. The Community Edition installer is available from the project website, and the source code is published on GitHub under the Apache License 2.0, so the entire upgrade path is inspectable.

The vendor recommends taking a snapshot of the server before upgrading, and that advice should be taken literally. Major stack migrations, Java 8 or 11 to 21, a new web console, shared library layout, are exactly the kind of change that can surprise you at 2 a.m. Test the migration in a staging environment first, especially if custom plugins or integrations depend on the old console.

One honest caveat: the announcement is a company release, and independent benchmarks of the new console performance or migration success rates have not been published yet. The technical claims are verifiable, the stack versions, the WAR packaging, the WebSocket alerts, and the source is open for anyone to audit. But early adopters should treat the first point releases of a rebuilt platform with the usual caution: back up, stage, and watch the logs.

Still, for the self-hosted crowd, Headwind MDM 7 is a welcome sign. An open-source project modernizing its foundations, lowering the cost of extension, and doubling down on air-gapped deployment is exactly the kind of maintenance the open infrastructure world depends on. The devices in your pocket deserve a management plane you can actually inspect.