Who omarchy is for#
Developers switching from macOS to Linux
The manual includes a dedicated 'Coming From Mac or Windows' section covering navigation differences and equivalent tools. Developers making the switch get a polished, familiar-feeling environment rather than a bare system to configure from nothing.
Skip if:
Skip if you are staying on macOS and do not plan to run Linux. Omarchy is a Linux workstation setup, not a macOS enhancement or Linux-in-a-VM experience.
Developers who want a preconfigured Neovim and terminal workflow
Omarchy bundles Neovim, shell tools, shell functions, and plugins into a cohesive setup. Developers who want these tools without spending weeks configuring them from scratch get a working terminal-first environment immediately.
Skip if:
Skip if you prefer VS Code, JetBrains IDEs, or another graphical editor over Neovim. Omarchy's defaults center on Neovim and terminal-first workflows.
Developers avoiding cloud dev environment billing
GitHub Codespaces, Gitpod, and Google Cloud Workstations charge by compute time and require ongoing accounts. Omarchy gives you an equivalent opinionated developer environment on your own hardware with no monthly cost after initial setup.
Skip if:
Skip if your workflow genuinely requires cloud-hosted environments: collaborative dev containers, ephemeral per-branch workspaces, or remote server access. Omarchy is a local workstation setup, not a remote environment.
Basecamp and 37signals followers adopting DHH's toolchain
Created and maintained under the Basecamp GitHub organization, omarchy reflects the tooling philosophy behind Ruby on Rails, Hey, and Basecamp. Developers who follow DHH's opinions on software development get a fully expressed version of that philosophy as a complete workstation.
Skip if:
Skip if you find DHH's tooling preferences (Neovim, terminal-first, Linux) misaligned with your own. The value of an opinionated setup depends on agreeing with the choices the curator made.
The problem it solves#
Setting up a productive Linux developer workstation from scratch is a time-consuming process with hundreds of small decisions: which terminal emulator, which editor and plugins, which shell, which clipboard manager, which window manager, and how to configure them to cooperate. Most developers spend days or weeks on environment setup before they can work at full speed. The result is often an inconsistent setup that degrades over time as packages conflict and dotfiles drift.
Cloud developer environments like GitHub Codespaces and Gitpod solve part of this by providing pre-built containers, but they cost money per compute hour, keep your environment on someone else's servers, and require an internet connection for day-to-day work. For developers who want a permanent local workstation with opinionated defaults they can trust, neither the blank Linux slate nor the cloud vendor option fully delivers.
How it solves it#
Preconfigured Neovim environment
Ships with a complete Neovim setup ready to use immediately, including plugins, key mappings, and configuration tuned for developer workflows. You get a working editor without spending hours on init.lua configuration or plugin manager setup.
Unified clipboard with history
System-wide clipboard that tracks copy history across all applications. Paste any previously copied item, not just the most recent one, without needing a separate clipboard manager tool or browser extension.
Theme system with custom theme support
Ships with built-in themes and supports extra themes and custom theme creation. You can change the visual appearance of your entire desktop environment, including terminal colors and UI elements, through a single configuration layer.
Shell tools, functions, and plugins
Ships with a curated set of shell tools, custom shell functions, and shell plugins configured to work together. Covers everyday developer tasks without requiring you to source and configure each tool individually from scratch.
AI coding tool integration
Includes configuration and setup for AI coding assistants. The distribution has a dedicated AI section in the manual covering setup and integration of AI coding tools into terminal-based development workflows.
Omarchy CLI
A dedicated command-line interface for managing your omarchy installation. The CLI provides shortcuts for common system tasks and configuration management without leaving the terminal environment.
Strengths and trade-offs#
Strengths
- MIT license with full source accessEvery omarchy script and configuration file is MIT licensed, meaning you can read, copy, modify, and redistribute it without restriction. Unlike cloud developer environment vendors, there is no proprietary layer hiding how your environment is configured.
- Runs entirely on hardware you ownNo compute billing, no internet dependency for day-to-day development, no vendor control over your environment. Omarchy runs on your laptop or desktop and continues to work regardless of any external service changes.
- 25,000+ GitHub stars in its first yearWith over 25,000 GitHub stars since its June 2025 launch, omarchy has attracted broad developer attention. The star count indicates real mindshare among developers looking for an opinionated, local Linux setup with a credible author behind it.
- Unattended and dual-boot installers includedShips with both an unattended installer for headless setup and a dual-boot installer for running alongside an existing macOS or Windows system. Both paths are covered in the manual, making the transition practical for developers moving from other platforms.
Trade-offs
- -743 open issues on a project less than two years oldWith 743 open GitHub issues and a launch date of June 2025, omarchy is still working through configuration gaps and edge cases. Developers who need a fully polished, battle-tested setup may encounter rough edges in less common hardware or workflow configurations.
- -Opinionated defaults require buy-inOmarchy makes specific choices about your editor (Neovim), shell, tools, and desktop environment. If you prefer VS Code, JetBrains, or a different workflow, you will spend time overriding defaults. The setup rewards developers who align with DHH's tooling preferences.
- -Linux-first with limited Mac coverageOmarchy is designed for Linux workstation installation. The manual includes a Mac support section, but the primary and most complete experience is on Linux. Windows users are not a supported target audience.
omarchy vs alternatives#
omarchy vs GitHub Codespaces
GitHub Codespaces provides cloud-hosted developer environments that spin up in minutes, accessible through a browser or VS Code, billed by compute hours. You get a pre-built container configured for a specific repository.
Omarchy takes the opposite approach: a local Linux workstation setup installed on hardware you own. There is no compute billing, no internet dependency for day-to-day development, and no container abstraction between you and your machine.
| Feature | omarchy | GitHub Codespaces |
|---|---|---|
| License | MIT | Proprietary |
| Hosting | Your hardware | GitHub cloud |
| Cost model | Free (one-time setup) | Billed by compute hour |
| Offline capability | Full | Requires internet |
| Editor | Neovim (preconfigured) | Any VS Code-compatible |
| Environment scope | Personal workstation | Per-repository container |
Omarchy is the better choice when you want a permanent local workstation with no recurring cost and full offline capability. GitHub Codespaces is worth choosing when you need ephemeral per-repository environments, collaborative dev containers, or consistent team environments without any local setup.
omarchy vs Gitpod
Gitpod creates automated, ephemeral development environments defined by a .gitpod.yml configuration in your repository. Like Codespaces, it is cloud-hosted and billed by workspace hours.
Omarchy and Gitpod solve related but different problems. Gitpod provides reproducible per-project environments that any team member can open in one click. Omarchy configures your personal workstation once and keeps it consistent across all projects you work on.
| Feature | omarchy | Gitpod |
|---|---|---|
| License | MIT | Proprietary (self-host option exists) |
| Environment type | Personal workstation | Per-repository workspace |
| Cost model | Free (self-installed) | Usage-based billing |
| Configuration | dotfiles and shell scripts | .gitpod.yml per repo |
| Primary editor | Neovim, terminal-first | VS Code, JetBrains, terminal |
Omarchy is the better choice for developers who want a tuned personal Linux environment they use across all projects. Gitpod is the better choice when the goal is reproducible, team-shared environments that developers can open without any local setup on any machine.
What it's built on#
- Languages
- JavaScriptLuaPython
FAQ#
Is omarchy a full Linux distribution or a configuration layer?
Omarchy is a configuration layer and installer, not a traditional Linux distribution with its own kernel or package repositories. It runs on top of an existing Linux base and applies DHH's opinionated setup: preconfigured Neovim, shell tools, themes, clipboard management, and a curated application selection. The project is MIT licensed and hosted on GitHub under the basecamp/omarchy repository.
Who created omarchy and who maintains it?
Omarchy was created by David Heinemeier Hansson (DHH), creator of Ruby on Rails and co-founder of Basecamp and 37signals. The project is hosted under the Basecamp GitHub organization and was first published in June 2025. As of August 2026, it remains actively maintained with recent pushes to the repository.
How does omarchy compare to GitHub Codespaces or Gitpod?
GitHub Codespaces and Gitpod are cloud-hosted developer environments you access through a browser or editor extension, billed by compute time. Omarchy is a local Linux workstation setup installed on hardware you own, with no ongoing cost. Both approaches solve the same underlying need (a preconfigured developer environment without manual setup) through different means: cloud compute versus local hardware. Omarchy is the better fit when you want offline capability and no billing; Codespaces or Gitpod are better when you need team-shared ephemeral environments.
Does omarchy work on macOS?
Omarchy has a Mac support section in its official manual, indicating some Mac compatibility. The primary and most complete target is a native Linux workstation install. The manual also covers dual-boot installation for running alongside macOS or Windows on the same machine.
What license does omarchy use?
Omarchy is released under the MIT License. You can use, modify, fork, and redistribute it without restriction, including for commercial purposes. The full source is available on GitHub at basecamp/omarchy.
Similar open-source tools#
EmDash CMS
Web-based CMS for creating and managing AI playgrounds
VoidZero
Next-generation unified JavaScript tooling infrastructure
Zed
High-performance open source code editor with built-in AI
dograh
Open source voice agent builder with telephony and BYOK AI support
iroh
Connect devices seamlessly without relying on the cloud.
whishper
Local speech-to-text transcription and subtitling with a web UI