Nirvati vs. StartOS

Below, we compare Nirvati with StartOS by Start9 Labs, 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 StartOS by facts you can check, with sources where possible. Where StartOS offers something Nirvati doesn't, we say so.

Select any row to read the details and our sources.

LicenseStartOS: Open source (MIT)Nirvati: Open source (AGPL-3.0)

StartOS is licensed under the MIT License, a permissive open source license. A few third-party files carry their own terms, and the Standard image includes proprietary firmware and drivers. A Slim image without any proprietary firmware is available too. Nirvati is licensed under the AGPL-3.0, a copyleft open source license.

Sources: StartOS license, StartOS third-party notices, Installing StartOS, Nirvati backend

HTTPSStartOS: Local certificate authority, Let's Encrypt for public domainsNirvati: Yes, with trusted Let's Encrypt certificates

For local and private addresses, StartOS uses certificates from its own certificate authority, which you install on each of your devices. For public domains, StartOS can get certificates from Let's Encrypt, as long as port 443 is reachable from the internet.

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

Sources: StartOS architecture, StartOS root CA, StartOS clearnet, Nirvati certificate issuers

Free domainStartOS: 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. StartOS has no built-in domain service. Start9's documentation suggests dynamic DNS from your router or a third-party service.

Source: StartOS inbound VPN

Your own domainsStartOS: Yes, DNS records set up by handNirvati: Yes, with DNS integrations and wildcard certificates

In StartOS, you can add your own domain to any service interface. You create the DNS records at your registrar yourself, and for a Let's Encrypt certificate, port 443 must be forwarded to your server or to your StartTunnel.

In Nirvati, you can connect your own domain too. 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.

Sources: StartOS clearnet, StartOS private domains

Multi-server supportStartOS: 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. StartOS manages a single server. StartTunnel can connect several StartOS servers to one virtual server, but they don't form a cluster.

Sources: StartOS architecture, StartTunnel

Multi-user supportStartOS: No, one master passwordNirvati: Yes, with fine-grained permissions

StartOS protects its interface with a single master password. It has no user accounts or roles. Family members use the accounts of the individual services.

Nirvati supports multiple users, each with their own apps and domains. You can give each user specific permissions, for example to manage apps, domains or users, and organize users in groups.

Sources: StartOS architecture, StartOS auth module, StartOS networking strategy

PasskeysStartOS: NoNirvati: Yes

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

Source: StartOS auth module

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

StartOS backs up your services to a drive or a network folder (SMB), encrypted with your master password. Services can leave out data that doesn't need a backup. Nirvati can take snapshots of apps, but doesn't have an integrated backup feature yet.

Sources: StartOS backups, StartOS architecture

VPN for remote accessStartOS: Your router's VPN, or StartTunnel on a server you rentNirvati: Built in: Nirvati Connect or Tailscale

StartOS doesn't include a hosted VPN. You can use your router's VPN server, or StartTunnel, a small router you install on a virtual server you rent (Start9 estimates about $5 to $10 per month). Everything then runs on infrastructure you control, and StartTunnel also works if your internet provider uses carrier-grade NAT.

Nirvati includes Nirvati Connect, which is free without limits and doesn't need a server of your own. Your server signs every change to your network, and the hosted service only relays encrypted data. Tailscale is supported as well.

Sources: StartOS remote access, StartOS CGNAT, StartTunnel, StartOS clearnet

Outgoing traffic through a VPNStartOS: Yes, for the whole system or per serviceNirvati: No

StartOS can send outgoing traffic through a WireGuard VPN, for example from a commercial VPN provider, either for the whole system or for individual services.

Nirvati can't route the outgoing traffic of apps through a VPN. Apps with the permission to can send their requests through Tor instead.

Sources: StartOS outbound VPN, StartOS architecture

GPU supportStartOS: Yes, with an NVIDIA imageNirvati: No

StartOS offers an image for x86_64 and ARM64 that includes the NVIDIA driver and container toolkit, so services can use an NVIDIA graphics card. Nirvati doesn't support GPUs for apps.

Source: Installing StartOS

Third-party app storesStartOS: YesNirvati: Yes, fully integrated

StartOS ships with two registries: the Start9 Registry, maintained by Start9, and the Community Registry. At the time of writing, they list 72 and 109 services. You can add more registries by their address, and anyone can run their own. In Nirvati, third-party app stores are part of the system's main app store, and you can host your own app store with the Nirvati App Store app.

Sources: StartOS default registries, StartOS alternative registries, Start9 Registry, Community Registry

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

StartOS only installs services in its own package format (s9pk). Nirvati can run apps from umbrelOS app stores and Tipi apps through compatibility apps.

Source: StartOS architecture

Choosing an app's version when installingStartOS: YesNirvati: Yes

In StartOS, you can pick from all versions of a service in the marketplace, and you can downgrade if the older version can take over the service's data. In Nirvati, you can choose which version of an app to install.

Sources: StartOS marketplace versions, StartOS installing

Installing the same app twiceStartOS: NoNirvati: Yes, for apps that support it

In StartOS, each service can be installed once per server. A second copy needs your own fork of the package under a different ID.

In Nirvati, you can install a second copy of an app if the app supports it, for example WordPress, Zitadel or LNbits. Each copy has its own name and its own data. Different users can also each install the same app for themselves.

Sources: StartOS installing, StartOS FAQ, Nirvati app validation, Nirvati app installation

Base systemStartOS: LXC containersNirvati: Kubernetes

StartOS runs each service in its own LXC container on a single device, without Docker. Nirvati runs apps on Kubernetes, which makes multi-server setups and network policies between apps possible.

Source: StartOS architecture

ImagesStartOS: x86_64, ARM64, RISC-V, Raspberry Pi 4, Start9 hardwareNirvati: UEFI PCs (x86_64, arm64), Raspberry Pi, Radxa Orion O6N

StartOS offers images for x86_64 and ARM64, each also as a version without proprietary firmware and as a version with NVIDIA drivers, as well as images for RISC-V and the Raspberry Pi 4. Start9 also sells its own servers. Nirvati OS offers images for PCs and servers with UEFI (x86_64 and arm64), Raspberry Pi and Radxa Orion O6N.

Sources: Installing StartOS, Start9 hardware

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 appsStartOS: Shared network bridge, ports reachable by other servicesNirvati: Own namespace per app, network policies

On StartOS, all service containers share one network bridge. Start9's packaging documentation says that every port a service opens can be reached by other services through the host, even if the service doesn't publish it as an interface. A package can protect a port with a password or token that StartOS checks, but StartOS doesn't control which services may talk to each other.

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: StartOS service-to-service networking, StartOS proxy authentication, StartOS firewall rules, Nirvati network policies

Isolation from the hostStartOS: Unprivileged container per service, no exceptionsNirvati: Enforced when installing, exceptions only with your permission

On StartOS, every service runs in an unprivileged LXC container with its own user namespace and an AppArmor profile. The package format has no way to request privileged mode, host networking or folders of the host. A service only gets its own volumes and those of the services it depends on, and packages can't run scripts on the host.

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.

Sources: StartOS container configuration, StartOS package manifest, StartOS mounts, Nirvati namespaces, Nirvati permission checks, Nirvati install permissions

Login before opening an appStartOS: Only a password or token set by the packageNirvati: Yes, with your Nirvati account

StartOS has no login in front of service interfaces. Services use their own logins, and a package can protect an interface with a password or token that StartOS checks. On Nirvati, you can protect an app, so anyone opening it first signs in with their Nirvati account.

Source: StartOS proxy authentication

Remote accessStartOS: StartTunnel on your own serverNirvati: Nirvati Connect, signed by your server

With StartTunnel, the whole connection runs on a virtual server you rent and control, and HTTPS ends at your own service. Your hosting provider can see metadata about your traffic.

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.

Sources: StartTunnel, StartOS clearnet

CertificatesStartOS: Local certificate authorityNirvati: Let's Encrypt

For local and private addresses, StartOS uses its own 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.

Source: StartOS root CA

Signed apps and updatesStartOS: Yes, with keys you choose to trustNirvati: Not yet (planned)

Every StartOS package and every StartOS update is signed. You decide which signing keys you trust, separately for apps and for system updates. StartOS blocks system updates from keys you don't trust and asks before installing an app from such a key. Installation images come with checksums and signatures. Nirvati doesn't verify signatures of apps or updates yet. This is planned.

Sources: StartOS trusted keys, StartOS updates, StartOS update signers

Encryption at restStartOS: NoNirvati: Full disk encryption with Nirvati OS

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

Start9's documentation says that the master password doesn't encrypt the data drive, so anyone holding the server or its drive can read every service's data. Backups made with StartOS are encrypted.

Source: StartOS architecture

TorStartOS: Tor service from the marketplace, onion addresses per serviceNirvati: Tor for apps with permission, onion domains

On StartOS, you install the Tor service from the marketplace and then add onion addresses to individual services. The Tor service runs the original Tor daemon, written in C, from Alpine Linux's packages. 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. The app uses Arti, the Tor Project's newer implementation written in Rust. Nirvati also sends telemetry through Tor, if you opted in.

Sources: StartOS Tor, StartOS Tor service, Nirvati Tor support app