authentik
The first patch on 2026.8 is twenty-odd fixes and no new surface.
A side-by-side editorial comparison of Skipper and Webmin — release velocity, themes, recent moves, and the top alternatives to consider.
Skipper tags a release per commit, so four versions in an hour can mean one real change.
Skipper is Zalando HTTP router and reverse proxy, and it cuts a version tag for essentially every merged commit. Four tags landed inside one hour on 31 August: three dependency and housekeeping commits and one real optimisation that removed redundant Sprintf calls from route formatting, measured at roughly 14 percent faster route serialisation and 16 percent fewer allocations. The releases before them are the same mix, with the OIDC claim-pruning filter and the atomic Valkey SetWithExpire as the recent capability work.
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.
Skipper is Zalando HTTP router and reverse proxy, and it cuts a version tag for essentially every merged commit. Four tags landed inside one hour on 31 August: three dependency and housekeeping commits and one real optimisation that removed redundant Sprintf calls from route formatting, measured at roughly 14 percent faster route serialisation and 16 percent fewer allocations. The releases before them are the same mix, with the OIDC claim-pruning filter and the atomic Valkey SetWithExpire as the recent capability work.
Two kinds of change alternate on this feed: filter and backend capability arriving occasionally, and a continuous stream of dependency group bumps between them. The capability side has been concentrated on the proxy edge — OIDC claim handling, load-balancer algorithms, Valkey-backed state — while the performance work targets the route data path itself. Because the tagging is per commit, cadence here says nothing about how much shipped.
Given the benchmark-driven optimisation in this batch, further allocation work on the eskip formatting and routing path is the most likely next capability change, with dependency bumps continuing to fill the tags between.
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.
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 Skipper or Webmin.
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.
The 3.x line finally ships function: authenticated secret writes and render patches.
Folder-level RBAC lands, and approvals finally get a webhook to talk to.
See all Skipper alternatives → · See all Webmin alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Skipper is currently shipping more aggressively (velocity 6.3 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. Skipper is currently shipping more aggressively (velocity 6.3 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 Skipper alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Skipper alternatives" section above for the current picks, or visit /alternatives/skipper for the full list with editorial commentary on each.
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.