Fleetdm

Limitations

• Operational maintenance overhead: Operating the control plane requires running external MySQL 8.0 databases, Redis clusters for live query execution, and TLS proxies.
• Commercial feature gating: Zero-touch hardware enrollment, SCIM-based IdP group syncing, conditional access rules, and automated disk encryption key escrow require a paid Fleet Premium subscription.
• Maturing mobile management: While desktop coverage is extensive, managing corporate-owned Android devices and zero-touch mobile enrollment remains under active development.
• Immutable Linux packaging: Because the fleetd agent bundles its own osquery binary, deploying on immutable systems like NixOS requires custom packaging workarounds.

Who should use it

• Platform engineers managing developer workstations who want to review device configurations and policies in pull requests before deployment.
• Security and site reliability teams that need ad-hoc SQL queries across hybrid environments to investigate vulnerabilities across macOS, Windows, and Linux hosts.
• Engineering organizations with strong privacy standards that need transparent, auditable telemetry collection instead of closed-source monitoring agents.

FAQ

Is Fleetdm free for commercial use? The core self-hosted server and agent are open source under Apache-2.0, allowing commercial deployment without licensing costs. Enterprise features like zero-touch enrollment and automated IdP syncing require a paid Fleet Premium license.

How does Fleetdm differ from traditional tools like Jamf Pro? Legacy management suites rely on proprietary web consoles focused on single operating systems, whereas Fleetdm provides cross-platform management powered by GitOps automation and SQL-based osquery telemetry.

What infrastructure is required to self-host Fleetdm? A self-hosted deployment requires running the Go server binary alongside a MySQL 8.0 database for configuration storage and a Redis instance for real-time query streaming.

Verdict

Fleetdm fits engineering teams that want to manage endpoint compliance through version-controlled manifests rather than interactive administrative consoles. If your team lacks the operational capacity to maintain dedicated MySQL and Redis instances or needs out-of-the-box mobile provisioning, a managed proprietary solution is simpler to operate. Active development with recent 2026 commits and an Apache-2.0 license for the core platform give engineering organizations full control over their fleet telemetry without vendor lock-in.