🚀 CuOS components help you keep systems and services secure, up-to-date, and easy to manage — from a single device to a small fleet. They let you define, update, and control infrastructure via container images, Git workflows, or declarative configs, bringing practical DevOps to embedded, edge, server, and cloud environments.
The CuOS operating system is also a solid base for IoT, edge, and VM-based products.
To build a bootable system, start at cuos-release: describe the system you want in a system.json and run ./cuos-release/tool.sh image. It produces a disk image, an ISO installer or an LXC container.
Components are organized in layers from device to service:
| Layer | Component & purpose | Repository |
|---|---|---|
| Device management | CuOS Fleet Management — agent + server for device enrollment, health telemetry, remote commands, and rollout orchestration. | cuos-iac |
| Service management | CuOS IaC — Infrastructure-as-Code manager and Web UI for defining services, builds, deployments, and release channels. | cuos-iac |
| Operating system | CuOS (OS) — minimal OS image with updater, OTA tooling and reproducible builds. | cuos |
| Build & release | CuOS Release Tooling — tool.sh, the image and installer factories, pinned image versions, configuration merging, signing and encryption. |
cuos-release |
All components can be used independently — each CuOS component works standalone (you don’t need to run the others to use a single component).
CuOS can be taken up at four levels, from running services on a ready-made system to building an OS from scratch. The Development Guide explains which one is yours; these repositories are the starting points.
| Level | Repository |
|---|---|
| Container Service — run services, build nothing | iac-hello-world-system |
| Own CuOS Init App — your own update or deployment mechanism | boilerplate-own-cuos-init-app |
| Own OS based on the CuOS system — another board, or your own kernel drivers | boilerplate-own-os-based-on-cuos |
- Open an issue in the relevant repo.
- Contact us directly (contact AT simonwalz.de or via LinkedIn)