Timely
Timely adds seat visibility and per-period budgets in a steady run of weekly releases.
A side-by-side editorial comparison of CrowdSec and Icinga — release velocity, themes, recent moves, and the top alternatives to consider.
CrowdSec's 1.8.2 candidates let operators write their own bot fingerprints.
The bot detection introduced with 1.8 is now being opened to customization. The 1.8.2 candidates add custom JavaScript fingerprinting, a cscli bot subcommand and a FlagSubmission helper, and rc2 adds a RateLimit helper for the WAF plus a cookie option for embedded contexts. Operational work runs alongside it: a cs_features metric, optional limits on concurrent decision streams and TLS certificate reloads.
Icinga 2 has now shipped security releases in July, August and October.
Icinga 2 patches security issues as simultaneous releases across its supported branches. On 28 October v2.16.6 and v2.15.7 fixed mail-flag injection in the default notification scripts plus several API issues. That follows the August pair closing a /v1/events permission bypass and a node-to-node memory exhaustion path, and the July trio covering 2.14, 2.15 and 2.16 with fixes for unauthenticated takeover and crash bugs.
The bot detection introduced with 1.8 is now being opened to customization. The 1.8.2 candidates add custom JavaScript fingerprinting, a cscli bot subcommand and a FlagSubmission helper, and rc2 adds a RateLimit helper for the WAF plus a cookie option for embedded contexts. Operational work runs alongside it: a cs_features metric, optional limits on concurrent decision streams and TLS certificate reloads.
The WAF remains the center of gravity, and the direction is programmability. RateLimit, SkipProcessing and the fingerprinting hooks give rule authors primitives rather than fixed behavior. The LAPI changes point at larger deployments, where decision streaming puts load on the central API.
The final 1.8.2 is dated 26 October on GitHub, though it has not reached this feed yet. Whether fingerprint data ever joins the community blocklist remains unanswered in these notes.
Icinga 2 patches security issues as simultaneous releases across its supported branches. On 28 October v2.16.6 and v2.15.7 fixed mail-flag injection in the default notification scripts plus several API issues. That follows the August pair closing a /v1/events permission bypass and a node-to-node memory exhaustion path, and the July trio covering 2.14, 2.15 and 2.16 with fixes for unauthenticated takeover and crash bugs.
Three security rounds in four months point to a sustained audit of the API and cluster protocol, now reaching the shipped notification scripts. The 2.14 branch got the July fixes but no 2.14 release appears in the feed for August or October, which suggests its support is narrowing.
Further paired 2.16.x and 2.15.x security releases are likely while the audit continues; watch whether 2.14 gets the October fixes at all.
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 CrowdSec or Icinga.
Timely adds seat visibility and per-period budgets in a steady run of weekly releases.
Volatility 3 2.28.2 adds Mermaid tree output and starts deprecating macOS analysis.
GLAuth's September releases are security dependency updates and build fixes.
LibreSpeed 6.3 adds shareable result images and fixes Safari upload tests.
Cronicle closes three permission holes in two days, including API key exposure.
Windmill adds workspace roles and AI decision steps as its agent tooling fills out.
See all CrowdSec alternatives → · See all Icinga alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. CrowdSec and Icinga are shipping at a similar cadence (velocity 5.0 vs 5.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. CrowdSec and Icinga are shipping at a similar cadence (velocity 5.0 vs 5.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 CrowdSec alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "CrowdSec alternatives" section above for the current picks, or visit /alternatives/crowdsec for the full list with editorial commentary on each.
Top Icinga alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Icinga alternatives" section above for the current picks, or visit /alternatives/icinga for the full list with editorial commentary on each.