Nirvati vs. Runtipi
Below, we compare Nirvati with Runtipi, an open source project that runs self-hosted apps with Docker on a Linux server and manages them through a web interface. Nirvati is built in an open spirit, with free and open source licenses, and with a strong focus on security. We describe Runtipi by facts you can check, with sources where possible. Where Runtipi offers something Nirvati doesn't, we say so. Nirvati can also run Tipi apps through its Tipi compatibility app.
Select any row to read the details and our sources.
LicenseRuntipi: Open source (GPL-3.0)Nirvati: Open source (AGPL-3.0)
Runtipi and its official app store are licensed under the GPL-3.0. Nirvati is licensed under the AGPL-3.0. Both are open source licenses.
Sources: Runtipi license, Runtipi app store license, Nirvati backend
InstallationRuntipi: On an existing 64-bit Linux systemNirvati: Nirvati OS images, or on an existing Linux system
Runtipi installs with a script on a 64-bit Linux system, including a Raspberry Pi, and installs Docker if it's missing. You keep your Linux distribution and maintain it yourself. Runtipi doesn't offer its own OS images.
Nirvati OS offers images for PCs and servers with UEFI (x86_64 and arm64), Raspberry Pi and Radxa Orion O6N. Nirvati can also be installed on an existing Linux system with systemd.
Sources: Runtipi quick start, Runtipi setup script
Minimum disk spaceRuntipi: 10 GBNirvati: 40 GB
Runtipi asks for at least 4 GB of RAM and 10 GB of disk space. For an installation on an existing system, Nirvati asks for at least 4 GB of RAM and 40 GB of disk space.
Source: Runtipi quick start
HTTPSRuntipi: Yes, with a local certificate authority, or Let's Encrypt for exposed appsNirvati: Yes, with trusted Let's Encrypt certificates
On your local network, Runtipi serves apps on a local domain with certificates from its own local certificate authority. To avoid browser warnings, you install that certificate authority on your devices. For apps you expose to the internet on your own domain, Runtipi gets certificates from Let's Encrypt, which requires forwarding ports 80 and 443 to your server.
Nirvati issues certificates from Let's Encrypt automatically, which every browser already trusts.
Sources: Runtipi local certificates, Runtipi release notes, Exposing apps in Runtipi, Nirvati certificate issuers
Free domainRuntipi: 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. Runtipi has no built-in domain service.
Your own domainsRuntipi: Yes, per app, with a public IP addressNirvati: Yes, with wildcard certificates
In Runtipi, you can expose an app on a domain you own. You point the domain to your public IP address and forward ports 80 and 443 to your server. A guide explains how to switch to Cloudflare's DNS challenge by editing the configuration.
In Nirvati, you connect your own domain in the dashboard. 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: Exposing apps in Runtipi, Runtipi DNS challenge guide
VPN for remote accessRuntipi: Via apps or a Cloudflare Tunnel guideNirvati: Built in: Nirvati Connect or Tailscale
Runtipi has no built-in remote access. You can install a VPN app such as Tailscale, or follow the guide for Cloudflare Tunnels. 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.
Source: Runtipi Cloudflare Tunnel guide
Multi-server supportRuntipi: 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. Runtipi runs on a single server.
Source: Runtipi README
App permissions & isolationRuntipi: Docker Compose applied as written, the rest is up to store reviewNirvati: Enforced by Nirvati
Runtipi installs apps from Docker Compose files. It adds networks, ports, labels and a restart policy, and applies everything else as written, such as privileged containers, host networking, host folders, devices or access to the Docker socket. Whether an app is allowed to do these things is decided when it is reviewed for an app store, not by Runtipi.
In the official Runtipi app store, at the time of writing, 8 of 266 apps use privileged containers, 10 use host networking and 13 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.
Sources: Runtipi compose builder, Runtipi compose schema, Runtipi app store, Nirvati permission checks, Nirvati install permissions
Multi-user supportRuntipi: No, one accountNirvati: Yes, each user with their own apps
Runtipi has a single account: once it exists, no further accounts can be registered. You can turn on a guest dashboard that lists your apps without signing in. In Nirvati, every user with the permission to manage apps installs their own apps, which run in their own Kubernetes namespaces. You can give each user specific permissions, for example to manage apps, domains or users, and organize users in groups.
Sources: Runtipi registration, Runtipi guest dashboard, Nirvati app namespaces
PasskeysRuntipi: NoNirvati: Yes
Nirvati supports signing in with passkeys. Runtipi doesn't.
Source: Runtipi login
Integrated backupsRuntipi: Yes, per appNirvati: No, app snapshots only
Runtipi can back up each app as an archive, optionally before every update, and restore it later. You can download and upload these archives. Nirvati can take snapshots of apps, but doesn't have an integrated backup feature yet.
Sources: Runtipi backups, Runtipi app updates
Storage limits for appsRuntipi: NoNirvati: Yes
In Nirvati, each app's storage has a size, so a single app can't fill up your disk. Runtipi doesn't add storage limits when it sets up an app.
Source: Runtipi compose builder
Apps in the official app storeRuntipi: About 260Nirvati: 34 in FOSS Apps
The official Runtipi app store has about 260 apps. It receives updates and fixes, and new apps are published in community app stores. In Nirvati, the FOSS Apps repository currently lists 34 apps.
Sources: Runtipi app store, Runtipi maintainers on the app store, Nirvati app store
Third-party app storesRuntipi: YesNirvati: Yes
Runtipi can use several app stores at once, and lets you add custom apps. 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.
Source: Runtipi apps and app stores
Apps from other platformsRuntipi: NoNirvati: Yes, from umbrelOS and Tipi
Nirvati can run apps from umbrelOS app stores and Tipi apps through compatibility apps. The Tipi compatibility app converts Tipi app definitions into Nirvati apps. Tipi apps that use options it doesn't support, such as the Docker socket, devices, deploy, security_opt, extra hosts or custom DNS, can't be installed on Nirvati.
Source: Nirvati Tipi compatibility
Choosing an app's version when installingRuntipi: NoNirvati: Yes
In Runtipi, apps are installed and updated to the version in the app store. To go back, you restore a backup. In Nirvati, you can choose which version of an app to install.
Source: Runtipi apps and app stores
Base systemRuntipi: DockerNirvati: Kubernetes
Runtipi runs apps with Docker on a single server. Nirvati runs apps on Kubernetes, which makes multi-server setups and isolation between apps possible.
Source: Runtipi README
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 appsRuntipi: Main containers share one networkNirvati: Own namespace per app, network policies
On Runtipi, apps run as Docker containers on one host. Apps with several containers get their own network, but the main container of every app also joins a shared network with the reverse proxy, so apps can reach each other there. Runtipi's own database and queue run on a separate internal network.
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: Runtipi compose builder, Runtipi release notes, Nirvati network policies
Isolation from the hostRuntipi: Decided by store reviewNirvati: Enforced when installing
On Runtipi, an app's Docker Compose file can use privileged containers, host networking, host folders, devices or the Docker socket, and Runtipi applies these as written. Runtipi and its reverse proxy access the Docker socket to manage apps.
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 Tipi compatibility app run with the Privileged Pod Security level, but anything privileged they actually use still needs such a permission, and apps that need the Docker socket or devices aren't converted.
Sources: Runtipi compose schema, Runtipi compose file, Nirvati namespaces, Nirvati permission checks, Nirvati Tipi compatibility
Login before opening an appRuntipi: Yes, optional per appNirvati: Yes
Both systems can ask you to sign in before an app opens. In Runtipi, you can turn on authentication for an app's domain, so visitors sign in to Runtipi first. This applies to the app's domain, not to access through a port of your server. On Nirvati, you can protect an app, so anyone opening it first signs in with their Nirvati account.
Source: Runtipi Traefik labels
Isolation between usersRuntipi: One accountNirvati: Separate apps, namespaces and permissions
Runtipi has a single account, so there is nothing to separate between users. On Nirvati, each user installs their own apps into their own namespaces, and what a user may do is controlled by fine-grained permissions.
Source: Runtipi registration
Remote accessRuntipi: Not built inNirvati: Nirvati Connect, signed by your server
Runtipi has no built-in remote access. You set up a VPN app or a Cloudflare Tunnel yourself.
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.
Source: Runtipi Cloudflare Tunnel guide
CertificatesRuntipi: Local certificate authority, Let's Encrypt for exposed appsNirvati: Let's Encrypt
On your local network, Runtipi uses its own local certificate authority, which you install on your devices. For apps exposed on your own domain, it uses Let's Encrypt. Nirvati uses certificates from Let's Encrypt, which browsers already trust, for your nirvati.me domain and your own domains.
Sources: Runtipi local certificates, Exposing apps in Runtipi
Signed updatesRuntipi: NoNirvati: With Nirvati OS
Runtipi's setup script downloads the Runtipi command line tool from GitHub without checking a checksum or signature, and its releases don't include checksums or signatures. 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: Runtipi setup script, Runtipi release assets, Nirvati OS updates
Encryption at restRuntipi: Up to your Linux systemNirvati: Full disk encryption with Nirvati OS
Nirvati OS encrypts the full disk. An installation of Nirvati on a standard Linux system is considered unencrypted.
Runtipi runs on a Linux system you set up yourself, so whether your disk is encrypted depends on that system. Runtipi doesn't encrypt app data itself, and its app backups are archives without encryption.
Source: Runtipi backups
TorRuntipi: Not built inNirvati: Tor for apps with permission, onion domains
Runtipi has no built-in Tor support. 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.