DHH Launches Omarchy Quattro and an $8M Linux

The "year of the Linux desktop" has been a running joke in developer circles for so long that it's basically a personality trait at this point — a kind of annual ritual humiliation that Linux enthusiasts perform on themselves. DHH, to his considerable credit, is aware of this. He's been on the Linux desktop for over two years and has spent much of that time publicly willing the rest of the developer world to follow him there.

On a recent episode of The Standup, alongside ThePrimeagen, Teej, and TrashDev, he made his most serious case yet — and backed it with something that has a way of clarifying intent: money.

What Omarchy Quattro Actually Is

Omarchy is DHH's opinionated Arch Linux distribution, built around Hyprland and oriented toward keyboard-first developers. Quattro is the first version to get its own moniker, and DHH describes it as a ground-up rewrite rather than an incremental update. The whole thing was rebuilt in QuickShell, with 17 dependencies removed, the ISO shrunk by 30%, and the install time reduced significantly — now coming in around 45 seconds on fast hardware, by DHH's account.

The architecture shift that matters most, though, is the move from a git-checkout-in-your-home-directory setup to a fully packaged system. That change alone, DHH says, eliminated roughly 70% of the bug reports they were seeing, because user configs and system configs were no longer stepping on each other. It sounds unglamorous — and it is — but it's the kind of foundational work that separates "passionate side project" from "distribution people can actually depend on."

The plugin story is still early but notable. A community-led repository at omachiplugins.com launched alongside Quattro, and DHH reports on the podcast that it was tracking toward 1,000 plugins within its first week of existence.

The $8 Million

Here's where it gets interesting for anyone who follows OSS sustainability. DHH announced — live, apparently within the hour before recording — the formation of the Omarchy Foundation, with $8 million in pledged funding.

The donor list is not subtle: Michael Dell, Toby Lütke (Shopify), Patrick Collison (Stripe), Matthew Prince (Cloudflare), Brendan Eich (Brave), Jason Fried (37signals/Basecamp), and Jack Dorsey, among others. DHH describes pitching Lütke on Sunday with the idea of putting in a million dollars himself, and Lütke immediately matching without hesitation. "What do you mean, you don't have to think about it?" DHH recalls responding.

According to DHH on the podcast — and confirmed separately via his own post on X — Omarchy Quattro is currently pulling close to 5,000 ISO downloads per day.

The foundation money has three stated uses: fund developers, fund infrastructure, fund marketing. The developer funding piece is where the most concrete announcement sits. Vaxry — the creator of Hyprland — is becoming the Omarchy Foundation's exclusive sponsor for three years, with a two-year option, meaning he can focus entirely on Hyprland development without commercial pressure. DHH is quick to note that Hyprland remains MIT-licensed and freely available to any other distribution. "It's not like, oh my god, now it's off the market," he says. "This is all MIT licensed stuff."

That distinction is worth dwelling on. The OSS sustainability conversation has a recurring anxiety about what happens when a foundation or corporate sponsor starts funding a critical dependency — does the code quietly drift toward proprietary? Does it create a de facto lock-in even if the license doesn't? DHH's explicit answer is no, and the MIT license enforces that legally. But the social reality of a project having a single large sponsor with its own distribution motives is more complicated than the license alone can resolve. History has examples going both ways.

The infrastructure pillar involves building out sovereign package servers, mirrors, agent runners, and QA infrastructure — everything required to run what DHH calls a "top-tier" distribution without depending on third parties for the critical path. The marketing pillar is the one DHH acknowledges developers are "goddamn allergic to" — merchandise, events, visibility. The goal is making people aware that Linux, specifically Omarchy's version of it, exists and is good.

The Supply Chain Question

The most substantive technical exchange in the episode comes when the hosts push DHH on supply chain security — a concern that's not abstract. The AUR (Arch User Repository), which Omarchy has historically leaned on, is among the largest community package repositories around, according to the AUR's own package index. And as the hosts note, supply chain attacks against community repositories have been happening with uncomfortable regularity.

DHH's answer is essentially: we're going to stop depending on the AUR for anything that ships by default. Everything in the core Omarchy installation is already compiled on their own build machines and hosted in their own package repository. The AUR is currently still used for some optional installs, but the plan is to keep cherry-picking the most popular packages — the top slice of downloads that represents the bulk of actual usage — and bring them in-house, until the AUR is purely an opt-in for power users who know what they're doing.

He also describes a two-tier package update system that's genuinely clever: stable system packages managed through Pacman run on a one-month lag from upstream Arch by default, which prevents the 3am "someone pushed a broken update" problem they learned about the hard way. Meanwhile, high-churn developer tools like AI coding agents — which can update many times in a single day — live in a separate tier managed through a tool called Mise, so they can move fast without touching system stability. BTRFS snapshots and a factory reset feature round out the resilience story.

The agent-powered security vetting of plugins is the piece that's still more aspiration than implementation, and DHH is honest about that. The plugin repository has the same trust problem as the AUR. He says it's going to get fixed. Whether you find that reassuring probably depends on your prior relationship with promises made during launch week.

The Apple Grievance (It's Not Just Grievance)

A significant chunk of the episode is DHH making the case that macOS is architecturally hostile to AI agents — not as a rhetorical flourish, but as a structural argument. The core of it: everything you'd want an agent to configure on your behalf on a Mac requires either navigating GUI menus manually or going through Apple's notarization process. You can't set hotkeys programmatically. You can't check in your configs. Raycast, a popular launcher, requires you to use export/import menus to move your config around. Homebrew softens some of this but can't fix the underlying architecture.

"The entire operating system is just not built for agents," DHH says. "It's not built for accessibility of the tooling we want to use."

This is the strongest version of his argument, and it's worth taking seriously even if you like your Mac. The premise is that in an era where AI agents are increasingly doing configuration and setup work on behalf of users, an OS where those agents can't touch the core is going to lose ground to one where they can touch everything. Linux's traditional selling point — that you can change anything — stops being a nerd credential and starts being a genuine product advantage when there's an agent doing the changing for you.

Whether that advantage materializes depends on agents being actually good at this, on distributions being stable enough that people trust the output, and on the hardware finally being competitive. DHH is betting all three conditions are now met, or close enough.

The Community Politics

One of the more pointed passages in the episode is DHH going after the governance culture in parts of the Linux world — specifically calling out ideological gatekeeping around who's allowed to use what software and on what terms. He frames the Omarchy Foundation partly as a counterweight to that: a home for people who just want to work on computers without the culture-war adjacency.

"We need just some people who are like, do you know what? We make fun computers. Do you like computers? Then come have fun with us," he says. "I don't give a flying [expletive] what you think about other topics."

That's a position, and it's going to land differently depending on where you sit in the community. Some will find it genuinely refreshing. Others will read it as a familiar move — invoking "just build stuff" as a way to sidestep legitimate governance questions. Both readings are available. What it definitely is: a deliberate positioning choice that will shape who shows up to build Omarchy and who doesn't.

The foundation model itself is new territory for a project like this. OSS sustainability built on a few large donors and a charismatic founder has a track record that's genuinely mixed. The money is real. The ambition is clear. But five years is a long time, and foundations have a way of developing interests of their own.

DHH's version of the year of the Linux laptop might actually be 2026. Or it might be another entry in the longest-running joke in developer culture. The difference, this time, is that the joke has an $8 million punchline.