Free tools Windows power users keep installed
One-click scans. No signup required.
Lennart Poettering, the systemd developer, did not simply join an existing startup: he co-founded Amutable, announced on January 27, 2026, and was named its Chief Engineer. The company says it is building a minimal, immutable Linux system that can provide cryptographic evidence of what is running on infrastructure. Its technical direction is clearer than its commercial offering: as of Amutable’s September 2026 roadmap, product availability and terms had not yet been announced.
What is Amutable, and what role does Poettering have?
Amutable announced its launch on January 27, 2026. Its named founding leaders were Chris Kühl as CEO, Christian Brauner as CTO, and Lennart Poettering as Chief Engineer; launch coverage also identified David Strauss as Chief Product Officer. Poettering is associated with systemd, the widely used Linux system and service manager. In his launch announcement, he wrote, “Today, we announce Amutable, our ✨ new ✨ company.” Amutable’s announcement and heise online’s launch coverage describe a founding announcement, not a hire at an established company.
What does the startup say it is building?
Amutable’s September 3, 2026 roadmap describes a minimal, immutable, image-based Linux system intended to cryptographically prove what is running on infrastructure. The company says components, updates, and configuration would be measured and auditable, with trust rooted in hardware and integrity remotely verifiable by system owners. It names containers, virtual machines, databases, and agents as potential workloads. These are the company’s stated aims and target uses, not independently confirmed deployments or measured security results. Amutable’s roadmap
How would measured boot and verifiable integrity work?
Measured boot records measurements—typically hashes—of firmware and software as a machine starts, with the measurements anchored in a root of trust such as a Trusted Platform Module (TPM). Those records can be checked later or sent for remote verification. Secure Boot has a different emphasis: it can refuse to boot when a component fails verification, whereas measured boot records what was loaded so that evidence can be assessed. The distinction is described in heise online’s launch-era explanation.
#1 Best Overall
Amutable says it is integrating systemd’s pcrlock and report tools toward measured boot, verification, and remote attestation. A TPM may be relevant to a hardware-rooted design, but the cited material does not establish that every Amutable setup requires a separately purchased TPM module or identify supported hardware. Compatibility depends on the host system.
Why does Amutable emphasize images and upstream Linux work?
Rather than treating integrity as only a matter of scanning individual files, Amutable describes verifying system components through image-based mechanisms. Its September 8 technical post discusses Discoverable Disk Images (DDIs) and signed dm-verity roots, alongside immutable, verifiable sources and trusted code execution. The company frames the effort as upstream-oriented work across the Linux kernel, systemd, build tooling, and update tooling. Amutable’s kernel post
Rank #2
For readers, the practical distinction is that an image-based approach aims to establish integrity for defined system images or components, while file-by-file checking asks whether individual files appear to match expectations. Amutable presents the former as part of its technical direction; the post does not establish that all of these capabilities are already combined in a generally available product.
What is Quarry, and what does it change about software updates?
Quarry is Amutable’s software distribution and provisioning toolchain, described in a September 29 post and listed as recently open-sourced by an October 1, 2026 conference entry. Amutable says it developed Quarry in response to its update and provisioning needs. Its design goals include static update payloads that can be served by simple hosting, granular ownership of signed data, flexible key escrow, autonomous updates, staged rollouts, blue-green deployments, fine-grained fleet targeting, and limiting each node to the provisioning data it needs. These are stated design goals, not an independent assessment of Quarry’s performance or security. Amutable’s Quarry post · All Systems Go! conference listing
Recommended Free Tools
| Update approach | What the cited material says |
|---|---|
| Generic distribution | The sources do not specify a particular generic server or key-management model for comparison. |
| Quarry’s stated goals | Static payloads on simple hosting; signed data with granular ownership; autonomous, staged or blue-green rollouts; fine-grained fleet targeting; and restricted access to provisioning data. |
Is Amutable available to buy or deploy?
The cited September 3 roadmap says Amutable would share more about its commercial products and how organizations could work with it later. The material available through the September technical posts and October Quarry listing does not establish commercial availability, pricing, customer deployments, certifications, or a hardware compatibility list. Quarry’s open-source status is a separate software fact; it does not by itself show that Amutable’s planned Linux system is a purchasable product.
Quick Recap
Best Value
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
