---
title: "Nirvati vs. Cloudron"
description: "Below, we compare Nirvati with Cloudron, a commercial platform by Cloudron UG for installing and managing web apps on your own server. Nirvati is built in an open spirit, with free and open source licenses, and with a strong focus on security. We describe Cloudron by facts you can check, with sources where possible. Cloudron is ahead of Nirvati in several areas, for example backups, email and single sign-on, and we say so in each of them."
canonical_url: "https://nirvati.eu/compare/cloudron"
---

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

# Nirvati vs. Cloudron

Below, we compare Nirvati with Cloudron, a commercial platform by Cloudron UG for installing and managing web apps on your own server. Nirvati is built in an open spirit, with free and open source licenses, and with a strong focus on security. We describe Cloudron by facts you can check, with sources where possible. Cloudron is ahead of Nirvati in several areas, for example backups, email and single sign-on, and we say so in each of them.

Select any row to read the details and our sources.

<compare-table feature-label="Feature" label="Comparison of Cloudron and Nirvati" left="Cloudron" right="Nirvati">
<compare-row left="Source available, production use requires a subscription" right="Open source (AGPL-3.0)" title="License" winner="right">

The Cloudron platform is published under the Cloudron Subscription license. You may only use it in production with a valid Cloudron subscription, and you may only use your own modifications with a subscription, too. Copying and distributing the software isn't allowed. Using it for development and testing is free. Cloudron's README states that its source-available license is not the same as an open source license. Cloudron's app packages are published separately, for example the Nextcloud package under the MIT license.

Nirvati is licensed under the AGPL-3.0, an open source license.

Sources: [Cloudron license](https://git.cloudron.io/platform/box/-/blob/v10.1.6/LICENSE), [Cloudron README](https://git.cloudron.io/platform/box/-/blob/v10.1.6/README.md#L54-L55), [Cloudron Nextcloud package license](https://git.cloudron.io/packages/nextcloud-app/-/blob/master/LICENSE), [Nirvati backend](https://gitlab.com/nirvati-ug/nirvati/backend)

</compare-row>

<compare-row left="Free plan, Pro from 15 € per month, Max from 25 € per month" right="No subscription required" title="Price" winner="right">

Cloudron's pricing page lists three plans. The free plan includes two apps. Pro costs 15 € per month billed yearly, or 30 € billed monthly, and allows unlimited apps. Max costs 25 € per month billed yearly, or 50 € billed monthly, and adds user groups and roles, the directory server, multiple backup sites and VPN-only access to apps. Prices exclude VAT. According to the pricing page, all plans include app updates, per-app backups, a firewall, email and single sign-on. If a subscription ends, Cloudron and its apps keep running, but no longer receive updates.

Cloudron's code contains default limits that apply until the subscription state has been loaded from Cloudron's servers: two apps, five users, one domain, five mailboxes and one backup site. A code comment says these defaults are adjusted once the subscription state is known; the actual limits per plan come from Cloudron's servers.

Nirvati is licensed under the AGPL-3.0 and doesn't need a subscription to run.

Sources: [Cloudron pricing](https://www.cloudron.io/pricing.html), [Cloudron plan defaults](https://git.cloudron.io/platform/box/-/blob/v10.1.6/src/appstore.js#L28-L46), [Cloudron updates](https://docs.cloudron.io/updates/)

</compare-row>

<compare-row left="Yes" right="No" title="Terms of service restricting your use" winner="right">

Cloudron's terms of service apply to its subscriptions. Among other things, they prohibit attempting to reverse engineer or otherwise derive the source code, and they allow Cloudron to end access at any time. Nirvati itself has no terms of service.

Source: [Cloudron terms of service](https://www.cloudron.io/legal/terms.html)

</compare-row>

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

Cloudron needs a domain of your own. 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.

Source: [Cloudron domains](https://docs.cloudron.io/domains/)

</compare-row>

<compare-row left="Yes, with wildcard certificates" right="Yes, with wildcard certificates" title="Your own domains" winner="both">

Cloudron integrates with about 20 DNS providers, such as Cloudflare, deSEC, Hetzner, Porkbun and Route 53, and issues wildcard certificates from Let's Encrypt through them. Without a DNS integration, it can validate certificates over HTTP. In Cloudron's code, the default limit before the subscription state is loaded is one domain (see the price row).

In Nirvati, you can connect your own domains and get Let's Encrypt certificates automatically. With a DNS integration (Cloudflare built in, or Bunny.net through an app), Nirvati issues wildcard certificates, also when your server has no public IP address.

Sources: [Cloudron domains](https://docs.cloudron.io/domains/), [Cloudron plan defaults](https://git.cloudron.io/platform/box/-/blob/v10.1.6/src/appstore.js#L28-L46), [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="Self-hosted VPN app, VPN-only access with Max" right="Built in: Nirvati Connect or Tailscale" title="VPN for remote access" winner="right">

Cloudron offers a VPN server app with OpenVPN and WireGuard. Your server has to be reachable from the internet for it. With the Max plan, you can make individual apps reachable only through a VPN or from allowed IP addresses.

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.

Sources: [Cloudron network docs](https://docs.cloudron.io/network/), [Cloudron installation](https://docs.cloudron.io/installation/), [Cloudron pricing](https://www.cloudron.io/pricing.html)

</compare-row>

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

A Cloudron installation runs on one server, and according to Cloudron staff, a subscription can only be active on one server at a time. You can move to a new server through a backup.

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.

Sources: [Cloudron forum on licensing](https://forum.cloudron.io/topic/2753/cloudron-pricing-and-licensing-help/9), [Cloudron backups](https://docs.cloudron.io/backups/)

</compare-row>

<compare-row left="198 in the App Store, plus community apps" right="34 in FOSS Apps, plus Nirvati Essentials, umbrelOS and Tipi apps" title="Number of apps">

At the time of writing, the Cloudron App Store lists 198 apps, all packaged by Cloudron. Community apps that other developers publish can be added as well.

At the time of writing, Nirvati's FOSS Apps repository lists 34 apps. Nirvati Essentials and the umbrelOS and Tipi app stores add more.

Sources: [Cloudron App Store API](https://api.cloudron.io/api/v1/apps), [Cloudron apps docs](https://docs.cloudron.io/apps/)

</compare-row>

<compare-row left="Yes, added by URL, not reviewed by Cloudron" right="Yes, third-party app stores fully integrated" title="Community and third-party apps" winner="both">

In Cloudron, you can add a community app by pasting the address of its version file into the dashboard, and it then receives updates automatically. A directory lists community apps. Cloudron doesn't review them, and as a security measure, community apps can't use Cloudron's Docker add-on.

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. Each app shows its publisher, developers, permissions and version history.

Sources: [Cloudron publishing docs](https://docs.cloudron.io/packaging/publishing/), [Cloudron apps docs](https://docs.cloudron.io/apps/), [Cloudron app checks](https://git.cloudron.io/platform/box/-/blob/v10.1.6/src/apps.js#L1920)

</compare-row>

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

Cloudron apps are packaged specifically for Cloudron. Apps hosted elsewhere can be added to the dashboard as links. Nirvati can run apps from umbrelOS app stores and Tipi apps through compatibility apps.

</compare-row>

<compare-row left="Yes, with a URL parameter" right="Yes, in the app store" title="Choosing an app's version when installing" winner="right">

In Cloudron, you can install a specific version by adding its package version to the app's App Store address, and then turn off automatic updates for that app. In Nirvati, you choose which version of an app to install directly in the app store.

Source: [Cloudron apps docs](https://docs.cloudron.io/apps/)

</compare-row>

<compare-row left="Yes" right="Yes" title="Multi-user support" winner="both">

Both systems support multiple users. Cloudron has a built-in user directory, with mailboxes per user. In Nirvati, every user has their own apps and domains.

Source: [Cloudron user management](https://docs.cloudron.io/user-management/)

</compare-row>

<compare-row left="Admins, for everyone" right="Every user with the permission to" title="Who installs apps" winner="right">

In Cloudron, admins install apps for the whole server and decide which users or groups can access each app. In Nirvati, every user with the permission to manage apps installs their own apps.

Source: [Cloudron user management](https://docs.cloudron.io/user-management/)

</compare-row>

<compare-row left="Five roles and groups, with the Max plan" right="Fine-grained permissions and groups" title="User roles and groups" winner="right">

Cloudron has the roles user, user manager, mail manager, admin and owner, and groups to control who can access an app. According to the pricing page, user groups and roles are part of the Max plan.

In Nirvati, you can give each user specific permissions, for example to manage apps, domains or users, and organize users in groups.

Sources: [Cloudron user management](https://docs.cloudron.io/user-management/), [Cloudron pricing](https://www.cloudron.io/pricing.html)

</compare-row>

<compare-row left="Yes, with OpenID Connect and LDAP" right="No built-in SSO, login protection in front of apps" title="Single sign-on for apps" winner="left">

Cloudron has a built-in user directory with an OpenID Connect provider and an LDAP server. Apps can sign users in with their Cloudron account, and apps without their own login can be placed behind Cloudron's login. At the time of writing, 130 of the 198 apps in the App Store use one of these integrations. Cloudron can also connect to an external LDAP directory.

Nirvati doesn't have a built-in single sign-on provider for apps. You can protect an app, so anyone opening it first signs in with their Nirvati account. Keycloak and Zitadel are available as apps.

Sources: [Cloudron security policy](https://git.cloudron.io/platform/box/-/blob/v10.1.6/SECURITY.md), [Cloudron user management](https://docs.cloudron.io/user-management/), [Cloudron App Store API](https://api.cloudron.io/api/v1/apps)

</compare-row>

<compare-row left="Yes, with backup codes" right="Passkeys" title="Two-factor authentication and passkeys" winner="left">

Cloudron supports time-based codes with backup codes and passkeys, and admins can require two-factor authentication for all users.

Nirvati supports signing in with passkeys.

Sources: [Cloudron changelog](https://git.cloudron.io/platform/box/-/blob/v10.1.6/CHANGES), [Nirvati login](https://gitlab.com/nirvati-ug/nirvati/backend/-/blob/main/services/api/src/graphql/mutation/login.rs)

</compare-row>

<compare-row left="Yes, built in" right="Available as an app (Stalwart)" title="Email server" winner="left">

Cloudron includes a mail server with mailboxes, mailing lists, forwarding and spam filtering, and apps can send email through it. Nirvati doesn't include a mail server, but you can install the Stalwart mail server from the app store.

Sources: [Cloudron pricing](https://www.cloudron.io/pricing.html), [Cloudron changelog](https://git.cloudron.io/platform/box/-/blob/v10.1.6/CHANGES)

</compare-row>

<compare-row left="Yes, encrypted, to many destinations" right="No, app snapshots only" title="Integrated backups" winner="left">

Cloudron backs up each app and the whole system on a schedule, with retention rules, to S3-compatible storage, Backblaze B2, Google Cloud Storage, Cloudflare R2, network shares or local disks. Backups can be incremental and encrypted with AES-256, including file names. Cloudron checks their integrity, makes a backup before every update, and can restore, clone or move a whole server from a backup. Multiple backup destinations require the Max plan.

Nirvati can take snapshots of apps, but doesn't have an integrated backup feature yet.

Sources: [Cloudron backups](https://docs.cloudron.io/backups/), [Cloudron pricing](https://www.cloudron.io/pricing.html)

</compare-row>

<compare-row left="Automatic, with a backup before each update" right="From the dashboard" title="Updates" winner="left">

Cloudron can update the platform and apps automatically on a schedule. It makes a full backup before every platform update and doesn't update if the backup fails, and backs up each app before updating it. Individual apps can be excluded from automatic updates.

In Nirvati, the Updates page in the dashboard installs updates, including upgrades of Kubernetes. Updates that require intermediate versions are installed step by step. Nirvati doesn't install updates automatically. You start every update yourself, including updates of Nirvati OS.

Sources: [Cloudron updates](https://docs.cloudron.io/updates/), [Nirvati OS updates in Nirvati](https://gitlab.com/nirvati-ug/nirvati/backend/-/blob/main/services/agent/src/system_management/os_updates.rs)

</compare-row>

<compare-row left="2 GB RAM, 20 GB disk" right="4 GB RAM, 40 GB disk" title="Minimum hardware" winner="left">

Cloudron needs at least 2 GB of RAM and 20 GB of disk space. Nirvati needs at least 4 GB of RAM and 40 GB of disk space.

Source: [Cloudron installation](https://docs.cloudron.io/installation/)

</compare-row>

<compare-row left="x86_64 servers with Ubuntu" right="UEFI PCs (x86_64, arm64), Raspberry Pi, Radxa Orion O6N" title="Supported hardware" winner="right">

Cloudron installs with a script on a fresh Ubuntu server and only supports x86_64. According to its documentation, it doesn't support ARM, so it doesn't run on a Raspberry Pi. Several cloud providers offer ready-made Cloudron 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 a Linux system with systemd.

Sources: [Cloudron installation](https://docs.cloudron.io/installation/), [Cloudron setup script](https://git.cloudron.io/platform/box/-/blob/v10.1.6/scripts/cloudron-setup#L71)

</compare-row>

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

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

</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 Cloudron and Nirvati" left="Cloudron" right="Nirvati">
<compare-row left="Hardened containers, enforced by Cloudron" right="Permissions you grant, enforced by Nirvati" title="Isolation from the host" winner="both">

Cloudron runs every app in a Docker container with a read-only root file system, an AppArmor profile and no extra Linux capabilities. Apps can only request a few additional capabilities, for example for a VPN server or hardware video decoding, and folders from the host are only mounted if an admin configures them. No app gets the Docker socket: apps that start their own containers talk to a filtering proxy, which blocks privileged containers and only allows the app's own folders. Only the owner can install such apps. One app in the App Store, the Container Registry, runs as a privileged container without an AppArmor profile.

On Nirvati, each app's namespace gets a Kubernetes Pod Security level. Nirvati works out which permissions an app needs from its definition: 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. 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 and devices.

Sources: [Cloudron container settings](https://git.cloudron.io/platform/box/-/blob/v10.1.6/src/docker.js#L707-L824), [Cloudron Docker proxy](https://git.cloudron.io/platform/box/-/blob/v10.1.6/src/dockerproxy.js), [Cloudron app routes](https://git.cloudron.io/platform/box/-/blob/v10.1.6/src/routes/apps.js#L155), [Cloudron security docs](https://docs.cloudron.io/security/), [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 install permissions](https://gitlab.com/nirvati-ug/nirvati/backend/-/blob/main/services/api/src/graphql/mutation/apps.rs), [Nirvati Tipi compatibility](https://gitlab.com/nirvati-ug/nirvati/backend/-/blob/main/plugins/tipi/src/convert.rs)

</compare-row>

<compare-row left="One shared network, separate credentials" right="Own namespace per app, network policies" title="Isolation between apps" winner="right">

On Cloudron, all app containers are attached to the same Docker network, and the firewall only limits the rate of connections between them. Databases and other shared services are protected with separate credentials for each app.

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: [Cloudron network setup](https://git.cloudron.io/platform/box/-/blob/v10.1.6/src/platform.js#L47-L54), [Cloudron firewall](https://git.cloudron.io/platform/box/-/blob/v10.1.6/setup/start/cloudron-firewall.sh#L116-L121), [Cloudron security docs](https://docs.cloudron.io/security/), [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="Yes" right="Yes" title="Login before opening an app" winner="both">

Both systems can ask you to sign in before an app opens. On Cloudron, the proxy authentication add-on puts a login, including two-factor authentication, in front of apps without their own login. On Nirvati, you can protect an app, so anyone opening it first signs in with their Nirvati account.

Source: [Cloudron security policy](https://git.cloudron.io/platform/box/-/blob/v10.1.6/SECURITY.md)

</compare-row>

<compare-row left="Shared apps with access control" right="Separate apps, namespaces and permissions" title="Isolation between users" winner="right">

On Cloudron, users share the apps admins install, and access control decides who may use each app. According to Cloudron's documentation, admins can sign in to any app regardless of access control, and can reach user data through the file manager or web terminal.

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: [Cloudron user management](https://docs.cloudron.io/user-management/)

</compare-row>

<compare-row left="Public server, optional VPN app" right="Nirvati Connect, signed by your server" title="Remote access" winner="right">

Cloudron needs a server that is reachable from the internet on ports 80 and 443. For private access, you can install the VPN server app, and with the Max plan, limit apps to VPN users or allowed IP addresses.

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: [Cloudron installation](https://docs.cloudron.io/installation/), [Cloudron network docs](https://docs.cloudron.io/network/)

</compare-row>

<compare-row left="Let's Encrypt" right="Let's Encrypt" title="Certificates" winner="both">

Both systems get certificates from Let's Encrypt automatically, which browsers already trust, and both can issue wildcard certificates through a DNS integration.

Sources: [Cloudron domains](https://docs.cloudron.io/domains/), [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="Yes, for the platform" right="With Nirvati OS" title="Signed updates" winner="both">

Cloudron verifies a GPG signature on platform updates and on its release list before installing them. According to its documentation, the signing keys are kept offline. App images are downloaded by version tag. 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: [Cloudron updater](https://git.cloudron.io/platform/box/-/blob/v10.1.6/src/updater.js#L36-L142), [Cloudron security docs](https://docs.cloudron.io/security/), [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 server setup" right="Full disk encryption with Nirvati OS" title="Encryption at rest" winner="right">

Cloudron doesn't set up disk encryption itself. Whether your data is encrypted at rest depends on how your server or cloud provider is set up. Cloudron's backups can be encrypted (see the backups row).

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

</compare-row>

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

We didn't find Tor support in Cloudron. 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.
