Fleet turns year-old Omarchy support into an enterprise management push
DHH promoted Fleet's dedicated Omarchy integration, though several Linux controls still stop short of macOS and Windows parity.
By Ryan Merket · Published
Primary source: X - @dhh
Why it matters
Omarchy's path into companies depends on management software that preserves developer choice while satisfying security controls. Fleet has the distribution channel, but its documented Linux gaps leave room for deeper integration.
David Heinemeier Hansson (@dhh), the creator of Omarchy, promoted Fleet's device-management integration on X on September 15th, giving the enterprise software vendor a direct endorsement as it pitches companies on letting developers run the Arch-based Linux distribution at work.
"Need to manage a whole fleet of machines with Omarchy? Then Fleet's MDM solution is fully integrated," Hansson wrote. Fleet's dedicated Omarchy page says administrators can inventory software, execute scripts, remotely lock or wipe computers, set security policies and manage Omarchy machines alongside macOS and Windows endpoints.
Hansson created Ruby on Rails and co-owns 37signals, where the technical staff has switched to Omarchy. He built the distribution around an opinionated, preconfigured Linux desktop designed for developers and AI agents. Omarchy's website displayed more than 1.1 million ISO downloads during its first year and over 41,000 GitHub stars as of September 16th, figures reported by the project itself.
That growth creates the problem Fleet is selling against. A developer can install Omarchy without waiting for an IT department to approve a new operating system, but companies still need to know which packages are installed, whether security policies pass and what happens when a laptop is lost or an employee leaves.
The integration predates the endorsement
Fleet's Omarchy support did not ship this week. Fleet 4.75.0 added support for Arch Linux hosts on October 17th, 2025, including software inventory ingestion and the ability to generate native Arch installation packages for Fleet's agent. Fleet's release notes explicitly presented that work as support for Arch Linux and Omarchy.
The September endorsement therefore marks a distribution and positioning push around an integration that has existed for nearly eleven months. Fleet has packaged the underlying Arch support into a page written for companies considering Omarchy as an employee operating system, complete with Hansson quotes and links to Fleet's commercial plans.
Fleet grew out of osquery, the open-source endpoint instrumentation project created at Facebook in 2014 by Fleet co-founder Zach Wasserman, Mike Arpaia and other engineers. Wasserman later helped create the original Fleet server at Kolide before partnering with Mike McNeil to establish Fleet Device Management as an independent company in 2020. That lineage explains Fleet's approach to Linux: deep device visibility through an open-source agent, with management actions layered on through policies, scripts, APIs and GitOps.
Linux management still has edges
Fleet and Hansson use "MDM" as the umbrella term, but Fleet does not control Linux through the native management protocols used by Apple and Microsoft. Its lock and wipe documentation says Linux actions run scripts, while macOS, Windows, iOS and iPadOS wipes use MDM commands.
Fleet's Omarchy support also has documented limits. Its current compatibility guide says disk-encryption enforcement is available only for Ubuntu, Kubuntu and Fedora among Linux distributions. Fleet Desktop, the end-user tray application used for self-service workflows and management notices, is officially supported on GNOME and KDE Plasma; Omarchy uses a different desktop stack.
Vulnerability reporting is another gap. Fleet can inventory pacman packages on Arch and Omarchy and compare versions with the National Vulnerability Database, but Fleet's vulnerability documentation says the platform does not detect kernel vulnerabilities for either distribution. It also warns that version-only package matching can produce false positives because the database may miss security fixes backported by a distribution.
Those constraints make Fleet useful for inventory, policy checks, software deployment, scripts and incident response without making Omarchy identical to a managed Mac or Windows fleet. The dedicated page's promise of managing Omarchy "like" those platforms describes a unified administrative console, rather than feature-for-feature parity.
The commercial incentive is straightforward. Fleet's public pricing page lists a free self-hosted tier and a Premium plan at $7 per host each month. Application management, remediation, maintenance windows, remote lock and wipe, targeted device groups and managed cloud deployment sit in the paid column.
Hansson's endorsement gives Fleet access to an expanding population of developers who want Omarchy on work machines. Fleet gives Hansson a practical answer when security and IT teams ask how those machines can enter a corporate network. The remaining work lies in closing the Linux-specific control gaps before "fully integrated" means the same thing to an auditor that it does in an X post.