Introducing Immos
An immutable Linux desktop that updates as one whole image and rolls back in a single step. This is the project's public starting point — downloads follow soon.
The idea
A desktop accumulates state. Packages replaced by hand, configuration files edited and forgotten, an upgrade that went half-way — over the months the machine you have quietly stops being the machine you chose. Immos is built against that. The system is one read-only image: the desktop, the kernel and the system services ship together, updates replace the whole image rather than patching pieces of it, and nothing on the running system can drift from what was built and signed.
What works today
- Atomic updates with automatic rollback. An update is written into the system slot you are not running from, verified against a signed manifest, and given three attempts at boot. If it never reaches a working desktop, the machine returns to the previous image on its own — atomic updates and snapshots and rollback explain the mechanism.
- KDE Plasma 6 on Wayland, with applications from Flathub. What touches hardware, sessions or system services is native; everything that is an application window is a Flatpak.
- Signed updates end to end. The release key is baked into the image, and every manifest is checked against it before a single byte is written to disk.
- A graphical installer. It boots a live session, checks the machine can install, previews the whole-disk layout before anything is erased, and writes the same image the update server ships.
Downloads are coming soon
The system runs, but the public download server is not open yet, so there is nothing to install from this site today. When the first public images land, the download page will carry both release channels with signed checksums, and the release will be announced in the news.
Meanwhile the docs describe the system as it is today, and the impatient can build an image from source: building your own image walks through it, and everything it needs is in the repository.
Where this is going
Opening the downloads is the next step. After that: Secure Boot, verified images, delta updates. The full list, roughly in build order, is on the roadmap — together with the trade-offs that were chosen deliberately rather than left as gaps.
Follow along
Development happens in the open. The repository holds the build pipeline and the issue tracker, and the docs grow with the system.