omarchy

Open source alternative to macOS, Windows and ChromeOS

45.3K stars
MIT
Active this week
Last commit 1 day ago

Last verified Oct 20, 2026

Deploy DHH's opinionated Arch Linux desktop on hardware you own: preconfigured Neovim, shell tools, and themes for a full developer environment.

Visit website GitHub45.3K

Read the full breakdownWho it is for, how it works, trade-offs and the FAQ

who it's for

Who omarchy is for#

Developers switching from macOS to Linux

Developers who want to leave Apple hardware or the macOS ecosystem without spending weeks configuring a Linux environment from scratch. Omarchy provides a working daily-driver setup with a documented manual for every component, reducing the Mac-to-Linux transition from an open-ended configuration project to a single install.

Skip if:

You depend on macOS-only commercial applications with no Linux alternatives, such as Xcode for iOS development, Final Cut Pro, or Logic Pro. Omarchy is a developer workstation; it does not run macOS software natively.

Developers unhappy with WSL2 on Windows

Windows developers who use WSL2 for Linux toolchains but want native Linux behavior for networking, filesystem performance, and process management. Omarchy installs alongside Windows in a dual-boot setup, giving you a native Linux environment when needed without abandoning Windows entirely.

Skip if:

Your work is Windows-specific: Windows desktop application development, Active Directory administration, or .NET on Windows. Omarchy's Windows VM chapter covers occasional Windows software use, but omarchy is not a Windows-primary environment.

Developers who want Neovim and CLI tooling without manual setup

Developers who prefer keyboard-driven, terminal-first workflows and want Neovim, shell functions, and a tiling window manager without spending time on configuration decisions. Omarchy delivers a working configuration of these tools on first boot, with a manual documenting every default and how to override it.

Skip if:

You prefer IDE-driven development with graphical debuggers, visual Git clients, or browser-based dev tools as your primary interface. Omarchy's toolchain is oriented toward terminal and keyboard-first workflows; you would be fighting the defaults.

the problem

The problem it solves#

Switching from macOS or Windows to Linux as a primary developer OS is harder than it looks. A clean Arch Linux install delivers building blocks, not a working environment: you spend days configuring a window manager, choosing a terminal emulator, wiring up a clipboard manager, selecting and configuring a code editor, and debugging display scaling and power management on your specific hardware. Most developers give up mid-process and return to macOS, or accept Windows with WSL2 as a compromise that never quite behaves like native Linux.

macOS solves the out-of-box problem but at a cost: Apple hardware lock-in means your development environment is tied to Apple products. Windows offers hardware flexibility but routes Linux toolchains through WSL2, a compatibility layer with known friction around filesystem performance and networking. ChromeOS requires a Google account, stores files in the cloud by default, and treats its Linux container as a feature add-on rather than the primary environment. None of these gives a developer a native Linux environment that is ready to use on day one on hardware they already own.

how omarchy solves it

How it solves it#

Tiling Window Manager and Preconfigured Desktop

Omarchy ships with a preconfigured tiling window manager alongside a top bar, a theme system with support for custom and extra themes, hotkey definitions, and screen and screensaver management. The manual documents navigation, idle behavior, screenshots, and screen recording across dedicated chapters, so developers arrive at a working graphical environment without configuring each component from scratch.

Preconfigured Neovim Environment

Neovim is included as the primary editor with an omarchy-specific configuration, documented in its own manual chapter. Developers get a functional editor setup on first boot rather than starting from a blank configuration file. The distribution also covers AI-assisted coding tools in a separate chapter, giving developers an integrated coding environment out of the box.

Unified Clipboard and History

Omarchy includes a clipboard manager with persistent history, documented in a dedicated manual chapter. This replaces the standard single-entry clipboard with a history accessible from any application. macOS ships this natively; most vanilla Linux setups require manually installing and configuring a clipboard manager before it works the same way.

Shell Tools and Functions

The distribution includes curated shell tools and pre-defined shell functions, covered across two dedicated manual chapters (Shell Tools and Shell Functions). Developers get a configured command-line environment with useful tools and aliases in place on first boot, rather than sourcing and configuring them one by one. Shell plugins are also extensible through the documented plugin system.

Omarchy CLI

A dedicated command-line interface manages omarchy-specific operations and system settings, documented in a standalone manual chapter. The Omarchy CLI provides a consistent interface for managing the distribution without editing configuration files directly, and covers operations that span system management, updates, and configuration.

strengths · trade-offs

Strengths and trade-offs#

Strengths

MIT License with No Hardware Lock-inOmarchy carries no OS licensing fee and no hardware requirements. Unlike macOS, which requires Apple hardware by design, or Windows, which carries licensing costs on OEM hardware purchases, omarchy runs on any compatible machine you already own or can buy at any price point. The MIT license also means you can fork the distribution itself and maintain your own variant.
DHH's Active Daily-Driver ConfigurationThe configuration in omarchy is the same environment DHH uses for daily software development. This is not a demonstration setup or a teaching distribution: it is a working developer environment maintained by its author as their own primary workstation OS, which means real-world usability across actual development workflows is the ongoing quality test.
50-Chapter Manual Covering Every ComponentOmarchy ships with a detailed manual at learn.omacom.io covering navigation, themes, shell tools, Neovim, AI tools, browsers, gaming, Windows VM usage, hardware authentication, security, dual boot install, unattended installs, system snapshots, and troubleshooting across more than 50 chapters. Developers switching from macOS or Windows have documented guidance for every omarchy subsystem.
No Cloud Dependency or Vendor Account RequiredThe entire system runs locally with no cloud sync, no vendor account login, and no internet dependency for the core environment. This contrasts with ChromeOS, which requires a Google account and defaults to Google Drive, and with macOS, which increasingly routes features through Apple ID. Omarchy works fully offline after installation.

Trade-offs

-Arch Linux Base Requires Linux FamiliarityOmarchy builds on Arch Linux, which is not a beginner-friendly distribution. Troubleshooting system issues, recovering from failed updates, and diagnosing driver problems all require comfort with the Linux command line. Developers coming from macOS with no prior Linux experience will face a learning curve beyond the omarchy configuration itself, and the Arch rolling-release model means occasional breakage is possible.
-1,415 Open Issues Signal an Active Bug SurfaceThe GitHub repository shows over 1,400 open issues. For a tool that configures an entire OS, this means some hardware configurations, driver combinations, or workflow scenarios may not work out of the box. The project is actively developed and the community is engaged, but issues may not resolve quickly for uncommon hardware or edge-case configurations.
-Opinionated Defaults Limit Escape HatchesOmarchy makes strong choices about the window manager, editor, shell, and tooling. If your workflow depends on a different editor or a different desktop model, you are working against the grain of the distribution. The dotfiles system in the manual allows customization, but you are forking from an opinionated baseline rather than composing from neutral parts.

versus alternatives

omarchy vs alternatives#

omarchy vs macOS

macOS is the default developer desktop for engineers who want a polished Unix-like system on premium hardware. It handles display management, power efficiency, and peripheral integration well, and its application ecosystem is broad. The constraint is hardware: macOS runs legally only on Apple hardware, which means your operating system and hardware vendor are the same company. When Apple changes its chip architecture or discontinues a Mac model, your OS choice moves with it.

omarchy runs on any compatible x86_64 machine. Developers who own non-Apple hardware, or who want hardware flexibility at any price point, can run omarchy at no OS licensing cost. For development toolchains specifically, Docker, kernel networking, and Linux-native build tools run without macOS-specific quirks around filesystem performance in containerized workloads or process isolation behavior.

The tradeoff is application breadth outside development. macOS ships with a mature ecosystem for design tools, video editing, and consumer software. omarchy is a developer workstation, not a general consumer desktop, so developers who mix heavy creative work with coding may find macOS the better primary OS.

omarchy vs Windows

Windows offers the broadest hardware compatibility of any consumer OS and, through WSL2, a way to run Linux toolchains on Windows hardware. WSL2 has improved significantly over time, but it remains a virtual machine: file I/O across the Windows and Linux filesystem boundary is slower than native Linux, and some networking configurations behave differently than on a bare Linux system.

omarchy eliminates that translation layer. Running directly on Linux hardware, every Linux-native tool behaves as documented with no WSL boundary between you and the kernel. For workflows that depend on native Linux behavior (containerized deployments with complex networking, kernel-level debugging, or file-intensive builds), this difference is meaningful.

The tradeoff is that Windows supports a wider range of commercial GUI applications. omarchy includes a Windows VM chapter in its manual for running Windows software when needed, but that is a compatibility measure, not native Windows support.

omarchy vs ChromeOS

ChromeOS is a managed, cloud-first desktop designed primarily for general productivity on Chromebooks. It requires a Google account for basic operation, defaults to Google Drive for storage, and targets users who work primarily in a web browser. ChromeOS does offer a Linux container (Crostini) for developers, but it is a Debian VM with limited hardware access, not a native developer environment.

omarchy is the opposite model: fully offline-capable, no vendor account required, with the terminal and local filesystem as first-class citizens. For software developers, the gap is clearest at the toolchain level. omarchy ships a configured editor, shell, and development tools as the primary environment. ChromeOS's Linux support is an optional feature layered on top of a browser runtime.

ChromeOS is the better choice for managed enterprise deployments where IT controls the device, cloud integration is a feature rather than a concern, and the primary workflow lives in web applications. omarchy is the better choice when you own the hardware outright, need a native Linux developer environment, and want no Google account dependency in your daily OS.

tech stack · detected from GitHub

What it's built on#

Languages: JavaScriptLuaPython

frequently asked

FAQ#

Is omarchy free to use?

Yes. Omarchy is MIT licensed and free to install on hardware you own. There is no OS licensing fee, no subscription, and no managed cloud tier. The only costs are the hardware you run it on and the time to install it. The MIT license also allows you to fork and modify the distribution for your own use.

What Linux distribution does omarchy use as its base?

Omarchy is built on Arch Linux. It layers its own configuration, tools, manual, and setup scripts on top of Arch's rolling-release base. This means you get access to the full Arch package ecosystem (including the AUR) alongside omarchy's preconfigured developer environment. The rolling-release model keeps packages current but also means occasional updates can break things.

Does omarchy support dual booting with macOS or Windows?

Yes. Omarchy has a dedicated dual boot install chapter in its manual, allowing you to run omarchy alongside an existing macOS or Windows installation on the same machine. This lets you transition gradually without committing to Linux as your only OS from day one.

Can I customize omarchy after installing it?

Yes, through the dotfiles system documented in the manual. You can override omarchy's defaults with your own configurations for the shell, editor, themes, and other components. Because omarchy is MIT licensed, you can also fork the repository and maintain your own variant of the distribution with different defaults.

What is the Omacom Foundation?

The Omacom Foundation is the organization supporting omarchy's long-term development and stewardship. It launched with $8 million and provides the infrastructure behind the omarchy manual and the learn.omacom.io documentation site. The project itself is maintained by Basecamp (DHH's company) with the foundation providing organizational backing.

also worth a look