31 AUG 2026 — Ten people have each written a US$1m cheque to the Omacom Foundation, the nonprofit behind the Omarchy Linux desktop, taking it to US$10m. None of that money is a corporate commitment, and none of it is for building the distribution.
Who paid, and what the foundation is for
The first eight donors were Shopify's Tobi Lütke, Stripe's Patrick Collison, Michael Dell, Block chairman Jack Dorsey, Cloudflare's Matthew Prince, Oculus co-founder Brendan Iribe, 37signals chief executive Jason Fried and David Heinemeier Hansson, who created Omarchy. Dropbox co-founder Drew Houston and OpenClaw's Peter Steinberger joined afterwards, taking the total to ten patrons and US$10m.
The foundation's stated remit is narrow: hold the trademarks, cover infrastructure costs, and support the open-source projects and developers that Omarchy depends on.
Individuals, not companies
Headlines describing this as backing from Shopify, Stripe, Dell and Cloudflare are compressing something that matters. Those companies have not funded anything. Ten wealthy individuals, most of whom happen to run technology companies, have made personal donations.
The difference is about what happens next rather than about the money now. Corporate open-source funding survives the person who authorised it, sits in a budget line, and comes with procurement expectations attached. Personal patronage does not renew automatically, is not on anyone's roadmap, and depends on continued individual enthusiasm.
Neither model is better. Corporate funding brings influence with it, which is the criticism usually made of foundations dominated by their largest members. Personal patronage avoids that and buys less certainty. A US$10m headline sounds like institutional backing, and in this case it is not.
What US$10m actually buys
Against the stated remit, this is a modest and sensible amount, not a transformative one.
Trademark holding is cheap and mostly a governance device: it puts the name in a legal entity rather than in a person, which is what protects a project from its founder's later decisions. Infrastructure — build servers, mirrors, package hosting for an Arch respin — is real but not expensive at this scale.
The third item is where the money goes and it is the most interesting. Supporting the upstream projects Omarchy depends on means paying people who work on Hyprland, on Arch packaging, and on the long tail of components a desktop needs. Omarchy is a curated assembly of other people's software, and a foundation that funds the software it assembles is behaving well by the standards of a field where downstream projects usually take without giving.
So the accurate description is a fund of that size supporting upstream maintainers, not a war chest for building a Linux desktop. US$10m does not pay a distribution engineering team for long. Directed at the specific projects one distribution depends on, it is a substantial injection.
The security objection deserves a straight answer
The criticism quoted alongside this news is blunt: do not use Omarchy if you care about security. It is a point worth engaging with, not just repeating or dismissing.
The substance is structural rather than a claim about a specific flaw. Omarchy is an opinionated respin installed by a script, layered on Arch, which is a rolling release without the staged testing of a fixed-release distribution. Version 4.0.1 shipped in mid-August as a security fix, which is the system working. The concern is that a curated layer on top of a rolling base adds a maintainer whose review capacity is the bottleneck for everything in that layer.
That is a fair description of the trade-off, and one that every derivative distribution makes. Whether it is acceptable depends on the use: for a developer workstation it is one thing, for a machine holding production credentials it is another. The foundation's money is relevant here in a way nobody has connected — funding upstream maintainers is the only structural answer to a review-capacity objection.
The pattern this belongs to
Two other open-source governance stories this month point the same way, and together they describe a shift.
We reported that AWS bought DuckDB's maintainers rather than DuckDB: the licence stayed open while the people deciding what gets written moved onto a payroll. And Debian's resolution on generative AI put responsibility on individual contributors while declining to police them, a policy that assumes contributors remain individuals.
Omacom is the third variant. In each case the licence is not the thing that changed and is not the thing worth watching. The meaningful change is about who pays the people, and open-source governance conversations are still largely conducted in the vocabulary of licences.
Why a regional developer might care
Desktop Linux adoption in Southeast Asia is driven by cost and by hardware longevity more than by ideology, and this is where an opinionated distribution has a real argument.
A curated, keyboard-driven, tiling desktop on modest hardware is a good fit for a developer working on a machine that would struggle with a current commercial operating system. The counterweight is that Arch expects a user who can recover it, and rolling releases assume bandwidth that is not free everywhere.
The benefit that extends beyond Omarchy's own users is the upstream funding. Money reaching Hyprland and Arch packaging maintainers improves the components that many other distributions ship, including the ones that regional users actually run.
View author profile → · Editorial policy
