Ten days after Ruby on Rails creator David Heinemeier Hansson incorporated the Omacom Foundation with an $8 million pledge from eight tech-industry heavyweights, the nonprofit has added its first two corporate sponsors — password manager 1Password and software company 37signals — and brought total commitments to $12.6 million across fourteen patron agreements. The additions, announced today on August 31, also include two new individual patrons identified only as Brian and Yunjie, each pledging $1 million.

The foundation exists to sustain Omarchy, an opinionated Arch Linux distribution that Hansson — known professionally as DHH — built around the Hyprland tiling compositor and the Quickshell desktop toolkit. What makes today’s announcement structurally significant is not the dollar total but what the foundation has already done with the money it raised last week: deployed long-term, unconditional funding into two upstream open-source projects — Hyprland and Quickshell — that previously relied on individual donations and small subscriptions to keep their sole developers working.

From $8M to $12.6M in Ten Days

When Hansson announced the Omacom Foundation on August 21, the initial patron roster included Shopify CEO Tobi Lütke, Stripe CEO Patrick Collison, Dell Technologies CEO Michael Dell, Block Chairman Jack Dorsey, Cloudflare CEO Matthew Prince, Oculus co-founder Brendan Iribe, 37signals CEO Jason Fried, and Hansson himself — eight patrons at $1 million each.

Three days later, Dropbox co-founder and co-CEO Drew Houston and Peter Steinberger, creator of the AI coding tool OpenClaw, joined as Founding Patrons at $1 million each, bringing the total to $10 million. Today’s announcement added Brian and Yunjie as individual patrons on the same terms, while 1Password and 37signals each pledged $100,000 per year for three years — a $600,000 combined corporate commitment that takes the foundation to $12.6 million total.

Hansson drew a clear line around what corporate patronage does and does not buy. “Corporate money and individual money all buy the same thing: recognition for being part of the mission,” he wrote. “There’s no quid pro quo here.” He added that Omarchy’s technical decisions would always be driven by what makes for “the very best malleable OS in the world” — a principle he anchors explicitly in his own preferences before anyone else’s.

What the Foundation Does — and Why the Upstream Funding Matters

The Omacom Foundation’s stated mandate covers four pillars: holding the Omarchy trademark, funding infrastructure, promoting adoption, and supporting the open-source projects and developers Omarchy depends on. That last pillar is where the foundation has been most concrete.

On the same day it incorporated, the foundation announced an exclusive three-year Hyprland sponsorship. The deal allows Vaxry, the Polish developer who created Hyprland, to focus entirely on compositor development without needing commercial contracts or separate fundraising. The sponsorship takes effect October 10, with an option to extend for two additional years.

As part of that arrangement, Hyprland’s existing Hyprperks paid-subscription tier — which previously offered early access and other perks for roughly €5 (approximately $6) per month — will be discontinued, and everything previously gated for free will be released to the public. Personal donations to Hyprland will still be accepted.

The foundation has also announced a Quickshell three-year premier sponsorship under a separate term. Its developer, who goes by “outfoxxed,” built the component that Omarchy Quattro used to replace eight separate desktop utilities with a single long-running process — a structural change that propagates theme changes across the terminal, editor, notifications, and system monitor in unison.

How Quickshell’s Single-Process Shell Changes the Architecture

For technically literate readers, the Quickshell consolidation in Omarchy Quattro — released August 14 — is the most interesting engineering development the foundation is now underwriting.

In Omarchy’s previous 3.x releases, the desktop was assembled from eight separate programs replaced in Quattro: Waybar (status bar), Walker (application launcher), Mako (notifications), SwayOSD (on-screen displays), hyprlock (lock screen), hypridle (idle management), swaybg (wallpaper), and polkit-gnome (authentication dialogs). Each had its own configuration format, theming system, and no shared state with the others. Changing an accent color meant touching each of them and hoping they agreed.

Quickshell replaces all eight with a single long-running process. It is built on Qt6/QtQuick — a GPU-accelerated scene-graph framework whose QML configuration language describes the UI declaratively, as a set of relationships rather than a sequence of instructions. The practical consequence: status updates are event-driven rather than polled; a notification popup survives a shell restart; saving any file in the plugin directory hot-reloads that plugin without restarting the entire shell. DHH reports the shell runs under 300 MB of combined runtime memory.

The architectural bet is that this single-process approach, built on Quickshell’s plugin system, makes the desktop itself programmable rather than merely configurable. Over 1,000 plugins created in the week following Quattro’s release — a figure the foundation cited when announcing the Quickshell sponsorship.

AI Agents as OS Citizens, Not Application Add-ons

Alongside the shell rewrite, Omarchy Quattro introduced a design philosophy that no mainstream Linux distribution has previously implemented at this scale: treating AI coding agents as first-class operating-system citizens rather than applications you happen to run.

The status bar displays a live widget tracking Claude Code weekly usage. When a process crashes, the OS surfaces a notification offering to route the core dump to the user’s default agent, using a shipped diagnose-crash skill. The system includes an agent skill symlinked into ~/.claude/skills, ~/.codex/skills, and a generic ~/.agents/skills, teaching agents how to reconfigure the machine they are running on. Nine agent CLIs — including Claude Code, OpenAI Codex, OpenCode, Gemini CLI, GitHub Copilot CLI, and Grok — come pre-wired as lazy-loaded launchers.

Omarchy Quattro also ships Herdr, a Rust-based terminal multiplexer developed externally by the herdrdev team under an Apache 2.0 license, which Omarchy adopted. Where tmux can split a terminal into panes but cannot tell you whether the agent in each pane is idle, actively working, blocked waiting for approval, or finished, Herdr surfaces that state as a first-class property per pane — solving a real operational problem for anyone running three or four coding agents simultaneously.

Why 1Password and 37signals Joined

For 1Password, the Distinguished Corporate Patronage formalizes a pre-existing integration. The password manager has shipped inside Omarchy since the project’s earliest days, and was previously bundled in Omakub, Hansson’s earlier Ubuntu-based setup script. Hansson describes 1Password as the first application he installs on any new machine — before configuring agents or logging into any services — and credits it as central to his “no backup, no cry” workflow of treating every machine as disposable.

37signals’ involvement is more deeply embedded still. The company — which makes Basecamp and HEY, and co-employs Hansson — has already migrated its entire technical team to Omarchy. Jason Fried, 37signals’ CEO, was one of the original eight patrons at $1 million. The corporate patronage formalizes financial support that 37signals had been providing informally throughout Omarchy’s development and makes it public on the same terms as every other Distinguished Corporate Patron.

Is It Secure? What Developers Should Know Before Adopting

The Omacom Foundation’s rapid fundraising has amplified scrutiny that was already building around Omarchy’s security posture — and developers evaluating it as a primary workstation OS should read that scrutiny carefully before committing.

When Omarchy Quattro shipped on August 14, it contained bash injection and arbitrary code execution vulnerabilities via video titles and notifications, which were addressed in a v4.0.1 security patch shortly after. A blog post titled “Merchants of Insecurity,” linked by The Register, opens with a direct warning: “Do NOT use Omarchy if you care about security of your machine even a little bit.” Omarchy’s own package repository is configured with SigLevel = Optional TrustAll, meaning its packages carry SHA-256 checksums for integrity but no PGP signature chain — trust falls to the host at pkgs.omarchy.org rather than a cryptographic key.

Earlier versions had other documented gaps: LLMNR was enabled by default — a known attack vector for name-poisoning on local networks — the UFW firewall was configured but not running, and the login attempt limit was relaxed from the standard three attempts to ten, making brute-force attacks against local accounts more feasible. Community developer “dannymcc” published an open-source hardening script on GitHub addressing these gaps.

Additionally, Omarchy requires Secure Boot and TPM to be disabled — a deliberate design choice that limits its deployability on managed enterprise machines or machines that need those protections.

None of this is fatal for a developer workstation with appropriate threat modeling. But the combination of a rolling Arch base, a shell layer tracking upstream git rather than tagged releases, an unsigned package repository, and a documented history of security gaps in early release versions means that adoption on machines holding production credentials, SSH keys, or cloud API tokens warrants a deliberate hardening pass before or immediately after installation.

A Governance Model That Concentrates Power By Design

Beyond the security questions, the Omacom Foundation’s structure raises a governance question that the open-source sustainability literature identifies as a known risk: single-patron dependency.

Unlike the Apache Software Foundation, the Linux Foundation, or Mozilla, the Omacom Foundation is not community-governed. It is explicitly controlled by its founder, with a “by DHH” byline baked into the Omarchy installer. Hansson has been transparent about this: “Before this can be an amazing system for everyone, it first has to be an amazing system for me, personally.” That philosophy produced Omarchy — but it also means the foundation’s mission, and the financial security of the upstream projects it now funds, are structurally dependent on one person’s continued engagement.

Vaxry, whose Hyprland project will be exclusively funded by the Omacom Foundation beginning October 10, previously relied on individual donations and the Hyprperks subscription program. That distributed funding base — however modest — was replaced by a single exclusive sponsorship from a single organization. The community has separately raised questions about whether the foundation intends to support Arch Linux’s parent organization, the Software in the Public Interest (SPI) nonprofit, given Omarchy’s dependence on the Arch ecosystem.

The Vaxry/Hyprland relationship carries one additional layer of complexity: Vaxry was banned from freedesktop.org — the umbrella organization covering Wayland, X.org, and related Linux desktop projects — in April 2024, following a code-of-conduct dispute rooted in behavior on the Hyprland Discord server. That ban resurfaced as a public controversy when Framework began sponsoring Hyprland in late 2025, and it remains part of the backdrop as the Omacom Foundation commits to a multi-year exclusive relationship with him.

Does Omarchy Work?

For developers who can tolerate or ignore the political context: yes, it works. The Register tested it hands-on and found it functional, visually striking, and fast on hardware, while noting a clunky secondary-display experience, non-standard keyboard conventions, and a default install footprint of roughly 14 GB after first update — not lightweight, but consistent with a batteries-included philosophy.

Hardware support is broadening. Speaker tuning for Dell XPS in the 2026 lineup was completed ahead of Quattro’s release — notable given that Dell CEO Michael Dell is a founding patron. Framework has certified Omarchy as an officially supported system for its repairable laptops. Omarchy also runs on Beelink mini PCs, which Hansson has publicly recommended as entry hardware for developers exploring Linux.

Whether the Omacom Foundation’s patron model proves durable — and whether Omarchy can expand beyond the developer communities already using it — depends on whether its governance concentration proves to be a feature (clear direction, fast decisions, high quality bar) or a liability (fragility, community alienation, key-person risk). The foundation now has $12.6 million and institutional structure to find out. What it does not yet have is an answer to what happens if the person whose name is on the installer decides to move on.

Currency conversions in this article are approximate, based on exchange rates as of August 31, 2026.

Frequently Asked Questions

What is the Omacom Foundation, and how does it fund Omarchy development?

The Omacom Foundation is a US nonprofit incorporated by DHH (David Heinemeier Hansson) in August 2026 to provide long-term institutional support for Omarchy, an Arch Linux distribution built around the Hyprland compositor and Quickshell desktop toolkit. The foundation’s mandate includes holding the Omarchy trademark, funding infrastructure, promoting adoption, and directly sponsoring the upstream open-source developers whose work Omarchy depends on. Rather than paying Omarchy developers directly, it has so far channeled funds to Vaxry (Hyprland’s creator) and “outfoxxed” (Quickshell’s creator) under multi-year exclusive and premier sponsorships — meaning those developers now have stable, unconditional income to work on the tools that underpin the entire Omarchy desktop.

What is Hyprland, and why does the Omacom Foundation’s exclusive sponsorship matter?

Hyprland is a dynamic tiling Wayland compositor — the layer of Linux software that manages how windows are drawn, arranged, and animated on screen. It is one of three core technologies in Omarchy (alongside Arch Linux and Quickshell), and its creator, Vaxry, had previously sustained development through individual donations and a paid subscription program called Hyprperks. The Omacom Foundation’s exclusive three-year sponsorship replaces all of that with a single long-term commitment, allowing Vaxry to work full-time on Hyprland without seeking commercial development contracts. As a condition of the deal, Hyprperks will be discontinued and its previously gated content will be released for free.

Is Omarchy Linux secure enough for production development use?

Not out of the box — at least not at version 4.0. The initial Quattro release shipped with documented vulnerabilities (including bash injection and arbitrary code execution via notifications) that required a rapid v4.0.1 patch. Earlier versions had additional known gaps: LLMNR was enabled, the firewall was configured but not running, and the login attempt limit was set to ten rather than the usual three. The package repository uses checksums rather than a full PGP signature chain. Omarchy requires Secure Boot and TPM to be disabled by design. For a developer workstation that holds SSH keys, cloud credentials, or production access, a deliberate hardening pass after installation is advisable. Community-maintained tools exist for this purpose, including the open-source omarchy-hardening script.

What does it mean that Omarchy is “by DHH,” and why does governance matter for a Linux distribution?

The “by DHH” byline embedded in the Omarchy installer signals that the project is explicitly built around one person’s preferences — DHH has stated that the system must first work for him personally before it can work for others. The Omacom Foundation inherits this model: it is controlled by its founder rather than by a community board or membership structure, unlike major open-source foundations such as Apache, Mozilla, or the Linux Foundation. This produces a clear editorial direction and fast decision-making, but it also means the upstream projects the foundation funds — Hyprland and Quickshell — are now financially dependent on an organization whose mission and longevity are tied to a single individual’s continued engagement.