Lennart Poettering (@poettering) - Profile
Identity
| Field |
Value |
| Full Name |
Lennart Poettering |
| GitHub |
@poettering - 1,800 followers |
Career Timeline
| Period |
Employer |
Role |
| 2008–2022 |
Red Hat |
systemd creator, PulseAudio, Avahi (~14 years) |
| 2022–Jan 2026 |
Microsoft |
Continued systemd work, WSL/Azure integration (~3.5 years) |
| Jan 2026–present |
Amutable |
Co-founder + Chief Engineer |
Major Projects Created
- PulseAudio (2004) - Sound server, adopted by virtually all Linux distros
- Avahi (2005) - Zero-configuration networking implementation
- systemd (2010) - Init system and service manager, replaced SysV init across all major distros
- casync - Content-addressable data synchronization
- mkosi - Build legacy-free OS images
Amutable - The New Startup
| Field |
Value |
| Founded |
January 28, 2026 |
| Location |
Berlin, Germany |
| Mission |
"Cryptographically verifiable integrity for Linux workloads everywhere" |
| Focus |
Deterministic builds, verified boot states, runtime integrity |
| Product |
Not yet announced - no public product, source code, or pricing |
| Funding |
Undisclosed - no public VC announcements |
| GitHub org |
amutable-systems |
Amutable Leadership
| Role |
Person |
Background |
Key Detail |
| CEO |
Chris Kühl |
Ex-Microsoft (via Kinvolk acquisition 2021), GNOME Foundation, Flatcar Container Linux |
Left Microsoft 2025 |
| CTO |
Christian Brauner |
Ex-Microsoft, Linux kernel VFS maintainer, LXC/LXD creator |
Left Microsoft Jan 2026 |
| Chief Engineer |
Lennart Poettering |
systemd creator, ex-Red Hat, ex-Microsoft |
Left Microsoft Jan 2026 |
Amutable Team Members (with systemd/kernel ties)
| Person |
Previous Employer |
systemd Role |
Key Detail |
| Zbigniew Jędrzejewski-Szmek |
Red Hat (Fedora) |
systemd maintainer, FESCo member |
Advocated for birthDate field in PR #40954 |
| Daan de Meyer |
Meta |
systemd maintainer, mkosi primary maintainer |
Manages systemd deployments across Meta fleet |
| David Strauss |
Pantheon Systems (co-founder/CTO) |
systemd/udev co-maintainer |
Enterprise Linux background |
| Aleksa Sarai |
SUSE |
OCI runtime (runc) maintainer |
Container security |
| Rodrigo Campos Catelin |
— |
— |
— |
| Kai Lüke |
— |
— |
— |
| Joaquim Rocha |
— |
— |
— |
| Michael Vogt |
— |
— |
— |
All Three Founders Left Microsoft Within Months
- Chris Kühl: left Microsoft 2025
- Christian Brauner: left Microsoft January 2026
- Lennart Poettering: left Microsoft January 2026
All continue to hold their open source maintainership positions.
Role in the birthDate Revert Block
Timeline
- March 18, 2026: Boccassi merges PR #40954 (birthDate field)
- March 19, 2026: Community submits revert PR #41179
- March 19, 2026: Poettering personally closes revert PR
Poettering's Exact Arguments
- "It's an optional field in the userdb JSON object. It's not a policy engine, not an API for apps."
- "systemd enforces zero policy, it leaves that up for other parts of the system."
- "I am really not interested in these discussions here...please don't bring it here."
Actions Taken
- Closed the revert PR without merging
- Locked the conversation as "too heated"
- Restricted further discussion to collaborators only
- Made the decision irreversible through normal community channels
Conflict of Interest Assessment
Amutable's Business Incentives
Amutable's stated mission - "cryptographically verifiable integrity for Linux workloads" - gives the company direct business interest in:
- Identity metadata at the OS level - the birthDate field sets precedent for richer user records that integrity verification systems can build upon
- Compliance tooling market - enterprises needing to prove their Linux systems support age verification laws become potential Amutable customers
- "Verified state" narrative - every new field in userdb strengthens the argument that Linux needs a commercial integrity verification layer
Governance Power
- Poettering retains full control over systemd's technical direction while simultaneously running a commercial startup that benefits from systemd's feature expansion
- He can unilaterally close revert PRs and lock discussions, as demonstrated on March 19
- No formal governance body, board, or steering committee can override his decisions
- No conflict-of-interest disclosure requirements exist
Key Question
Poettering has confirmed he will "remain deeply involved in the systemd ecosystem" while serving as Amutable's chief engineer. No mechanism exists to evaluate whether his systemd decisions serve the community or his commercial interests.
Sources
