---
title: "Nirvati vs. Runtipi"
description: "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."
canonical_url: "https://nirvati.eu/compare/runtipi"
---

> Index of every page on this site: [llms.txt](https://nirvati.eu/llms.txt)

# 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.

<compare-table feature-label="Feature" label="Comparison of Runtipi and Nirvati" left="Runtipi" right="Nirvati">
<compare-row left="Open source (GPL-3.0)" right="Open source (AGPL-3.0)" title="License" winner="both">

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](https://github.com/runtipi/runtipi/blob/v4.12.0/LICENSE), [Runtipi app store license](https://github.com/runtipi/runtipi-appstore/blob/3042a43cf215d743b6a0b389ee4d3e6571fb9ff8/LICENSE), [Nirvati backend](https://gitlab.com/nirvati-ug/nirvati/backend)

</compare-row>

<compare-row left="On an existing 64-bit Linux system" right="Nirvati OS images, or on an existing Linux system" title="Installation">

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](https://runtipi.io/docs/quick-start), [Runtipi setup script](https://setup.runtipi.io)

</compare-row>

<compare-row left="10 GB" right="40 GB" title="Minimum disk space" winner="left">

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](https://runtipi.io/docs/quick-start)

</compare-row>

<compare-row left="Yes, with a local certificate authority, or Let's Encrypt for exposed apps" right="Yes, with trusted Let's Encrypt certificates" title="HTTPS" winner="right">

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](https://github.com/runtipi/runtipi/blob/v4.12.0/packages/backend/src/core/local-tls/local-tls.service.ts#L55), [Runtipi release notes](https://github.com/runtipi/runtipi/releases/tag/v4.12.0), [Exposing apps in Runtipi](https://runtipi.io/docs/guides/expose-your-apps), [Nirvati certificate issuers](https://gitlab.com/nirvati-ug/nirvati/backend/-/blob/main/services/agent/src/ingress/domains/https/providers.rs)

</compare-row>

<compare-row left="No" right="Yes, a nirvati.me subdomain" title="Free domain" winner="right">

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.

</compare-row>

<compare-row left="Yes, per app, with a public IP address" right="Yes, with wildcard certificates" title="Your own domains" winner="right">

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](https://runtipi.io/docs/guides/expose-your-apps), [Runtipi DNS challenge guide](https://runtipi.io/docs/guides/dns-challenge-cloudflare)

</compare-row>

<compare-row left="Via apps or a Cloudflare Tunnel guide" right="Built in: Nirvati Connect or Tailscale" title="VPN for remote access" winner="right">

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](https://runtipi.io/docs/guides/expose-apps-with-cloudflare-tunnels)

</compare-row>

<compare-row left="No" right="Yes, with Nirvati OS" title="Multi-server support" winner="right">

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](https://github.com/runtipi/runtipi/blob/v4.12.0/README.md)

</compare-row>

<compare-row left="Docker Compose applied as written, the rest is up to store review" right="Enforced by Nirvati" title="App permissions & isolation" winner="right">

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](https://github.com/runtipi/runtipi/blob/v4.12.0/packages/backend/src/modules/docker/builders/compose.builder.ts#L121-L180), [Runtipi compose schema](https://github.com/runtipi/runtipi/blob/v4.12.0/packages/common/src/schemas/dynamic-compose-ark.ts), [Runtipi app store](https://github.com/runtipi/runtipi-appstore/tree/3042a43cf215d743b6a0b389ee4d3e6571fb9ff8/apps), [Nirvati permission checks](https://gitlab.com/nirvati-ug/nirvati/backend/-/blob/main/services/core/src/apps/validator/permissions.rs), [Nirvati install permissions](https://gitlab.com/nirvati-ug/nirvati/backend/-/blob/main/services/api/src/graphql/mutation/apps.rs)

</compare-row>

<compare-row left="No, one account" right="Yes, each user with their own apps" title="Multi-user support" winner="right">

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](https://github.com/runtipi/runtipi/blob/v4.12.0/packages/backend/src/modules/auth/auth.service.ts#L136-L170), [Runtipi guest dashboard](https://github.com/runtipi/runtipi/blob/v4.12.0/packages/backend/src/app.controller.ts#L26-L35), [Nirvati app namespaces](https://gitlab.com/nirvati-ug/nirvati/backend/-/blob/main/shared/common/src/kubernetes.rs)

</compare-row>

<compare-row left="No" right="Yes" title="Passkeys" winner="right">

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

Source: [Runtipi login](https://github.com/runtipi/runtipi/blob/v4.12.0/packages/backend/src/modules/auth/auth.service.ts)

</compare-row>

<compare-row left="Yes, per app" right="No, app snapshots only" title="Integrated backups" winner="left">

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](https://github.com/runtipi/runtipi/blob/v4.12.0/packages/backend/src/modules/backups/backups.controller.ts#L47), [Runtipi app updates](https://github.com/runtipi/runtipi/blob/v4.12.0/packages/backend/src/modules/app-lifecycle/app-lifecycle.controller.ts#L75)

</compare-row>

<compare-row left="No" right="Yes" title="Storage limits for apps" winner="right">

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](https://github.com/runtipi/runtipi/blob/v4.12.0/packages/backend/src/modules/docker/builders/compose.builder.ts#L121-L180)

</compare-row>

<compare-row left="About 260" right="34 in FOSS Apps" title="Apps in the official app store" winner="left">

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](https://github.com/runtipi/runtipi-appstore/blob/3042a43cf215d743b6a0b389ee4d3e6571fb9ff8/README.md), [Runtipi maintainers on the app store](https://github.com/runtipi/runtipi/issues/2317#issuecomment-3217972183), [Nirvati app store](https://apps.nirvati.eu)

</compare-row>

<compare-row left="Yes" right="Yes" title="Third-party app stores" winner="both">

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](https://runtipi.io/docs/learn/apps-and-app-store)

</compare-row>

<compare-row left="No" right="Yes, from umbrelOS and Tipi" title="Apps from other platforms" winner="right">

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](https://gitlab.com/nirvati-ug/nirvati/backend/-/blob/main/plugins/tipi/src/convert.rs)

</compare-row>

<compare-row left="No" right="Yes" title="Choosing an app's version when installing" winner="right">

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](https://runtipi.io/docs/learn/apps-and-app-store)

</compare-row>

<compare-row left="Docker" right="Kubernetes" title="Base system">

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](https://github.com/runtipi/runtipi/blob/v4.12.0/README.md)

</compare-row>
</compare-table>

## 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.

<compare-table feature-label="Area" label="Comparison of the security architecture of Runtipi and Nirvati" left="Runtipi" right="Nirvati">
<compare-row left="Main containers share one network" right="Own namespace per app, network policies" title="Isolation between apps" winner="right">

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](https://github.com/runtipi/runtipi/blob/v4.12.0/packages/backend/src/modules/docker/builders/compose.builder.ts#L140-L153), [Runtipi release notes](https://github.com/runtipi/runtipi/releases/tag/v4.12.0), [Nirvati network policies](https://gitlab.com/nirvati-ug/nirvati/backend/-/blob/main/services/core/src/apps/generator/kubernetes/networkpolicy.rs)

</compare-row>

<compare-row left="Decided by store review" right="Enforced when installing" title="Isolation from the host" winner="right">

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](https://github.com/runtipi/runtipi/blob/v4.12.0/packages/common/src/schemas/dynamic-compose-ark.ts), [Runtipi compose file](https://github.com/runtipi/runtipi/blob/v4.12.0/docker-compose.prod.yml), [Nirvati namespaces](https://gitlab.com/nirvati-ug/nirvati/backend/-/blob/main/shared/common/src/kubernetes.rs), [Nirvati permission checks](https://gitlab.com/nirvati-ug/nirvati/backend/-/blob/main/services/core/src/apps/validator/permissions.rs), [Nirvati Tipi compatibility](https://gitlab.com/nirvati-ug/nirvati/backend/-/blob/main/plugins/tipi/src/convert.rs)

</compare-row>

<compare-row left="Yes, optional per app" right="Yes" title="Login before opening an app" winner="both">

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](https://github.com/runtipi/runtipi/blob/v4.12.0/packages/backend/src/modules/docker/builders/traefik-labels.builder.ts#L40-L67)

</compare-row>

<compare-row left="One account" right="Separate apps, namespaces and permissions" title="Isolation between users" winner="right">

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](https://github.com/runtipi/runtipi/blob/v4.12.0/packages/backend/src/modules/auth/auth.service.ts#L136-L170)

</compare-row>

<compare-row left="Not built in" right="Nirvati Connect, signed by your server" title="Remote access" winner="right">

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](https://runtipi.io/docs/guides/expose-apps-with-cloudflare-tunnels)

</compare-row>

<compare-row left="Local certificate authority, Let's Encrypt for exposed apps" right="Let's Encrypt" title="Certificates" winner="right">

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](https://github.com/runtipi/runtipi/blob/v4.12.0/packages/backend/src/core/local-tls/local-tls.service.ts#L55), [Exposing apps in Runtipi](https://runtipi.io/docs/guides/expose-your-apps)

</compare-row>

<compare-row left="No" right="With Nirvati OS" title="Signed updates" winner="right">

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](https://setup.runtipi.io), [Runtipi release assets](https://github.com/runtipi/runtipi/releases/tag/v4.12.0), [Nirvati OS updates](https://gitlab.com/nirvati-ug/nirvati-os/-/blob/main/rust/nirvati-osd/src/update/mod.rs)

</compare-row>

<compare-row left="Up to your Linux system" right="Full disk encryption with Nirvati OS" title="Encryption at rest" winner="right">

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](https://github.com/runtipi/runtipi/blob/v4.12.0/packages/backend/src/modules/backups/backups.controller.ts#L47)

</compare-row>

<compare-row left="Not built in" right="Tor for apps with permission, onion domains" title="Tor" winner="right">

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.

</compare-row>
</compare-table>

## Sitemap

See the full [sitemap](https://nirvati.eu/sitemap.md) for all pages.
