authentik
The first patch on 2026.8 is twenty-odd fixes and no new surface.
A side-by-side editorial comparison of Webmin and Windmill — 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.
Windmill gives its AI agents a test harness, the piece that lets them into production flows
Windmill is a developer platform for scripts, flows and internal apps, shipping weekly across three lanes. The AI lane is the busiest: sessions that build scripts and flows as reviewable drafts, a read-only plan mode that refuses writes until you approve, version history on session artifacts, and now evaluation for reusable agents. The runtime lane keeps absorbing data tooling — dbt projects run natively, BigQuery and Snowflake came out from behind the Enterprise licence. The workspace lane is consolidating deployment semantics around fork lineage.
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.
Windmill is a developer platform for scripts, flows and internal apps, shipping weekly across three lanes. The AI lane is the busiest: sessions that build scripts and flows as reviewable drafts, a read-only plan mode that refuses writes until you approve, version history on session artifacts, and now evaluation for reusable agents. The runtime lane keeps absorbing data tooling — dbt projects run natively, BigQuery and Snowflake came out from behind the Enterprise licence. The workspace lane is consolidating deployment semantics around fork lineage.
The AI work has moved through a recognisable sequence: first let the assistant build things, then constrain what it may do without approval, then make its output reviewable and revertible, and now make agents measurable against a fixed set of cases. That is the arc of taking AI from a demo surface to something you are willing to put in a scheduled flow. In parallel, Windmill keeps pulling data-stack runtimes inside its own execution model rather than integrating with them, and keeps giving away runtimes that were previously licensed.
Evals are the obvious hook for regression gating, so expect them to be callable from a flow or CI rather than only from the agent card, and expect the eval run history to feed the same version-comparison surface the session artifacts already use.
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 Windmill.
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 Webmin alternatives → · See all Windmill alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — self-hosted — within Infra & APIs. Windmill is currently shipping more aggressively (velocity 6.3 vs 2.5), with 1 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. Windmill is currently shipping more aggressively (velocity 6.3 vs 2.5), with 1 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 Windmill alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Windmill alternatives" section above for the current picks, or visit /alternatives/windmill for the full list with editorial commentary on each.