# ZimaOS: a Buildroot NAS operating system built around OTA updates > IceWhale's release distribution for its Zima hardware, grown out of CasaOS, distributed as a disk image you flash with Etcher rather than a package you install, with support extending to generic x86-64 machines. **IceWhaleTech/ZimaOS** — A Simplified, Focused and Open NAS OS_ - Repository: https://github.com/IceWhaleTech/ZimaOS - Website: https://www.zimaspace.com/zimaos - Stars: 2,987 · Forks: 127 - Language: Shell - License: not declared - Published: 2026-10-06 · Updated: 2026-10-06 · Language: en - Canonical page: https://hysenlabs.com/projects/icewhaletech-zimaos ## A distribution, not a package manager The first thing to understand about ZimaOS is that this repository is not where the operating system lives. The README says plainly that the project is just for releasing test images, and that discussion belongs on the IceWhale community forum. The tree matches that description exactly: a README, a SECURITY file, an assets directory of screenshots, a public-test directory, a release-note directory, a rauc.txt and a single shell script called zimaos-fix.sh. The actual system is built with Buildroot, which is the right tool for the job. Buildroot produces a small embedded root filesystem rather than a distribution with a package manager, which is where the two headline features come from: a lightweight, memory-efficient system and minimized I/O. For a device whose job is serving files and running a handful of containers, that is a sensible trade. The release badge and download badge both point at a separate repository, zimaos-rauc, which is where the actual artifacts live. RAUC is the update mechanism, and it is what makes the over-the-air and offline update features work. That separation is easy to miss when you arrive from a GitHub search and land on what looks like a source tree. ## What it adds on top of CasaOS ZimaOS is evolved from CasaOS, and the README is explicit about why: a release version was built for better hardware compatibility and a better update experience. The features it advertises are lightweight and memory-efficient operation, minimized I/O, over the air updates, offline updates and better disk management capabilities. Every one of those five is an operational claim about a shipped product, not a feature of a library. The comparison with CasaOS is presented as a table in the README rather than as prose, which is the right format for the question and also the least satisfying one to read from a text editor. What can be said from the surrounding text is that ZimaOS adapts well to the Zima series of hardware and is also compatible with x86-64 systems running UEFI. The supported hardware list names four specific products, ZimaBoard, ZimaBoard2, ZimaBlade and ZimaCube, plus generic x86-64 machines such as an Intel NUC. That last entry is the interesting one for readers without IceWhale hardware, because it means the image is not locked to one board even though the project is funded by selling boards. ## Installation means erasing a disk with a USB stick There is no package to install and no installer script you can inspect before committing a machine to it. The documented procedure starts with preparation: enable UEFI boot in BIOS or UEFI and disable Secure Boot, and back up anything on the target drive, because the selected disk will be erased. That warning appears before anything is downloaded, which is the correct order. The image itself is a file named zimaos_XXXXX_installer.img, where the digits vary by version, downloaded from the Releases page. The flashing tool is Balena Etcher, available for Windows, macOS and Linux, and the README walks through it as a four step sequence: launch Etcher, select the downloaded .img file, choose the target USB drive while verifying it is the correct device, click Flash, wait, then eject safely. Then the physical install: insert the USB stick, open the boot menu, boot from it in UEFI mode, follow the on-screen installer to select the target disk and confirm, reboot when prompted, remove the stick, and boot from the installed disk to finish initial setup. Five explicit steps and no ambiguity about what gets destroyed. The repository also links a recorded walkthrough of the whole process as a video attachment. ## What the release notes reveal about the software underneath The release notes are the most technical document associated with the project, because the image hides the source. Version 1.7.1, released 2026-08-21, leads with a security fix for a high-risk issue in the file services, then adds a be2net network driver for Emulex network cards and Azerbaijani language support. The bug fixes in that release describe software with real structure. There is a fix for abnormal memory usage in certain file operation scenarios, one for empty folders left behind after cutting folders, one for backup tasks that could fail or be interrupted, one for USB-related tasks lost after a system restart, and one for inaccurate RAID status display. Two of them are worth reading twice because they describe data loss rather than inconvenience: the empty folder after a cut, and the uninstall behaviour that could delete the application configuration folder. The improvement list tells you what CasaOS is actually built on. Docker container startup speed and efficiency, the network configuration experience during Docker installation, the Docker web URL port configuration with more flexible port settings, YAML configuration saving compatibility to reduce failures caused by special content, App Store and installation window display, and app migration compatibility. Every one of those is a container management or application management concern. The last entry, 1.7.1-beta1, also points readers to a Discord community described as having 43,000 members. ## A test image program, and what that implies The heading on this repository is the ZimaOS Public Evaluation Program. That framing is more informative than it first appears. It tells you that the artifacts are released for evaluation, that bug reports are expected to go to the forum rather than to the issue tracker here, and that the README's own description of the repository as being for test images is meant literally. There is a practical consequence worth planning around. You should not treat an update channel as a support contract. If ZimaOS is going onto a machine holding data you care about, the offline update path and the backup functionality are the two features to verify first, and the release notes suggest the backup code has needed fixing as recently as 1.7.1. For anyone deploying at scale or wanting a repeatable provisioning process, there is a documented path that bypasses the USB stick entirely. A wiki issue on the zimaos-rauc repository covers installation on Proxmox, contributed by a user named silycr, and the README credits them. That route suits a virtual machine or a bare metal host you provision programmatically, and it is the piece to read before flashing anything. ## Conclusion The line between ZimaOS and CasaOS is the line between a project you build yourself and a distribution someone ships. ZimaOS exists because a consumer NAS needs a release image with a stable update channel, and that is a packaging problem more than a design problem. Flashing is the price of admission: you erase a disk, you need UEFI with Secure Boot off, and there is no in-place path from a CasaOS install described in the documentation. If you own Zima hardware this is clearly the intended path and OTA updates are the reason to prefer it. On generic x86-64 the same image works, but the honest question is why you would not run CasaOS or a plain Linux distribution with Docker and Samba instead. The Proxmox route in the wiki is worth reading first if that is your target. ## FAQ ### What is ZimaOS for? It is the operating system IceWhale ships for its Zima hardware, a NAS oriented system built on CasaOS with Buildroot and an over the air update channel. It also runs on generic x86-64 machines with UEFI, and its job is file services, Docker containers and app management rather than a general purpose desktop. ### Should I use CasaOS or ZimaOS? They are related rather than competing, since ZimaOS is evolved from CasaOS. The difference is distribution: ZimaOS is a released image with OTA and offline updates and better hardware compatibility, aimed at the Zima boards but also x86-64. CasaOS is what you build and update yourself. Choose ZimaOS if you want someone else to own the update channel. ### Is Zima OS any good? The release notes for 1.7.1 show an active project that fixes real defects, including data loss cases around folder operations and app uninstalls, and that also shipped a high-risk file services security fix. That combination suggests software still being hardened rather than a finished product. The repository itself is explicitly a public evaluation program for test images. ### How much does ZimaOS cost? The software is distributed as freely downloadable images from the Releases page and there is no licence fee described for the OS itself. The Zima boards that it is designed for are commercial hardware, which is where the cost sits if you are buying the appliance rather than installing on a machine you already own. ## Sources - [IceWhaleTech/ZimaOS on GitHub](https://github.com/IceWhaleTech/ZimaOS) - [Issues](https://github.com/IceWhaleTech/ZimaOS/issues) - [Project website](https://www.zimaspace.com/zimaos) - [README](https://github.com/IceWhaleTech/ZimaOS/blob/main/README.md) - [Releases](https://github.com/IceWhaleTech/ZimaOS/releases) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/icewhaletech-zimaos