umbrelOS: a self-hosting OS that installs on bare metal, not on top of Linux
An elegant home server OS. Run OpenClaw, store your files and, and do more with over 300 apps in the Umbrel App Store.
At a glance
- What is it?
- umbrelOS is a standalone home server operating system from getumbrel, distributed as a free image for Intel and AMD machines, Raspberry Pi 5 and VMs, with a 2.0 beta in flight and a PolyForm Noncommercial licence. It is aimed at people who want app-store convenience without renting someone else's computer.
- Who is it for?
- Adopt umbrelOS if you want a self-hosted app catalogue on a dedicated Intel or AMD box, a Raspberry Pi 5 booting from NVMe or USB, or a Proxmox VM, and you accept the PolyForm Noncommercial 1.0.0 terms for personal or nonprofit use.
- Can I use it commercially?
- Check first. The repository uses a licence we do not classify automatically, so read its LICENSE file before any commercial use.
- Is it still maintained?
- Yes. The repository last received commits 13 days ago.
- What is it written in?
- Mainly TypeScript, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on September 15, 2026, and from our analysis. They are not legal advice.
DEEP OPEN-SOURCE ANALYSIS
What problem umbrelOS solves, and for whom
The README frames the goal in one sentence: enjoy the convenience of the cloud without giving up ownership and control of your data. In practice that means the project ships an operating system rather than a package you install into Debian or Ubuntu. umbrelOS boots the machine itself, and the app catalogue lives on top of that. The audience is the person who wants Nextcloud, a Bitcoin node or one of the 300-plus apps named in the repository description, but does not want to hand-roll Docker Compose files, reverse proxies and TLS certificates to get there. The repository description also points at OpenClaw and file storage as headline uses. If your job is running a handful of self-hosted services for a household or a small group, this is the target case. If your job is running Kubernetes, it is not.
Standalone OS, not a layer on your existing Linux
The single most consequential design decision is stated plainly in the README: umbrelOS is a standalone operating system that installs directly onto your device, and it cannot be installed on top of an existing Linux distribution. That rules out the pattern many self-hosters expect, where you keep a familiar distro and add a management layer. Here the OS is the product. The README also states that the image you install on your own hardware is the same umbrelOS that ships on Umbrel Home and Umbrel Pro, with the same features and the same updates. That is a meaningful commitment: there is no separate community edition with features stripped out, at least according to the documentation. The trade-off is that you are adopting an entire platform, including its update cadence, rather than a tool you can remove from an otherwise standard server.
Hardware boundaries and the features that need more than one disk
The README lists the supported targets: most 64-bit Intel and AMD mini PCs, laptops, desktops, NAS boxes and servers; Raspberry Pi 5; and virtual machines on Proxmox, VirtualBox, VMware or anything else that supports EFI boot. Minimum requirements for Intel and AMD are a dual-core CPU, 4 GB RAM (8 GB or more recommended) and a 32 GB drive for umbrelOS itself. The layout detail matters: umbrelOS boots from one drive and uses the rest for apps and data. On Raspberry Pi 5 the README says to boot from an NVMe or USB drive rather than a microSD card, which is consistent with the known endurance problems of SD cards under sustained writes. Two features are hardware-gated. Storage Manager and FailSafe need two or more internal NVMe or SATA drives, and GPU acceleration needs an NVIDIA, AMD or Intel GPU on an Intel or AMD machine. If you have a single-disk mini PC, those two features are simply unavailable to you.
Getting it running: downloads, VM images and the beta toggle
Installation starts at umbrel.com/downloads, which the README says hosts the latest ISO and images plus step-by-step guides per platform. There is no apt package and no install script for an existing system. For the 2.0 beta there are two documented paths. A fresh install means downloading the 2.0 beta image from the same downloads page. If you are already running umbrelOS, the README instructs you to update to umbrelOS 1.7.4 or later, then open Settings > Advanced settings and turn on umbrelOS beta program to receive the 2.0 beta. Note the ordering: the beta toggle requires you to already be on 1.7.4 or newer, so an older install must be updated first. The README states the stable 2.0 release is planned for September 22, 2026, which is a plan, not a shipped artifact. App packaging is a separate repository: the README points developers to the Umbrel App Framework documentation in getumbrel/umbrel-apps rather than describing the manifest format here.
The licence is the constraint most people will miss
The repository metadata reports the licence as NOASSERTION, and the README resolves that ambiguity: umbrelOS is licensed under PolyForm Noncommercial 1.0.0. The README's own summary says you are free to use, fork, modify and redistribute Umbrel for personal and nonprofit use under the same licence, and that commercial use, such as selling plug-and-play home servers with umbrelOS, requires contacting partner@umbrel.com. This is not an OSI-approved open source licence, and the noncommercial restriction is the reason. For a homelab or a nonprofit deployment the terms as described are permissive. For a managed service provider, a reseller, or anyone building a product on top of the OS, the README directs you to a partner conversation instead of granting rights. That is a business decision embedded in a licence file, and it should be read in LICENSE.md rather than inferred from the README's TL;DR. Nothing here is legal advice; the point is that the licence text, not the summary, governs.
Where umbrelOS is the wrong tool
Three cases stand out. First, you already run a tuned Linux server with your own storage layout, firewall rules and backup jobs. The README forecloses installing umbrelOS on top of that distribution, so adopting it means rebuilding the machine, not extending it. Second, you are on a single-drive box and your reason for looking at umbrelOS is storage pooling or redundancy. Storage Manager and FailSafe both require two or more internal NVMe or SATA drives, so on one disk those features do not exist for you. Third, you need commercial redistribution. The PolyForm Noncommercial terms block the reseller path without a separate agreement. There is also a maturity caveat in the material itself: 2.0 is in beta, and the README lists 1.7.4 as the stable line as of the 2.0 beta announcement. Anyone who needs the 2.0 feature set today is running beta software, and the README does not describe a rollback procedure.
The alternative: a general-purpose distro with your own container stack
The obvious comparison is Debian or Ubuntu plus Docker Compose, and the difference is where the abstraction sits. With a plain distro you own the bootloader, the upgrade path, the firewall and the volume mounts, and you install each service from its upstream image. You get portability: any container you define can move to another host unchanged, and nothing in your stack assumes an app-store manifest. umbrelOS inverts that. The OS boots the device, the app catalogue is curated, and updates arrive through the platform rather than through your own compose files. The cost is coupling. You cannot drop umbrelOS into an existing Linux install, the hardware gates on Storage Manager, FailSafe and GPU acceleration are fixed by the OS rather than by what you install, and the licence restricts commercial redistribution in a way that the Debian and Docker licences do not. Choose the distro route when you want to keep control of the boot and update layers, and umbrelOS when you want the appliance experience on hardware you own.
Maintenance and upgrade cost
The material supports a few concrete statements about upkeep. umbrelOS updates as a whole system, and the README says the self-installed image receives the same features and the same updates as the Umbrel Home and Umbrel Pro hardware. The beta channel is opt-in through Settings > Advanced settings, which means you can stay on the stable line and avoid the 2.0 beta churn until the planned September 22, 2026 release. The README does not document a downgrade path from the beta back to stable, so enabling that toggle is closer to a one-way move than the wording suggests. On the build side, the app framework documentation lives in a separate repository, so maintaining a private app means tracking that repository's manifest format rather than a format defined in this one. What is not in the material: any statement about release cadence beyond the three releases listed, any migration tooling between major versions, or any backup guidance for the OS volume itself.
Editorial conclusion
Adopt umbrelOS if you want a self-hosted app catalogue on a dedicated Intel or AMD box, a Raspberry Pi 5 booting from NVMe or USB, or a Proxmox VM, and you accept the PolyForm Noncommercial 1.0.0 terms for personal or nonprofit use. Do not adopt it if you need to layer it onto an existing Linux install (the README states it cannot be installed on top of one), if you plan to resell hardware with it preinstalled without contacting partner@umbrel.com, or if you depend on Storage Manager or FailSafe and have only one internal drive. Before committing, confirm your machine meets the dual-core, 4 GB RAM and 32 GB boot-drive minimums, check whether the 2.0 beta is still the only route to the features you want given the stable release is planned for September 22, 2026, and read LICENSE.md yourself rather than relying on the README's TL;DR.
Community notes