Lennart Poettering's Amutable opens private preview of immutable Linux fleet platform

Amutable, the startup co-founded by systemd creator Lennart Poettering with Christian Brauner and Chris Kühl earlier this year, has opened signups for a private preview of Amutable Foundations, its immutable Linux fleet management platform. The system eliminates traditional package management and remote access entirely: machines boot only signed unified kernel images with read-only dm-verity-protected volumes, and all configuration changes require deploying new signed images built reproducibly from pinned distribution inputs via the company's open-source tine build tool.

The platform's attestation mechanism relies on systemd-report, an experimental command introduced in systemd 260 that Amutable helped develop. Each machine cryptographically reports its complete boot chain and runtime state, signed by TPM or confidential-computing-capable CPU, to Amutable's control plane for verification against declared policy. Rollouts proceed only while machines demonstrate compliance, with attestation also governing access decisions such as cluster membership and secrets distribution. The company is recruiting design partners for early access and plans Kubernetes integration, with a presence at KubeCon North America in Salt Lake City.

Architecture and security model of Amutable Foundations

• Immutable base system: Read-only system volumes protected by dm-verity, with signed unified kernel images and measured boot ensuring only cryptographically verified code executes.
• Image build pipeline: Reproducible OS images with SBOMs built via tine, a Buck2-based tool under MPL-2.0 that imports packages from Fedora or CentOS Stream with pinned inputs.
• Distribution mechanism: Quarry, an Apache-2.0 TUF-based tool, delivers images to machines with signed metadata protecting against tampering, replay, and rollback attacks.
• Attestation and verification: Machines emit signed reports via systemd-report (experimental in systemd 260) covering firmware through OS configuration; signatures use TPM, confidential computing CPU, or software fallback.
• Operational model: No package manager, SSH, or interactive shell; operators manage fleets through a structured interface, with per-machine update repositories and policy-driven access control based on proven state.

Why it matters

Amutable Foundations represents a significant commercialization of immutable infrastructure concepts pioneered in projects like Fedora Silverblue and openSUSE MicroOS, backed by central figures in Linux systems development. The tight integration with upstream systemd through systemd-report, and the explicit targeting of Kubernetes workloads, signals potential influence on how container host security and fleet attestation evolve in enterprise Linux environments. However, the undisclosed licensing for Amutable-run components and the fully managed control plane model raise questions about open-source boundaries that the community will likely scrutinize as the preview progresses.