werf
Three release channels at once as werf 3 takes shape beside a still-shipping 2.75.
A side-by-side editorial comparison of Headscale and Fail2Ban — release velocity, themes, recent moves, and the top alternatives to consider.
Headscale is systematically reverse-engineering Tailscale's own behaviour to close the parity gap
Headscale is running a v0.29.0 beta series, now at beta.4, built around one theme: matching how the official Tailscale control plane actually behaves. The team generated extensive test cases against real Tailscale clients and the commercial SaaS to compare packet filter generation, and added support for SSH rules using the check action. Minimum supported client is v1.80.0.
Fail2Ban's last release was an interim beta 14 months ago; the feed spans eight years in six entries.
Fail2Ban has published one release since April 2024, and it was explicitly labelled an interim beta. The six most recent entries cover eight calendar years — 1.1.1.beta0 in June 2025, 1.1.0 in April 2024, then two 1.0.x releases from late 2022 and a pair of 0.10/0.11 releases from 2020. Every entry defers its substance to a linked ChangeLog, so the feed itself carries version numbers, joke release names and little else.
Headscale is running a v0.29.0 beta series, now at beta.4, built around one theme: matching how the official Tailscale control plane actually behaves. The team generated extensive test cases against real Tailscale clients and the commercial SaaS to compare packet filter generation, and added support for SSH rules using the check action. Minimum supported client is v1.80.0.
The methodology is the story — rather than implementing ACLs from documentation, the project is deriving behaviour empirically from the commercial service and closing the differences it finds. That is what an open-source control plane has to do to be a genuine drop-in. The four betas carry identical release notes, so the feature set was fixed at beta.1 and everything since is stabilisation.
Expect a v0.29.0 release candidate or final once the beta series stops adding notes, with ACL parity work continuing into the next cycle.
Fail2Ban has published one release since April 2024, and it was explicitly labelled an interim beta. The six most recent entries cover eight calendar years — 1.1.1.beta0 in June 2025, 1.1.0 in April 2024, then two 1.0.x releases from late 2022 and a pair of 0.10/0.11 releases from 2020. Every entry defers its substance to a linked ChangeLog, so the feed itself carries version numbers, joke release names and little else.
The stated purpose of the last substantive release was Python 3.12 and 3.13 compatibility, which is maintenance to stay installable rather than development. Release intervals have widened from months to years, and the most recent tag is a beta that has not been followed by a final. On the evidence here, the project is in preservation mode.
The most likely next event is another compatibility release triggered by a Python version that breaks the current code, not a feature release. Whether 1.1.1 ever leaves beta is not something these entries indicate — no further tag has followed it in over a year.
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 Headscale or Fail2Ban.
Three release channels at once as werf 3 takes shape beside a still-shipping 2.75.
Volatility 3 caught up with Volatility 2, then started reorganising itself.
A small LDAP server that grew OpenTelemetry tracing, embedded plugins and RISC-V builds.
OctoPrint 2.0 turns serial into one connector among several, and breaks plugins doing it.
Patch tags land monthly with release notes that itemize nothing.
A self-hosted PaaS spending its releases on secrets, injection fixes and plan limits.
See all Headscale alternatives → · See all Fail2Ban alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Headscale and Fail2Ban are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). 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. Headscale and Fail2Ban are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top Headscale alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Headscale alternatives" section above for the current picks, or visit /alternatives/headscale for the full list with editorial commentary on each.
Top Fail2Ban alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Fail2Ban alternatives" section above for the current picks, or visit /alternatives/fail2ban for the full list with editorial commentary on each.