Nirvati vs. Umbrel

Below, we compare Nirvati with Umbrel, another operating system for self-hosted servers. Nirvati is built in an open spirit, with free and open source licenses, and with a strong focus on security. We describe umbrelOS by facts you can check, with sources where possible. Where umbrelOS offers something Nirvati doesn't, we say so.

Select any row to read the details and our sources.

LicenseUmbrel: Source available, noncommercial use onlyNirvati: Open source (AGPL-3.0)

umbrelOS is licensed under the PolyForm Noncommercial License 1.0.0, which only permits noncommercial use. Nirvati is licensed under the AGPL-3.0, an open source license.

Sources: umbrelOS license, Nirvati backend

Terms of service restricting your useUmbrel: YesNirvati: No

Umbrel's terms of service cover umbrelOS and the Umbrel App Store. Among other things, they prohibit reverse engineering or analyzing Umbrel's products with the intent of creating a similar product. Nirvati itself has no terms of service.

Source: Umbrel terms of service

HTTPSUmbrel: Yes, with a local certificate authorityNirvati: Yes, with trusted Let's Encrypt certificates

umbrelOS serves its interface over HTTPS with certificates from its own local certificate authority. To avoid browser warnings, you download that certificate authority and install it on your devices.

Nirvati issues certificates from Let's Encrypt automatically, which every browser already trusts.

Sources: umbrelOS 2.0 release notes, umbrelOS LAN ingress, Nirvati certificate issuers

Free domainUmbrel: NoNirvati: Yes, a nirvati.me subdomain

During setup, Nirvati offers every user a free nirvati.me subdomain with HTTPS. The domain can point to your server's address in Nirvati Connect, Tailscale or your local network, so only your devices can reach it. umbrelOS has no built-in domain service.

Your own domainsUmbrel: NoNirvati: Yes, with wildcard certificates

In Nirvati, you can connect your own domain. With a DNS integration (for example Cloudflare, or Bunny.net through an app), Nirvati issues wildcard certificates, also when your server has no public IP address. umbrelOS doesn't support custom domains for its interface or apps.

Multi-server supportUmbrel: NoNirvati: Yes, with Nirvati OS

With Nirvati OS, you can add servers to your Nirvati from the dashboard. All servers form one cluster, your apps run across them, and with three control-plane servers, the cluster keeps working if one of them fails. umbrelOS runs on a single device.

Combining multiple disks (RAID)Umbrel: YesNirvati: No

umbrelOS can combine several internal drives into one storage space, or mirror them with FailSafe (RAID). Nirvati doesn't support this yet.

Source: umbrelOS 2.0 release notes

App permissions & isolationUmbrel: Folder choice per app, the rest is up to store reviewNirvati: Enforced by Nirvati

In umbrelOS, you can choose which of your folders an app gets. umbrelOS adds these folders as extra mounts. Everything else in the app's Docker Compose file, such as privileged containers, host networking, host folders or access to the Docker socket, is applied as written. Apps can also include hook scripts, which umbrelOS runs directly on the host. The umbrelOS daemon runs as root. Whether an app is allowed to do these things is decided when it is reviewed for the app store, not by umbrelOS.

In the official umbrelOS app store, at the time of writing, 98 apps include hooks, 15 use privileged containers, 27 use host networking and 7 have access to the Docker socket.

In Nirvati, every app runs in its own Kubernetes namespace. Nirvati works out which permissions an app needs from its definition: privileged containers, host folders, extra capabilities or host networking require built-in permissions, which you have to grant when you install the app, and only users with the right to install such apps can grant them. Network policies limit which apps can talk to each other, and apps can only use another app's services if they have the permission to.

Apps from the umbrelOS and Tipi compatibility layers run with the Privileged Pod Security level, but the permission system still applies to them: anything privileged that an app actually uses needs an explicit built-in permission granted at install. Hook scripts of umbrelOS apps run in an isolated container instead of on the host. The umbrelOS layer rejects apps that need the Docker socket, and the Tipi layer rejects options it doesn't support, such as the Docker socket, devices, deploy, security_opt, extra hosts and custom DNS.

Sources: umbrelOS app folder access, umbrelOS app script, umbrelOS service, umbrelOS app store, Nirvati permission checks, Nirvati install permissions, Nirvati network policies, Nirvati umbrelOS compatibility

Multi-user supportUmbrel: Yes, owner and member accountsNirvati: Yes

umbrelOS 2.0 added member accounts. Every account gets its own home screen and a private home folder. Nirvati supports multiple users, each with their own apps and domains.

Sources: umbrelOS 2.0 release notes, umbrelOS accounts

Who installs appsUmbrel: The ownerNirvati: Every user with the permission to

In umbrelOS, only the owner can install and uninstall apps. The owner can share apps with members, who then use the same app. In Nirvati, every user with the permission to manage apps installs their own apps.

Sources: umbrelOS app routes, umbrelOS app sharing

Separation between users' appsUmbrel: Members use the owner's shared appsNirvati: Each user's apps in their own namespace

In umbrelOS, there is one installation of each app, which the owner can share with members. In Nirvati, each user's apps run in their own Kubernetes namespace, with network policies between apps.

Source: Nirvati app namespaces

User rolesUmbrel: Owner and membersNirvati: Fine-grained permissions and groups

umbrelOS distinguishes between the owner and members. In Nirvati, you can give each user specific permissions, for example to manage apps, domains or users, and organize users in groups.

Integrated backupsUmbrel: Yes, encryptedNirvati: No, app snapshots only

umbrelOS includes a backup feature. Backups are stored in Kopia repositories that are protected with a password you set, so they are encrypted. Nirvati can take snapshots of apps, but doesn't have an integrated backup feature yet.

umbrelOS doesn't pass the password you set to Kopia directly. It first replaces it with the first 16 hexadecimal characters of its SHA-256 hash, which a code comment describes as a "128 bit hex string". 16 hexadecimal characters carry at most 64 bits, so the backup encryption is effectively limited to 64 bits of password strength, even if your password is stronger. Kopia then applies its own key stretching (scrypt) to this value.

Source: umbrelOS backups

VPN for remote accessUmbrel: Via app store (Tailscale)Nirvati: Built in: Nirvati Connect or Tailscale

On umbrelOS, you install Tailscale from the app store. Nirvati includes Nirvati Connect, which is free without limits. Your server signs every change to your network, and the hosted service only relays encrypted data. Tailscale is supported as well.

Storage limits for appsUmbrel: NoNirvati: Yes

In Nirvati, each app's storage has a size, so a single app can't fill up your disk. umbrelOS has no storage limits per app.

PasskeysUmbrel: NoNirvati: Yes

Nirvati supports signing in with passkeys. umbrelOS doesn't.

Third-party app storesUmbrel: Yes, in a separate viewNirvati: Yes, fully integrated

umbrelOS shows community app stores in a separate view. In Nirvati, third-party app stores are part of the system's main app store.

Apps from other platformsUmbrel: NoNirvati: Yes, from umbrelOS and Tipi

Nirvati can run apps from umbrelOS app stores and Tipi apps through compatibility apps.

Choosing an app's version when installingUmbrel: NoNirvati: Yes

In umbrelOS, apps are installed and updated to the version in the app store. In Nirvati, you can choose which version of an app to install.

Virtual machinesUmbrel: YesNirvati: No

umbrelOS can run virtual machines, for example Windows or Ubuntu, with Machines. Nirvati can't.

Source: umbrelOS 2.0 release notes

Reproducible buildsUmbrel: YesNirvati: Not yet (planned)

Starting with the 2.1 beta, every umbrelOS image, update and installer can be rebuilt from source and compared byte for byte. Reproducible builds are planned for Nirvati OS, but not available yet.

Source: umbrelOS 2.1 Beta 1 release notes

Base systemUmbrel: DockerNirvati: Kubernetes

umbrelOS runs apps with Docker on a single device. Nirvati runs apps on Kubernetes, which makes multi-server setups and isolation between apps possible.

ImagesUmbrel: x86_64 PCs, Raspberry Pi, Umbrel hardwareNirvati: UEFI PCs (x86_64, arm64), Raspberry Pi, Radxa Orion O6N

umbrelOS offers images for x86_64 PCs, including Umbrel's own hardware, and for Raspberry Pi. Nirvati OS offers images for PCs and servers with UEFI (x86_64 and arm64), Raspberry Pi and Radxa Orion O6N.

Security architecture

The table above compares single features. This section looks at how both systems are built to keep your server, your apps and your data safe.

Isolation between appsUmbrel: Shared Docker network by defaultNirvati: Own namespace per app, network policies

On umbrelOS, apps run as Docker containers on one host and are attached to a shared Docker network by default.

On Nirvati, every app runs in its own Kubernetes namespace. Cilium network policies define which apps and services an app can reach, and an app can only use another app's services if it has the permission to.

Sources: umbrelOS compose defaults, Nirvati network policies

Isolation from the hostUmbrel: Decided by store reviewNirvati: Enforced when installing

On umbrelOS, an app's Docker Compose file can use privileged containers, host networking, host folders or the Docker socket, and hook scripts run on the host. umbrelOS applies these as written.

On Nirvati, each app's namespace gets a Kubernetes Pod Security level. Privileged containers, host folders, extra capabilities and host networking require built-in permissions that you grant when you install the app, and only users who may install such apps can grant them. Apps from the umbrelOS and Tipi compatibility layers run with the Privileged Pod Security level, but anything privileged they actually use still needs such a permission. Hook scripts of umbrelOS apps run in an isolated container.

Sources: umbrelOS app script, Nirvati namespaces, Nirvati permission checks, Nirvati umbrelOS compatibility

Login before opening an appUmbrel: YesNirvati: Yes

Both systems can ask you to sign in before an app opens. On umbrelOS, this is handled by its app gateway. On Nirvati, you can protect an app, so anyone opening it first signs in with their Nirvati account.

Source: umbrelOS app gateway

Isolation between usersUmbrel: Private home folders, shared appsNirvati: Separate apps, namespaces and permissions

On umbrelOS, every member has a private home folder, and uses the apps the owner shares with them. On Nirvati, each user installs their own apps into their own namespaces, and what a user may do is controlled by fine-grained permissions.

Remote accessUmbrel: Tailscale app or TorNirvati: Nirvati Connect, signed by your server

On umbrelOS, you reach your server remotely with the Tailscale app or over Tor.

With Nirvati Connect, your server signs every change to your private network, and devices only join with a code from your server. The hosted service can't add devices or change rules, device names, IP addresses, policies, routes and DNS settings are encrypted, and traffic between devices is end-to-end encrypted with WireGuard. Tailscale is supported too.

CertificatesUmbrel: Local certificate authorityNirvati: Let's Encrypt

umbrelOS uses its own local certificate authority, which you install on your devices. Nirvati uses certificates from Let's Encrypt, which browsers already trust, for your nirvati.me domain and your own domains.

Signed updatesUmbrel: Yes, signed releases are verifiedNirvati: With Nirvati OS

umbrelOS checks that an update was signed by an approved key before installing it. Nirvati OS only installs an update if its manifest carries a valid signature from Nirvati's release key, which is built into the system. The manifest contains the SHA-256 checksums of all files of the update. On other Linux systems, Nirvati doesn't verify signatures of updates yet.

Sources: umbrelOS release signing, Nirvati OS updates

Encryption at restUmbrel: Not effectively encryptedNirvati: Full disk encryption with Nirvati OS

Nirvati OS encrypts the full disk. An installation of Nirvati on a standard Linux system is considered unencrypted.

On umbrelOS, storage setups with ZFS create the data dataset with AES-256-GCM encryption, but with a fixed default password that is the same on every device. A comment in the code says this doesn't provide any security and is meant to make full disk encryption possible later. The OS build doesn't set up any other disk encryption. App data at rest is therefore not effectively encrypted.

Source: umbrelOS storage setup

TorUmbrel: Tor proxy for apps, remote access over TorNirvati: Tor for apps with permission, onion domains

umbrelOS runs a Tor proxy that apps can use, and can make your server reachable over Tor. On Nirvati, the Tor support app lets apps send requests through Tor if they have the permission to, and you can add onion domains for your apps. Nirvati also sends telemetry through Tor, if you opted in.