Nirvati vs. Olares
Below, we compare Nirvati with Olares, 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 Olares by facts you can check, with sources where possible. Where Olares offers something Nirvati doesn't, we say so.
Select any row to read the details and our sources.
LicenseOlares: Unclear: AGPL-3.0 and the earlier Olares LicenseNirvati: Open source (AGPL-3.0)
The main license file in Olares' repository was changed to the AGPL-3.0 in August 2025. The repository also still contains the earlier Olares License, which only permits personal, non-commercial or internal business use, both in its root folder and for its core app package. We found no statement from Olares on which of the two applies to which parts. Nirvati is licensed under the AGPL-3.0, an open source license.
Sources: Olares AGPL license, Olares license change, Olares License file, Olares License in the core package, Nirvati backend
HTTPSOlares: Yes, certificate and private key issued by Olares' serviceNirvati: Yes, Let's Encrypt certificates requested by your server
Olares serves its apps over HTTPS with trusted certificates. For your olares.com domain, your device asks Olares' cloud service to create a certificate, then downloads the certificate together with its private key. The private key for your domain is therefore created outside your server.
Nirvati requests certificates from Let's Encrypt automatically, with cert-manager running on your server, so the private key is created on your server.
Sources: Olares certificate manager, Olares service addresses, Nirvati certificate issuers
Free domainOlares: Yes, an olares.com subdomainNirvati: Yes, a nirvati.me subdomain
Every Olares ID comes with a subdomain of olares.com, and apps get HTTPS addresses below it. 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.
Source: Olares network: endpoints
Your own domainsOlares: Through Olares Space before activation, or per public appNirvati: Yes, with wildcard certificates
To use your own domain for all of Olares, you create an organization in Olares Space and delegate your domain's DNS to Olares' Cloudflare account. This has to happen before you activate Olares, so a device that is already activated has to be reset. You can also give single apps your own domain, but only apps that are public without Olares login, and you upload a certificate and its private key yourself.
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.
Sources: Olares custom domain setup, Olares DNS delegation, Olares custom app domains
VPN for remote accessOlares: Built in: LarePass VPNNirvati: Built in: Nirvati Connect or Tailscale
The LarePass VPN uses the Tailscale client, with a Headscale coordination server that runs on your own Olares. If no direct connection is possible, traffic goes through Tailscale's relay servers.
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: LarePass VPN, Olares Headscale deployment
Public access without a public IP addressOlares: Yes: Olares Tunnel, your own FRP server or Cloudflare TunnelNirvati: Only through Tor, with onion domains
Without a public IP address, Olares can make apps reachable through Olares Tunnel, a relay service run by Olares, through your own FRP server, or through Cloudflare Tunnel. With Olares Tunnel and FRP, the encrypted connection is forwarded to your device and ends there. Olares Tunnel traffic is part of the Olares Space plans, which include a free plan.
Nirvati can't make apps publicly reachable without a public IP address. Without one, you reach your apps through Nirvati Connect or Tailscale, and through onion domains, which anyone can open with Tor Browser.
Sources: Olares reverse proxy, Olares tunnel configuration, Olares Space plans, Olares Space billing
Multi-server supportOlares: Alpha, one main server with workersNirvati: Yes, with Nirvati OS
Olares can add worker servers in the same local network. Olares calls this feature alpha and doesn't recommend it for production. Setting it up uses the command line and requires experience with Kubernetes, and the cluster has a single main server.
With Nirvati OS, you add servers from the dashboard with a join code, as workers or control-plane servers. With three control-plane servers, the cluster keeps working if one of them fails, and servers in different networks can join through Nirvati Connect.
Source: Olares multi-node installation
Graphics cardsOlares: Yes, NVIDIA, shared across apps and serversNirvati: No
Olares supports NVIDIA graphics cards. It can share them between apps and across servers, split them by time or memory, and its Market offers many ready-to-use AI model apps. Olares also sells its own hardware with an NVIDIA graphics card. Nirvati doesn't have built-in support for graphics cards.
Sources: Olares README, Olares One specifications
Integrated backupsOlares: Yes, scheduled and password-protectedNirvati: No, app snapshots only
Olares backs up folders on a schedule, first in full and then incrementally, to a local drive, a network share, Olares Space, AWS S3 or Tencent COS. Backups are protected with a password. Of the apps, only Olares' own Wise app can be backed up so far. Nirvati can take snapshots of apps, but doesn't have an integrated backup feature yet.
Source: Olares backups
AccountsOlares: Olares ID, created in the LarePass appNirvati: Accounts on your Nirvati, created by an admin
To use Olares, every user needs an Olares ID, which you create in the LarePass mobile app. The link between your ID and its cryptographic identity is recorded on a blockchain. You activate Olares and confirm sign-ins with LarePass, and the domain of every user's Olares ID has to match the admin's.
In Nirvati, the first account is created during setup. Further accounts are created by an admin or by users with the permission to manage users. There is no self sign-up.
Sources: Olares account system, Olares self-sovereign network, Olares team management
Who installs appsOlares: Members install their own, admins also shared appsNirvati: Every user with the permission to
In Olares, members can install regular apps from the Market for themselves. Admins can also install shared apps, which run once for all users. In Nirvati, every user with the permission to manage apps installs their own apps.
Source: Olares roles and permissions
Separation between users' appsOlares: Each user's apps in their own namespaceNirvati: Each user's apps in their own namespace
In Olares, every community app runs in a Kubernetes namespace named after the app and the user, for example n8n-alice. In Nirvati, each user's apps also run in their own Kubernetes namespace, with network policies between apps.
Sources: Olares application namespaces, Nirvati app namespaces
User rolesOlares: Super admin, admins and membersNirvati: Fine-grained permissions and groups
Olares has three fixed roles. Members can install regular apps, admins also install shared apps, manage resources and update the system, and only the super admin manages admins. In Nirvati, you can give each user specific permissions, for example to manage apps, domains or users, and organize users in groups.
Source: Olares roles and permissions
CPU and memory limits per userOlares: YesNirvati: No
In Olares, admins assign each user a share of the server's CPU and memory, at least one core and 3 GB. Nirvati doesn't have CPU or memory limits per user. In Nirvati, each app's storage has a defined size.
Source: Olares team management
App permissions & isolationOlares: Checks at install, with an exception for Beclab's imagesNirvati: Enforced by Nirvati, with permissions you grant
When Olares installs or updates an app, it checks the app's definition. Apps can't change nodes or network policies, and host networking is blocked outside of system namespaces. Containers can't run privileged or as root, unless their image is published under Beclab's own beclab/ name. A comment in the source code says that Beclab's images are trusted to need these settings. Folders of the host are allowed.
In the official Olares Market, at the time of writing, 35 apps use privileged containers, for example Jellyfin and Home Assistant with images republished under beclab/. 21 apps mount system folders of the host, such as /dev, /proc, /sys or /etc, and one app has access to the host's container runtime.
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. 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: Olares install checks, Olares security context check, Olares host folder check, Olares install handler, Olares host network check, Olares app index, Nirvati permission checks, Nirvati install permissions
App store reviewOlares: Automatic checks, merged without manual reviewNirvati: Changes merged by the Nirvati team
Apps are added to the official Olares Market through pull requests on GitHub. A bot checks file scope, ownership and versions, and in the words of Olares' documentation, valid pull requests are merged automatically without manual review.
Nirvati's app store can require a review of every new version before it is published. The official repositories are maintained by the Nirvati team: changes are made through merge requests in Nirvati's GitLab repositories, are checked automatically, and are published once they are merged.
Sources: Distributing Olares apps, Nirvati app store reviews, Nirvati FOSS Apps repository
Third-party app storesOlares: Yes, each in its own tabNirvati: Yes, fully integrated
In Olares, you can add other app sources by URL, and apps from each source appear in their own tab. In Nirvati, third-party app stores are part of the system's main app store, and you can host your own app store.
Source: Olares Market
Apps from other platformsOlares: NoNirvati: Yes, from umbrelOS and Tipi
Olares apps are packaged in its own format, based on Helm charts. Nirvati can run apps from umbrelOS app stores and Tipi apps through compatibility apps.
Source: Distributing Olares apps
Choosing an app's version when installingOlares: Not documentedNirvati: Yes
Olares' documentation describes installing and updating apps to the version currently in the Market, and doesn't mention choosing another version. In Nirvati, you can choose which version of an app to install.
Source: Olares Market
System updatesOlares: From the LarePass app, by adminsNirvati: From the dashboard
Olares is updated from the LarePass mobile app, and only admins can do this. In Nirvati, you install updates on the Updates page of the dashboard, including upgrades of Kubernetes. Updates that need intermediate versions are installed step by step.
Source: Updating Olares
Base systemOlares: Kubernetes (k3s), KubeSphere, CalicoNirvati: Kubernetes (K3s or RKE2), Cilium
Both systems run apps on Kubernetes. Olares uses k3s by default, adds KubeSphere, and uses Calico for networking. Nirvati runs on K3s or RKE2 and uses Cilium for networking and network policies.
Sources: Olares system architecture, Olares installation options
ImagesOlares: x86-64 PCs, Raspberry Pi 4B/5, DGX Spark, Olares hardwareNirvati: UEFI PCs (x86_64, arm64), Raspberry Pi, Radxa Orion O6N
Olares offers an installation image for x86-64 PCs, an installation script for Ubuntu and Debian, Docker Compose, setups for Proxmox, LXC, Raspberry Pi 4B and 5 and NVIDIA DGX Spark, and its own Olares One hardware. Nirvati OS offers images for PCs and servers with UEFI (x86_64 and arm64), Raspberry Pi and Radxa Orion O6N.
Sources: Installing Olares, Olares on Raspberry Pi
Minimum hardwareOlares: 4 CPU cores, 8 GB RAM, 150 GB SSDNirvati: 4 GB RAM, 40 GB disk
Olares needs at least 4 CPU cores, 8 GB of memory and 150 GB of SSD storage, also on a Raspberry Pi, and its installation fails on a hard disk drive. Nirvati needs at least 4 GB of memory and 40 GB of disk space.
Sources: Olares README, Installing Olares
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 appsOlares: Own namespace per app, network policiesNirvati: Own namespace per app, network policies
Both systems run every app in its own Kubernetes namespace and use network policies between them.
On Olares, network policies only let traffic into an app from its owner's system services and gateway. Apps reach system services and other apps' APIs through permissions declared in their manifest, which a system service checks and forwards.
On Nirvati, 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: Olares network policies, Olares network, Olares application permissions, Nirvati network policies
Isolation from the hostOlares: Checked at install, except for Beclab's imagesNirvati: Enforced when installing, with your permission
On Olares, privileged and root containers are rejected when an app is installed, unless the image is published under beclab/. Folders of the host can be mounted. Host networking is blocked outside of system namespaces.
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.
Sources: Olares security context check, Olares host network check, Nirvati namespaces, Nirvati permission checks
Login before opening an appOlares: YesNirvati: Yes
Both systems can ask you to sign in before an app opens. On Olares, requests to private apps first pass Authelia, and only signed-in users reach the app. App entrances can also be public, or open without login over the LarePass VPN. On Nirvati, you can protect an app, so anyone opening it first signs in with their Nirvati account.
Isolation between usersOlares: Separate namespaces per user, fixed rolesNirvati: Separate apps, namespaces and permissions
On Olares, each user's apps and system services run in their own namespaces, and apps are isolated between users. What a user may do depends on one of three fixed roles. On Nirvati, each user installs their own apps into their own namespaces, and what a user may do is controlled by fine-grained permissions.
Sources: Olares network, Olares application namespaces
TLS certificates and private keysOlares: Key created by Olares' service and sent to your deviceNirvati: Generated on your server, never sent to us
On Olares, your device sends only its Olares name to Olares' service to request a certificate, then downloads both the certificate and its private key from that service. The private key for your Olares domain's certificate is created by Olares' service and sent to your device, so the service also holds a copy. Since the same service also manages the domain's DNS records and offers tunnel nodes, whoever holds that key could impersonate the server for that domain.
Nirvati requests certificates from Let's Encrypt through cert-manager on your server, which creates the private key there. For nirvati.me domains, the DNS integration only publishes the TXT record for the ACME challenge (DNS-01) and never handles keys.
Sources: Olares certificate manager, Olares service addresses, Nirvati certificates, nirvati.me DNS integration
Remote accessOlares: LarePass VPN, coordinated by your serverNirvati: Nirvati Connect, signed by your server
On Olares, the LarePass VPN is coordinated by a Headscale server that runs on your own Olares, and Tailscale's relay servers forward traffic when no direct connection is possible.
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: LarePass VPN, Olares Headscale
Signed updatesOlares: No, MD5 checksums onlyNirvati: With Nirvati OS
Olares checks downloaded system components against MD5 checksums listed in a manifest. We found no signature checks: the Olares daemon downloads the new command line tool without checking a checksum or signature. 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: Olares manifest types, Olares CLI download, Olares download helper, Nirvati OS updates
Encryption at restOlares: None foundNirvati: Full disk encryption with Nirvati OS
Nirvati OS encrypts the full disk. An installation of Nirvati on a standard Linux system is considered unencrypted. We didn't find any disk or storage encryption in Olares' source code.
Source: Olares source code