Omacom Foundation's $10M: who holds your tool's trademark?

David Heinemeier Hansson launched the Omacom Foundation with $8 million behind Omarchy, his opinionated Arch Linux respin, and within a few days the total reached $10 million from ten founding patrons at $1 million each. The headline is the guest list. The line worth reading twice is the mandate: the foundation will hold the trademarks. That is the sentence that decides who controls an open-source project, and almost nobody checks it before adopting one.

What actually happened

Per the foundation's announcement on August 21, the eight initial patrons each contributed $1 million: Tobi Lütke (Shopify), Patrick Collison (Stripe), Michael Dell, Jack Dorsey (Block), Matthew Prince (Cloudflare), Brendan Iribe (Sesame and Oculus cofounder), Jason Fried (37signals), and Hansson himself. On August 24 the foundation added two more — Drew Houston of Dropbox and Peter Steinberger, creator of OpenClaw — taking it to $10 million.

The stated job: hold the trademarks, fund the infrastructure, promote the work, and support the open-source projects and developers Omarchy depends on. Omacom also covers Omakub, the Ubuntu-based sibling project.

Omarchy itself, as The Register describes it, is a keyboard-driven Arch respin built on the Hyprland tiling compositor, first released in June 2025, shipping preconfigured with a large pile of developer and desktop software. The Register also notes it has drawn security criticism from reviewers over its defaults and its departure from established desktop conventions. Fair on both counts — a batteries-included distro makes choices on your behalf, and those choices are worth auditing before you put one on a work machine.

Why trademark ownership matters for your tool choices

Permissive licenses get all the attention. MIT and Apache 2.0 mean nobody can revoke your right to use the code — we've made that argument here before. But a license governs the code, not the name, and the name is where the leverage lives.

Whoever owns the trademark controls what can be called the thing. They decide who ships an official build, who runs the package repository, who owns the domain your install script curls from, and who gets to say a fork isn't the real project. Plenty of open-source blowups that read as license disputes were actually trademark disputes — the code stayed free, and the community still had to rename everything and rebuild its distribution channel from scratch.

So when you're evaluating an open-source dependency for real work, three questions past the license file:

Who holds the mark, and is it a person or an entity? A foundation with named patrons is more durable than a maintainer's personal registration, because it survives the maintainer changing jobs, changing minds, or getting acquired.

Who pays for the infrastructure? The package mirror, the CI, the signing keys. Unfunded infrastructure is the actual single point of failure in most open-source supply chains, and it fails quietly.

What's your exit if the name goes away? For a library, usually nothing — vendor it and move on. For a distro, an OS, or anything your build pipeline pulls from at runtime, pin your versions, mirror your packages, and know which upstream you'd track if the project split.

Ten founders putting $1 million each behind a Linux distribution is unusual. Ten founders putting it behind a trademark and infrastructure entity, rather than a company, is the part that generalizes. Funded governance is a feature you can evaluate. Start evaluating it.

Sources: Omacom Foundation announcement, Omarchy News, The Register.