CuOS – Container Update OS
An operating system that updates like a container.
Devices in the field need security updates for ten years and more. Every update can cause an outage. That is why updates are often put off (especially in OT). CuOS makes them systematic and repeatable.
- Update
- whole system at once, automatic rollback
- Runs on
- x86_64, LXC, 64-bit Raspberry Pi
- In production
- base of a commercial product, 20+ environments
- Since
- 2025
How it works
The whole operating system is a container image. It is built from a Dockerfile and shipped through a registry. An update replaces the root filesystem at once. The new image goes into the second of two slots on Btrfs, and the device boots it. If it does not come up, the device rolls back to the old one on its own. So no device is left with a half-finished update.
CuOS is made for devices nobody stands in front of. These include edge devices, kiosks, embedded systems and VMs. CuOS started in 2025. Since early 2026 a commercial product has been built on it. CuOS runs in production in more than 20 environments on x86_64, LXC and 64-bit Raspberry Pi.