fleetdm/fleet

Fleet is worth a serious look if your team already manages endpoints through a patchwork of scripts and wants one self-hostable system that covers macOS, Windows, Linux and mobile devices, with an API and GitOps path rather than a GUI-only workflow. It is primarily an operations platform, not a developer tool.

The problem

Someone on IT or security wants to answer a simple question: which machines are missing patches, running unapproved software, or failing a compliance baseline? Today that often means combining several agents, spreadsheets and one-off scripts, then asking the same questions again next month. Fleet replaces that loop with a central server that collects host facts and lets you change device state — enforce MDM profiles, deploy software, run scripts, check benchmarks — from one place. The result is a recurring inventory-and-remediation workflow rather than a snapshot of unknown age.

What's different

Fleet builds on osquery for host visibility and nanoMDM for Apple MDM, wrapping them in one server with a REST API, webhooks, YAML configuration and the fleetctl CLI. For teams practicing GitOps, the configuration-as-code path means device policies and settings can live in version control instead of clicking through an admin console; GUI, API and CLI are all documented access routes. The README also stresses modularity: you can adopt MDM without the security features, or turn features off, which matters when only part of a team is ready to migrate.

A second differentiator is breadth. The README claims production use across Linux, macOS, Windows, Chromebooks, iOS and Android, plus cloud and container targets, with "first-class" Linux support rather than Linux as an afterthought. For mixed environments this reduces the number of consoles an admin has to learn — but it also means the surface area of configuration and permissions is large, and the tool is only as useful as the policies you write.

Who should try it

Good fit: an IT or security team with dozens to thousands of devices across more than one OS, already comfortable with APIs or configuration files, that wants device management it can self-host and inspect. It is also a reasonable fit for organizations that need audit evidence and CIS benchmark reporting for macOS and Windows without buying into a fully closed suite.

Poor fit: a single-user desktop or a small team that just wants to install apps on one laptop; the server, agent, configuration and policy work would outweigh the benefit. Teams that need no self-hosting at all may prefer a hosted path — Fleet's pricing and contact pages exist for trying it or talking to maintainers before operating it yourself.

Requirements and limitations

Adoption means running a server and an agent on every managed host, so you own upgrades, backups and access control for that infrastructure. The README lists separate binaries/download paths for the CLI and server, and the docs are the place to check platform prerequisites and MDM enrollment requirements; Apple MDM in particular brings certificate and push-notification setup that is not a one-file install. The free version is MIT-licensed, but the license file distinguishes paid features, so feature scope should be checked against your needs rather than assumed from "open source."

Ongoing upkeep is the bigger cost: policies, scripts and YAML configuration need review as your fleet and OS versions change, and integrations with tools like Splunk, Snowflake or ticketing systems only help if someone maintains them. The README also positions Fleet's data collection as limited to management and security needs; verify that its documented tables meet your compliance requirements before promising audit evidence.

HotRepo's take

HotRepo only has one dated observation: 7,062 stars on 2026-10-28, appearing on the daily trending board with +8 stars that day. That single snapshot cannot establish whether interest is growing, flat or fading, so treat the repository's 2020 creation date and the README's production claims as context rather than proof of current momentum. The specific thing to check before committing is the documented MDM enrollment and upgrade path for your least common OS — if that story is thin, the self-hosted promise gets expensive fast. Otherwise this is a credible candidate for teams already planning a cross-platform device management migration project README, configuration docs, CLI download.