By James Marcus (Content Lead, 5ac.vn) — technical CEO perspective. Sources: omarchy.org, github.com/basecamp/omarchy (v4.0.0 release, PR #6231, discussions #6486/#6387), DistroWatch, DeepWiki, Phoronix, shaunli.com.
Introduction
David Heinemeier Hansson (DHH) needs no introduction to anyone who has written Rails. The man who turned convention-over-configuration into an industry standard has now turned his attention to something else: the desktop you sit in front of for hours every day.
Omarchy is "Beautiful, Modern & Opinionated Linux". It sounds like a slogan, but the key is in the last word: opinionated. DHH did not build a distro for you to click through 4-8 hours of setup. He built an Arch + Hyprland desktop that he personally uses, packaged it into an ISO, and handed it to you on the assumption that his choices are better than your defaults.
This post does not compare Omarchy to 5ac's G-Company OS. They sit on completely different layers: Omarchy is a desktop running on your personal laptop; G-Company OS is an agentic OS running on a VPS for businesses. Here I answer one practical question: why would a developer in 2026 leave a MacBook or Windows for Omarchy, and what is the price you pay.
1. What is Omarchy?
Omarchy is an Arch-based Linux distro using the Hyprland tiling window manager, founded by DHH (basecamp/omarchy on GitHub, MIT licensed, open source). The "omakase" philosophy borrows from Japanese sushi tradition: you sit down, the chef (the distro) chooses for you, and it is usually better than if you chose yourself.
The target audience is clear: developers and technical creators who want Arch's power but do not want to spend half a day setting up Hyprland, Waybar, Mako, and the surrounding tooling. Omarchy ships all of it pre-configured.
Real numbers (as of 08/20/2026):
| Metric | Value | Source |
|---|---|---|
| GitHub stars | ~25,700 (25,682) | github.com/basecamp/omarchy |
| GitHub forks | ~2,600 (2,614) | github.com/basecamp/omarchy |
| GitHub open issues | 776 | github.com/basecamp/omarchy |
| DistroWatch rank | #21 (478 hits/day, 12mo) | distrowatch.com/omarchy |
| DistroWatch rating | 8.7/10 (39 reviews) | distrowatch.com/omarchy |
| GitHub Trending | Reached #3 (09/2025) | trendshift.io |
One important caveat about DistroWatch: "hits per day" measures page views, not actual install counts. DistroWatch states publicly that the number "correlates neither to usage nor to quality". Use it as a measure of interest, not market share. Omarchy's #21 rank is very high for a distro that launched 06/01/2025 (roughly 14 months old). One week after the v4.0.0 release, the rank jumped to #11 (750 HPD).
2. Quattro v4.0.0 — the biggest release since the project began
Released 08/14/2026 (tag v4.0.0, author dhh). The largest release in the project's history. Five points worth knowing:
2.1 The entire shell rewritten in Quickshell
omarchy-shell is a single Quickshell (Qt Quick) process running the whole desktop. Hyprland autostart launches it via quickshell -p $OMARCHY_PATH/shell. Everything (bar, panels, overlays, menu, lock screen, polkit dialog, even background services like battery watcher, idle watcher, night-light) is a plugin inside that one process.
It replaces the whole stack: Waybar, Walker, Mako, SwayOSD, hyprlock, hypridle, swaybg, polkit-gnome. Three reasons DHH gives (shell/README.md): (1) shared services run once instead of once per process; (2) summoning a panel is IPC into the running process, no cold-start; (3) third-party plugins load from disk without patching Omarchy source.
The plugin system uses a schemaVersion: 1 manifest with namespaced ids (omarchy.* reserved for first-party, third parties cannot claim them). It is managed over a Unix socket IPC: summon, hide, toggle, call, rescanPlugins, applyTheme... Third-party plugins install via omarchy plugin add <git-url>, landing in a DISABLED state so you read the code first; no install hook runs, no sudo is requested.
2.2 Model-usage bar widget
An "agents" icon appears on the bar automatically the moment Omarchy detects AI usage; it stays hidden if you do not use agents. Left-click opens a panel: plan, % of 5h-session + weekly limit, token usage by day and by model. Right-click launches the default agent. Data refreshes every 15 minutes.
Out of the box it supports Claude Code, Codex, Fireworks (per the v4.0.0 release notes + manual/17-ai.md). Some secondary sources mention Pi, Oh My Pi, OpenCode, but GitHub discussion #6486 (08/2026) confirms OpenCode is not yet first-class in the native agents panel. The counting mechanism is local scraping: each harness has its own collector (e.g. bin/omarchy-agent-usage-claude scans ~/.claude/projects/*.jsonl for assistant messages with a usage block, dedupes, aggregates tokens by model). Simple, local, no unified API needed.
2.3 Configurable default coding agent (lazy-install)
You pick 1 of 9: Claude Code, Codex, OpenCode, Pi, Oh My Pi, Gemini, Grok, Copilot, Crush. Stored at ~/.config/omarchy/defaults/agent. The good part: the agent is not pre-installed. Launchers are tiny stubs in ~/.local/bin/ managed by mise. The first call fetches the npm package via npx. SUPER+SHIFT+CTRL+A (or typing a in a terminal) opens the agent in its own window, app id org.omarchy.agent, running in ~/Work.
2.4 Dual-boot + OEM + Factory reset
Default bootloader is Limine (since Omarchy 2.0), using Unified Kernel Images + Snapper snapshots. When free space exists, the installer offers a side-by-side install; Windows is reminded to disable BitLocker first. limine-scan auto-detects EFI entries, and the ISO installer finds the Windows ESP (/EFI/Microsoft/Boot/bootmgfw.efi) on its own. OEM setup lets the install finish with no user, so the owner picks keyboard/account on first boot. Factory reset (Quattro only) swaps the root for a fresh @factory snapshot and scrubs machine identity for resale.
2.5 Theme engine 8 → 24 colors
Quattro expands the base 8 to 24 colors in colors.toml, auto-generating configs for terminal (Foot/Alacritty/Ghostty/Kitty), btop, Chromium, Hyprland, Neovim, Helix, VSCode, Obsidian, and the whole shell. 22 themes ship (Tokyo Night, Catppuccin, Gruvbox...). User override goes through ~/.config/omarchy/themed/<name>.tpl with placeholders {{ background }}, {{ accent }}, {{ color0 }}..{{ color15 }}. Switcher: SUPER+SHIFT+CTRL+SPACE.
The v4.0.0 ISO is under 6GB (5,982 MB, >1GB smaller than v3), install speed is +30% ("sub-minute installs now possible"). New default apps: Omawrite (Markdown writer replacing Typora), Omacut (video trim), Omacalc (calculator). The default terminal switches to Foot.
3. Why Omarchy fits as a MacBook/Windows replacement
Four practical reasons a 2026 developer considers the switch:
Keyboard-driven tiling. Hyprland manages windows by key, snap/move with SUPER+arrow, workspaces, gaps. macOS only has Stage Manager/Mission Control; tiling needs third-party tools (Rectangle, yabai). Windows has Snap layouts, weak tiling via PowerToys FancyZones. If you live by the keyboard, Omarchy was built for you.
Coding agent is a first-class citizen. Model-usage bar, 9 lazy-install agents, launch by shortcut, theme sync to the agent. macOS/Windows have no OS-level usage widget; you install terminal agents yourself.
Cost. Free OS; you only pay for a self-built PC (possibly reused). MacBooks are $1,000-$3,500+ with locked hardware. Windows is free on a self-built PC, but a pre-built license runs $600-$2,000.
Privacy. No telemetry, self-hosted. DHH proudly claims "no phoning home". macOS has telemetry (opt-out); Windows has the most (copilot/recall controversies).
The price: the Arch rolling release carries break risk, the learning curve is steep for Linux newcomers, and NVIDIA/VM compatibility is not perfect. Omarchy reduces break risk with snapshots and a migration runner (details in section 5).
4. Omarchy vs MacBook vs Windows
The table below summarizes real end-user dimensions (sources: omarchy.org manual, GitHub, DistroWatch, Phoronix):
| Dimension | Omarchy (Arch/Hyprland) | MacBook (macOS) | Windows (11/10) |
|---|---|---|---|
| Window management | Keyboard tiling (Hyprland), SUPER+arrow, workspace, gap | Stage Manager/Mission Control; tiling via 3rd-party | Snap layouts; weak tiling (FancyZones) |
| Coding agent | First-class: usage bar, 9 lazy-install agents, theme sync | Self-installed terminal; no OS-level widget | Self-installed; WSL2 for Linux toolchain; no widget |
| Cost (HW+OS) | Free OS; self-built/reused PC | $1,000-$3,500+, locked hardware | Free on self-built PC; or $600-$2,000 license |
| Customization | Total (QML plugin, 24-color theme, shell.toml) | Limited (System Settings, no WM edits) | Medium (registry, Powertoys); fixed WM |
| Update model | Rolling (Arch) + migration-runner + snapshot rollback | Yearly major + delta; very stable | Feature v2/23H2 + cumulative; many reboots, occasionally breaks |
| Arch rolling risk | Break possible (but direct block + snapshot protect) | None | None |
| Gaming / GPU | Linux drivers better but still behind Windows in spots | Good (Metal, native ports) | Best (DirectX, vendor drivers) |
| App ecosystem | Linux native + Flatpak/AUR; missing Adobe/Discord/some games | Full (Xcode, Adobe, Final Cut, AAA) | Most complete (vendor Windows-first) |
| Security | pkexec/polkit context-aware, fingerprint PAM, LUKS | T2/Secure Enclave, FileVault, Gatekeeper | BitLocker, Secure Boot, Defender |
| Learning curve | Steep for Linux newcomers | Low (consumer) | Low (consumer) |
| Offline / privacy | No telemetry, self-host | Telemetry present (opt-out) | Most telemetry |
Summary: Omarchy wins on tiling, agent integration, customization, cost, privacy. It loses on app ecosystem (Adobe/AAA games), rolling-Arch stability (mitigated by snapshot/migration), learning curve, gaming GPU. The segment is clear: highly technical developers who want self-sovereignty and a "developer workstation" without paying MacBook money or running Windows. Not for mainstream users.
5. Risks for Vietnam-based developers
A Vietnam developer reading this usually has 3-4 specific concerns. Here is the reality:
Arch rolling release. Direct pacman -Syu is blocked by Omarchy (a guard) to force omarchy update, because that snapshots the root FS → updates packages → runs omarchy-migrate → post-update hook. The migration runner executes migrations/*.sh (timestamped, idempotent, runs as user not root), with state at ~/.local/state/omarchy/migrations. Snapshot rollback picks a build from the Limine boot menu and restores the root FS (not /home or ~/.config). So breakage is less scary than raw Arch, but you still need to understand what you are doing.
NVIDIA driver. Linux drivers (NVIDIA/AMD/Intel) are much better now, but still behind Windows in some cases (especially game/graphics intensive). If you do ML on an NVIDIA GPU, test thoroughly before switching.
Dual-boot with BitLocker / Secure Boot. Windows uses BitLocker + Secure Boot. Limine by default does not support Secure Boot (per community discussion). If you do not disable BitLocker before dual-booting, Windows can fall into recovery from TPM/PCR drift. The community repo peregrinus879/omarchy-secureboot (sbctl signing + Limine enrollment) exists, but it is community, not official.
Bluetooth keyboard + LUKS. Full-disk LUKS encryption requires a passphrase at boot. Bluetooth keyboards often do not work at the pre-boot stage, so you can get stuck at the passphrase screen. Keep a wired keyboard as backup.
VM not recommended. Many features (LUKS, snapshot, fingerprint) depend on real hardware. Omarchy targets bare metal; running it in a VM/cloud desktop loses or limits functionality. Use real hardware.
6. Conclusion
Omarchy is not a business tool. It is a beautiful, keyboard-driven Linux desktop, ready to run coding agents, built for technical developers who want self-sovereignty without spending 4-8 hours setting up Arch. DHH packages his opinions into an ISO, and with Quattro v4.0.0 he pushes it from "something nice" to "something you can actually use daily" (rewritten shell, usage bar, lazy-install agent, theme engine, OEM/factory reset).
For 5ac: our G-Company OS is an agentic OS on a VPS for Vietnamese businesses, a completely different layer from Omarchy. But if you are a developer running 5ac agents on an Omarchy host, the two cooperate well: Omarchy handles the pretty, keyboard-driven desktop; G-Company OS handles the agent team running your business through a gateway. That is an upstream option, not the core of this post.
If you are weighing whether to drop a $3,000 MacBook to build a Linux PC, Omarchy is worth a try in 2026. Just remember: the rolling release is a feature, not a bug. Learn the snapshot and migration runner before you update.
SEO / Structured data (for deploy stage)
- Canonical pair: VI
/blog/omarchy-linux-desktop-thay-the-macbook-windows/↔ EN/en/blog/omarchy-linux-desktop-replaces-macbook-windows/ - Schema:
BlogPostingwithinLanguagevi/en,authorJames Marcus,publisher5ac.vn - Suggested internal links (C20/C21 cluster): zorin-os-18-1-core-vs-lite-may-cu-thoat-windows, deepseek-claude-code-codex-chon-mo-hinh-theo-roi-smb
- FAQ candidates: "Omarchy có free không?" (có, MIT); "Chạy được Adobe/AutoCAD không?" (không native, Wine/thực tế hạn chế); "Có an toàn cho beginner không?" (rolling release, cần hiểu snapshot); "Khác gì so với Ubuntu/Fedora?" (Arch rolling + opinionated DHH stack + Quickshell shell riêng).
- Images needed (hand to ux-designer): OG image (Omarchy desktop tiling screenshot mock), comparison table infographic, Quickshell plugin-architecture diagram.