authentik
The first patch on 2026.8 is twenty-odd fixes and no new surface.
A side-by-side editorial comparison of Webmin and werf — release velocity, themes, recent moves, and the top alternatives to consider.
Webmin absorbs Linux subsystems one module at a time, with access controls tightening underneath.
Webmin ships every few weeks as a paired release with Usermin, and the visible window runs from 2.641 in May to 2.660 in August. The substantial release is 2.650, which added modules for systemd services and units, the GRUB 2 boot loader and the Kea DHCP server, along with basic Alpine Linux support. Since then the work has narrowed to storage and packaging detail: Btrfs subvolume quota management, vfsv1 quota files above 4 TiB, APT package holds and incremental Fail2Ban ban times.
The 3.x line finally ships function: authenticated secret writes and render patches.
werf publishes the same work across alpha, beta, ea and stable channels plus a 3.x dev line, so one fix surfaces three or four times under different version numbers. This pair is that pattern exactly: v3.3.0 carries two features — writing authenticated secret values from deploy, and renderPatches support — plus four fixes, and v2.77.2 carries the same four fixes and nothing else. The fixes are the usual build-engine territory: buildah imports failing on symlinked paths, a panic when a stapel base image disappears mid-commit, a cache repo pointing at itself, and host-cleanup misreporting what it pruned.
Webmin ships every few weeks as a paired release with Usermin, and the visible window runs from 2.641 in May to 2.660 in August. The substantial release is 2.650, which added modules for systemd services and units, the GRUB 2 boot loader and the Kea DHCP server, along with basic Alpine Linux support. Since then the work has narrowed to storage and packaging detail: Btrfs subvolume quota management, vfsv1 quota files above 4 TiB, APT package holds and incremental Fail2Ban ban times.
Two lines run in parallel. One extends the range of Linux subsystems Webmin can administer, adding a module wherever the distributions have moved: systemd, Kea, nftables, Netplan, Alpine. The other tightens what an authenticated user is permitted to do. Release 2.652 added a per-user ACL blocking URL downloads from non-public IP addresses and enforced file access ACLs on local imports across the database and directory modules, while 2.650 fixed a reflected XSS and made RPC-only accounts fail before module ACL checks. For a panel that runs as root on other people's servers, the second line is the more consequential one.
Expect the module-per-subsystem pattern to keep tracking whatever the distributions adopt next, and further ACL work in the modules that fetch remote URLs or import local files, since that is where the last two releases found problems.
werf publishes the same work across alpha, beta, ea and stable channels plus a 3.x dev line, so one fix surfaces three or four times under different version numbers. This pair is that pattern exactly: v3.3.0 carries two features — writing authenticated secret values from deploy, and renderPatches support — plus four fixes, and v2.77.2 carries the same four fixes and nothing else. The fixes are the usual build-engine territory: buildah imports failing on symlinked paths, a panic when a stapel base image disappears mid-commit, a cache repo pointing at itself, and host-cleanup misreporting what it pruned.
The division of labour between the lines is now explicit — 2.x takes only fixes, 3.x takes fixes plus everything new. This is the first window where the 3.x dev line carries user-facing deploy function rather than build internals and gated experiments, which moves it from a place to accumulate changes toward something with its own reason to exist. The build-engine hardening under parallelism continues underneath both.
renderPatches and authenticated secret writes are both deploy-side, so the next 3.x releases likely continue there rather than returning to buildah. Whether the embedded deno work behind its build tag connects to the render path is still not stated.
Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Webmin or werf.
The first patch on 2026.8 is twenty-odd fixes and no new surface.
Alert rate limits stop being per-source and start being per-tenant, by query.
The essay series keeps running ahead of the products it describes.
Both lines patch on the same day, and the reverted JSONata upgrade finally sticks.
Folder-level RBAC lands, and approvals finally get a webhook to talk to.
Retool posts one-line changelog entries, and its agent work is the only visible thread
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. werf is currently shipping more aggressively (velocity 5.0 vs 2.5), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. werf is currently shipping more aggressively (velocity 5.0 vs 2.5), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top Webmin alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Webmin alternatives" section above for the current picks, or visit /alternatives/webmin for the full list with editorial commentary on each.
Top werf alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "werf alternatives" section above for the current picks, or visit /alternatives/werf for the full list with editorial commentary on each.