---
title: "Nirvati vs. CasaOS and ZimaOS"
description: "Below, we compare Nirvati with CasaOS and ZimaOS, both made by IceWhale Technology. CasaOS is installed on top of an existing Linux system, and ZimaOS is a complete operating system that grew out of CasaOS. Nirvati is built in an open spirit, with free and open source licenses, and with a strong focus on security. We describe CasaOS and ZimaOS by facts you can check, with sources where possible. Where the two differ, we list them separately, and where they offer something Nirvati doesn't, we say so."
canonical_url: "https://nirvati.eu/compare/casaos-zimaos"
---

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

# Nirvati vs. CasaOS and ZimaOS

Below, we compare Nirvati with CasaOS and ZimaOS, both made by IceWhale Technology. CasaOS is installed on top of an existing Linux system, and ZimaOS is a complete operating system that grew out of CasaOS. Nirvati is built in an open spirit, with free and open source licenses, and with a strong focus on security. We describe CasaOS and ZimaOS by facts you can check, with sources where possible. Where the two differ, we list them separately, and where they offer something Nirvati doesn't, we say so.

Select any row to read the details and our sources.

<compare-table feature-label="Feature" label="Comparison of CasaOS, ZimaOS and Nirvati" left="CasaOS / ZimaOS" right="Nirvati">
<compare-row left="CasaOS: Open source (Apache-2.0); ZimaOS: Source code not published" right="Open source (AGPL-3.0)" title="License" winner="right">

CasaOS is licensed under the Apache License 2.0, an open source license. ZimaOS is distributed as ready-made images. Its GitHub repository contains release notes, images and a security policy, but no source code for the operating system and no license. Some of its components come from CasaOS and are open source. Nirvati is licensed under the AGPL-3.0, an open source license.

Sources: [CasaOS license](https://github.com/IceWhaleTech/CasaOS/blob/0d3b2f444ec0193193cf03eef6d43c6e35b0183e/LICENSE), [ZimaOS repository](https://github.com/IceWhaleTech/ZimaOS/tree/1.8.0), [Nirvati backend](https://gitlab.com/nirvati-ug/nirvati/backend)

</compare-row>

<compare-row left="CasaOS: Free; ZimaOS: Free up to 4 disks and 3 members, ZimaOS+ for $29" right="Free" title="Price and limits" winner="right">

The free version of ZimaOS supports up to 4 disks and 3 members. ZimaOS+ removes these limits and costs 29 US dollars, as a lifetime license for one device. It's included with IceWhale's own hardware. CasaOS is free. Nirvati is free.

Source: [ZimaOS pricing](https://www.zimaspace.com/zimaos/pricing?sn=zimaos)

</compare-row>

<compare-row left="CasaOS: No, the dashboard uses HTTP; ZimaOS: Optional, with a certificate you have to trust yourself" right="Yes, with trusted Let's Encrypt certificates" title="HTTPS" winner="right">

CasaOS serves its dashboard over plain HTTP, and apps are opened directly on their own ports. ZimaOS can serve its dashboard over HTTPS with a certificate it generates for zimaos.local. Browsers only trust it after you import it on each device, and apps are still opened over plain HTTP on their own ports.

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

Sources: [CasaOS gateway](https://github.com/IceWhaleTech/CasaOS-Gateway/tree/606a84523802dde7269f10660c867d089e7ed660), [ZimaOS 1.4.2 release notes](https://github.com/IceWhaleTech/ZimaOS/releases/tag/1.4.2), [IceWhale forum: HTTPS on ZimaOS](https://community.zimaspace.com/t/help-with-https/5351), [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. CasaOS and ZimaOS have no built-in domain service.

</compare-row>

<compare-row left="Through apps" right="Yes, built in, with wildcard certificates" title="Your own domains" winner="right">

On CasaOS and ZimaOS, you can install an app such as Nginx Proxy Manager, point your domain to your public IP address and forward ports on your router. In Nirvati, you can connect your own domain directly. 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.

Source: [ZimaOS guide for Nginx Proxy Manager](https://github.com/IceWhaleTech/ZimaDocs/blob/653e3893bc3d809aa114344f8ece38b394025c7d/source/zimaos/app-store/nginx-proxy-manager-setup.md)

</compare-row>

<compare-row left="CasaOS: Through apps; ZimaOS: Built in, with ZimaClient" right="Built in: Nirvati Connect or Tailscale" title="Remote access" winner="both">

ZimaOS connects your devices through ZimaClient. According to IceWhale, ZimaClient uses ZeroTier, with the network controller running on your own device and ZeroTier's public servers used to find your devices. Remote access can be turned off. CasaOS has no built-in remote access, and on both systems you can install apps such as Tailscale or WireGuard.

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: [ZimaOS remote access](https://github.com/IceWhaleTech/ZimaDocs/blob/653e3893bc3d809aa114344f8ece38b394025c7d/source/zimaos/remote-access.md), [ZimaClient FAQ](https://github.com/IceWhaleTech/ZimaDocs/blob/653e3893bc3d809aa114344f8ece38b394025c7d/source/zimaos/zimaclient-install.md)

</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. CasaOS and ZimaOS each run on a single device. ZimaClient can switch between several ZimaOS devices.

Source: [ZimaOS remote access](https://github.com/IceWhaleTech/ZimaDocs/blob/653e3893bc3d809aa114344f8ece38b394025c7d/source/zimaos/remote-access.md)

</compare-row>

<compare-row left="CasaOS: No; ZimaOS: Yes, RAID 0/1/5/6, JBOD and ZFS" right="No" title="Combining multiple disks (RAID)" winner="left">

ZimaOS can combine disks with RAID 0, 1, 5 or 6 or as JBOD, and supports ZFS. CasaOS leaves this to the underlying Linux system. Nirvati doesn't support this yet.

Source: [ZimaOS features](https://github.com/IceWhaleTech/ZimaDocs/blob/653e3893bc3d809aa114344f8ece38b394025c7d/source/zimaos/features.md)

</compare-row>

<compare-row left="CasaOS: Compose file applied as written; ZimaOS: Source code not published" right="Enforced by Nirvati" title="App permissions & isolation" winner="right">

CasaOS installs apps from Docker Compose files. Privileged containers, host networking, host folders, devices or access to the Docker socket are applied as written in the file. The CasaOS system services run as root. In the official app store, automated checks only test that a file is valid, so whether an app gets these rights is decided when it is reviewed for the store. ZimaOS uses the same app store. We couldn't check how ZimaOS installs apps, because its source code isn't published.

In the official app store, at the time of writing, 8 of 182 apps use privileged containers, 18 use host networking, 18 get access to host devices and 7 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. Network policies limit which apps can talk to each other, and apps can only use another app's services if they have the permission to.

Apps from the umbrelOS and Tipi compatibility layers run with the Privileged Pod Security level, but the permission system still applies to them: anything privileged that an app actually uses needs an explicit built-in permission granted at install. 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, devices, `deploy`, `security_opt`, extra hosts and custom DNS.

Sources: [CasaOS app installation](https://github.com/IceWhaleTech/CasaOS-AppManagement/blob/debfa317f0f996b91b43210e8d57799461388704/service/compose_service.go#L45-L110), [CasaOS app management service](https://github.com/IceWhaleTech/CasaOS-AppManagement/blob/debfa317f0f996b91b43210e8d57799461388704/build/sysroot/usr/lib/systemd/system/casaos-app-management.service), [App store checks](https://github.com/IceWhaleTech/CasaOS-AppStore/blob/820f99007fd521d0b534d94366371debea2ed438/docs/cicd/validator-workflow.md), [Official app store](https://github.com/IceWhaleTech/CasaOS-AppStore/tree/820f99007fd521d0b534d94366371debea2ed438/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), [Nirvati network policies](https://gitlab.com/nirvati-ug/nirvati/backend/-/blob/main/services/core/src/apps/generator/kubernetes/networkpolicy.rs), [Nirvati Tipi compatibility](https://gitlab.com/nirvati-ug/nirvati/backend/-/blob/main/plugins/tipi/src/convert.rs)

</compare-row>

<compare-row left="CasaOS: One account; ZimaOS: Owner and members" right="Yes" title="Multi-user support" winner="right">

CasaOS supports a single account, which is created during setup. In ZimaOS, the first account is the owner, who can add members: up to 3 in the free version, and without a limit with ZimaOS+. Nirvati supports multiple users, each with their own apps and domains.

Sources: [CasaOS account setup](https://github.com/IceWhaleTech/CasaOS-UserService/blob/800c630c3443364cde142a9aadea0dc3880e6232/route/v1/user.go#L44-L80), [ZimaOS getting started](https://github.com/IceWhaleTech/ZimaDocs/blob/653e3893bc3d809aa114344f8ece38b394025c7d/source/zimaos/get-started.md), [ZimaOS pricing](https://www.zimaspace.com/zimaos/pricing?sn=zimaos)

</compare-row>

<compare-row left="CasaOS: The single account; ZimaOS: Not documented" right="Every user with the permission to" title="Who installs apps">

In CasaOS, the single account installs all apps. We couldn't find out from ZimaOS' documentation whether members can install their own apps. In Nirvati, every user with the permission to manage apps installs their own apps.

</compare-row>

<compare-row left="CasaOS: One admin account; ZimaOS: Owner and members" right="Fine-grained permissions and groups" title="User roles" winner="right">

CasaOS has a single admin account. ZimaOS distinguishes between the owner and members, and the owner can give members read or read-and-write access to each shared folder. In Nirvati, you can give each user specific permissions, for example to manage apps, domains or users, and organize users in groups.

Source: [ZimaOS shared folder permissions](https://github.com/IceWhaleTech/ZimaDocs/blob/653e3893bc3d809aa114344f8ece38b394025c7d/source/zimaos/samba-member-setup.md)

</compare-row>

<compare-row left="CasaOS: No; ZimaOS: Yes" right="No, app snapshots only" title="Integrated backups" winner="left">

ZimaOS includes a backup app that copies folders on a schedule between local disks, USB drives, other devices on your network and cloud storage, and keeps several versions. Nirvati can take snapshots of apps, but doesn't have an integrated backup feature yet.

Source: [ZimaOS 3-2-1 backup](https://github.com/IceWhaleTech/ZimaDocs/blob/653e3893bc3d809aa114344f8ece38b394025c7d/source/zimaos/how-to-use-3-2-1-backup-on-zimaos.md)

</compare-row>

<compare-row left="ZimaOS: SMB, Time Machine, device backups, photo library" right="No, apps like Nextcloud and Syncthing" title="File sharing and NAS features" winner="left">

ZimaOS shares folders over SMB with permissions per member, can be used as a Time Machine target, backs up phones and computers through ZimaClient, and includes a photo library with search. Nirvati doesn't share folders over SMB and has no built-in NAS features. For your files, you can install apps like Nextcloud or Syncthing.

Sources: [ZimaOS shared folder permissions](https://github.com/IceWhaleTech/ZimaDocs/blob/653e3893bc3d809aa114344f8ece38b394025c7d/source/zimaos/samba-member-setup.md), [ZimaOS Time Machine](https://github.com/IceWhaleTech/ZimaDocs/blob/653e3893bc3d809aa114344f8ece38b394025c7d/source/zimaos/time-machine-backup.md), [ZimaOS release notes](https://github.com/IceWhaleTech/ZimaOS/releases/tag/1.8.0)

</compare-row>

<compare-row left="CasaOS: No; ZimaOS: No" right="Passkeys" title="Two-factor authentication and passkeys" winner="right">

We found no two-factor authentication or passkeys in CasaOS. For ZimaOS, an answer in IceWhale's community forum from December 2025 says that it doesn't support two-factor authentication, and we found neither two-factor authentication nor passkeys in its release notes since then. Nirvati supports signing in with passkeys.

Sources: [CasaOS user service](https://github.com/IceWhaleTech/CasaOS-UserService/tree/800c630c3443364cde142a9aadea0dc3880e6232), [IceWhale forum: 2FA on ZimaOS](https://community.zimaspace.com/t/securing-zimaboard-2-2fa-setup-and-zerotier-vs-vpn-comparison/7316), [ZimaOS releases](https://github.com/IceWhaleTech/ZimaOS/releases), [Nirvati login](https://gitlab.com/nirvati-ug/nirvati/backend/-/blob/main/services/api/src/graphql/mutation/login.rs)

</compare-row>

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

At the time of writing, the official app store of CasaOS and ZimaOS contains 182 apps. Nirvati's FOSS Apps repository currently lists 34 apps, and Nirvati can also run apps from umbrelOS and Tipi app stores.

Source: [Official app store](https://github.com/IceWhaleTech/CasaOS-AppStore/tree/820f99007fd521d0b534d94366371debea2ed438/Apps)

</compare-row>

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

CasaOS and ZimaOS can add community app stores by their URL. In Nirvati, third-party app stores are part of the system's main app store, and you can also host your own app store.

Source: [Third-party app stores for CasaOS and ZimaOS](https://github.com/IceWhaleTech/CasaOS-AppStore/blob/820f99007fd521d0b534d94366371debea2ed438/docs/resources/recommended-third-party-stores.md)

</compare-row>

<compare-row left="Any Docker Compose file, adapted by hand" right="umbrelOS and Tipi apps, through compatibility apps" title="Apps from other sources">

CasaOS and ZimaOS can import any Docker Compose file as a custom app, which you can edit and adapt yourself. Nirvati can run apps from umbrelOS app stores and Tipi apps through compatibility apps.

Source: [ZimaOS features](https://github.com/IceWhaleTech/ZimaDocs/blob/653e3893bc3d809aa114344f8ece38b394025c7d/source/zimaos/features.md)

</compare-row>

<compare-row left="Only by editing the image tag" right="Yes" title="Choosing an app's version when installing" winner="right">

The app store of CasaOS and ZimaOS offers the current version of each app. You can change the container image tag in an app's settings yourself. In Nirvati, you can choose which version of an app to install.

Sources: [App store build output](https://github.com/IceWhaleTech/CasaOS-AppStore/blob/820f99007fd521d0b534d94366371debea2ed438/docs/specs/build-output.md), [ZimaOS release notes](https://github.com/IceWhaleTech/ZimaOS/releases/tag/1.5.1)

</compare-row>

<compare-row left="CasaOS: No; ZimaOS: Yes" right="No" title="Virtual machines" winner="left">

ZimaOS can run virtual machines with ZVM. Nirvati can't.

Source: [ZimaOS ZVM](https://github.com/IceWhaleTech/ZimaDocs/blob/653e3893bc3d809aa114344f8ece38b394025c7d/source/zimaos/zvm-next-virtual-machines-community-preview.md)

</compare-row>

<compare-row left="ZimaOS: Yes, two system partitions; CasaOS: Up to the Linux system" right="Nirvati OS: Yes, two system partitions with automatic rollback; otherwise: Up to the Linux system" title="Fallback after a system update" winner="right">

ZimaOS installs updates to a second system partition, and you can start the previous one if something goes wrong. Updates can also be installed offline. CasaOS is updated through its own scripts, and you update the underlying Linux system yourself. Nirvati OS installs updates to the second of two system partitions and first starts the new version on a trial basis. If it doesn't start or fails its health check, Nirvati OS automatically starts the previous version again. With several servers, Nirvati updates them one at a time. On other Linux systems, you take care of the underlying system yourself.

Sources: [ZimaOS system recovery](https://github.com/IceWhaleTech/ZimaDocs/blob/653e3893bc3d809aa114344f8ece38b394025c7d/source/zimaos/system-recovery.md), [ZimaOS offline updates](https://github.com/IceWhaleTech/ZimaDocs/blob/653e3893bc3d809aa114344f8ece38b394025c7d/source/zimaos/offline-install.md), [Nirvati OS updates](https://gitlab.com/nirvati-ug/nirvati-os/-/blob/main/rust/nirvati-osd/src/update/mod.rs)

</compare-row>

<compare-row left="Yes, Zima devices" right="No" title="Own hardware">

IceWhale sells ZimaBoard, ZimaBlade and ZimaCube devices, which come with ZimaOS and ZimaOS+. Nirvati runs on hardware you choose.

Source: [ZimaOS pricing](https://www.zimaspace.com/zimaos/pricing?sn=zimaos)

</compare-row>

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

CasaOS and ZimaOS run apps with Docker on a single device. Nirvati runs apps on Kubernetes, which makes multi-server setups and isolation between apps possible.

</compare-row>

<compare-row left="ZimaOS: x86_64 PCs with UEFI; CasaOS: Installs on Debian, Ubuntu or Raspberry Pi OS" right="UEFI PCs (x86_64, arm64), Raspberry Pi, Radxa Orion O6N" title="Images and platforms">

ZimaOS offers images for x86_64 PCs with UEFI, including IceWhale's own hardware. CasaOS installs on top of an existing Linux system on x86_64, arm64 or armv7. Nirvati OS offers images for PCs and servers with UEFI (x86_64 and arm64), Raspberry Pi and Radxa Orion O6N.

Sources: [ZimaOS downloads](https://github.com/IceWhaleTech/ZimaOS/releases/tag/1.8.0), [CasaOS README](https://github.com/IceWhaleTech/CasaOS/blob/0d3b2f444ec0193193cf03eef6d43c6e35b0183e/README.md)

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

## Security architecture

The table above compares single features. This section looks at how the systems are built to keep your server, your apps and your data safe. Where we could only check the CasaOS source code, because the ZimaOS source code isn't published, we say so.

<compare-table feature-label="Area" label="Comparison of the security architecture of CasaOS, ZimaOS and Nirvati" left="CasaOS / ZimaOS" right="Nirvati">
<compare-row left="Shared Docker network, ports published on the server" right="Own namespace per app, network policies" title="Isolation between apps" winner="right">

On CasaOS and ZimaOS, apps run as Docker containers on one host. Most apps in the official app store use Docker's default network and publish their ports on the server.

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: [Example app definition](https://github.com/IceWhaleTech/CasaOS-AppStore/blob/820f99007fd521d0b534d94366371debea2ed438/Apps/Jellyfin/docker-compose.yml), [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 CasaOS, an app's Docker Compose file can use privileged containers, host networking, host folders, devices or the Docker socket, and CasaOS applies these as written. Its system services run as root. ZimaOS uses the same app store, but we couldn't check how it installs 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 umbrelOS and Tipi compatibility layers run with the Privileged Pod Security level, but anything privileged they actually use still needs such a permission.

Sources: [CasaOS container settings](https://github.com/IceWhaleTech/CasaOS-AppManagement/blob/debfa317f0f996b91b43210e8d57799461388704/service/container.go#L541-L543), [CasaOS app management service](https://github.com/IceWhaleTech/CasaOS-AppManagement/blob/debfa317f0f996b91b43210e8d57799461388704/build/sysroot/usr/lib/systemd/system/casaos-app-management.service), [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)

</compare-row>

<compare-row left="No" right="Yes" title="Login before opening an app" winner="right">

On CasaOS and ZimaOS, you open apps directly on their own ports, and each app handles sign-in itself. A login in front of apps is only possible with an extra app, such as a reverse proxy you set up yourself. On Nirvati, you can protect an app, so anyone opening it first signs in with their Nirvati account.

Sources: [Example app definition](https://github.com/IceWhaleTech/CasaOS-AppStore/blob/820f99007fd521d0b534d94366371debea2ed438/Apps/Jellyfin/docker-compose.yml), [ZimaOS guide for Nginx Proxy Manager](https://github.com/IceWhaleTech/ZimaDocs/blob/653e3893bc3d809aa114344f8ece38b394025c7d/source/zimaos/app-store/nginx-proxy-manager-setup.md)

</compare-row>

<compare-row left="CasaOS: One account; ZimaOS: Folder permissions per member" right="Separate apps, namespaces and permissions" title="Isolation between users" winner="right">

CasaOS has a single account. On ZimaOS, the owner gives each member read or read-and-write access to shared folders, and apps run in one shared Docker installation. 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: [ZimaOS shared folder permissions](https://github.com/IceWhaleTech/ZimaDocs/blob/653e3893bc3d809aa114344f8ece38b394025c7d/source/zimaos/samba-member-setup.md), [Nirvati app namespaces](https://gitlab.com/nirvati-ug/nirvati/backend/-/blob/main/shared/common/src/kubernetes.rs)

</compare-row>

<compare-row left="CasaOS: MD5 without salt; ZimaOS: Source code not published" right="Argon2" title="Password storage" winner="right">

CasaOS stores account passwords as MD5 hashes without a salt. MD5 is fast to compute, so passwords are easier to recover from a copied database. We couldn't check ZimaOS, because its source code isn't published. Nirvati hashes passwords with Argon2, which is designed to be slow to compute.

Sources: [CasaOS user service](https://github.com/IceWhaleTech/CasaOS-UserService/blob/800c630c3443364cde142a9aadea0dc3880e6232/route/v1/user.go#L72), [Nirvati login](https://gitlab.com/nirvati-ug/nirvati/backend/-/blob/main/services/api/src/graphql/mutation/login.rs), [Nirvati setup](https://gitlab.com/nirvati-ug/nirvati/backend/-/blob/main/services/api/src/graphql/mutation/setup.rs)

</compare-row>

<compare-row left="ZimaOS: Yes, signed update bundles; CasaOS: Update script" right="With Nirvati OS" title="Signed updates" winner="both">

ZimaOS installs system updates as RAUC bundles. RAUC requires every bundle to be signed and checks the signature before it installs an update. We couldn't check which key ZimaOS uses, because its source code isn't published. CasaOS is installed and updated with a script that you download and run. 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: [ZimaOS downloads](https://github.com/IceWhaleTech/ZimaOS/releases/tag/1.8.0), [RAUC documentation](https://rauc.readthedocs.io/en/latest/basic.html), [CasaOS README](https://github.com/IceWhaleTech/CasaOS/blob/0d3b2f444ec0193193cf03eef6d43c6e35b0183e/README.md), [Nirvati OS updates](https://gitlab.com/nirvati-ug/nirvati-os/-/blob/main/rust/nirvati-osd/src/update/mod.rs)

</compare-row>

<compare-row left="CasaOS: Up to the Linux system; ZimaOS: Encrypted folders, in testing" right="Full disk encryption with Nirvati OS" title="Encryption at rest" winner="right">

ZimaOS can encrypt individual folders. IceWhale labels this feature as being in testing and recommends backing up your data. CasaOS doesn't set up encryption itself, so this is up to the underlying Linux system.

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

Sources: [ZimaOS release notes](https://github.com/IceWhaleTech/ZimaOS/releases/tag/1.5.4), [ZimaOS folder encryption](https://github.com/IceWhaleTech/ZimaDocs/blob/653e3893bc3d809aa114344f8ece38b394025c7d/source/developer/folder-encryption.md)

</compare-row>

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

CasaOS and ZimaOS have 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.
