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 NGINX — 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.
nginx patched HTTP/3 twice in a month and is trimming old platform code on mainline.
nginx runs a 1.31 mainline and a 1.30 stable line. After 1.31.5 added a native control API, a JSON module and predicate locations in September, the following releases were mostly security: 1.31.6 and 1.30.5 fixed an HTTP/3 buffer overflow (CVE-2026-90439), then 1.31.7 and 1.30.6 fixed five more CVEs including HTTP/3 request body injection. 1.31.8 on October 21 removed the Win32 iocp event module and fixed further HTTP/3 issues.
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.
nginx runs a 1.31 mainline and a 1.30 stable line. After 1.31.5 added a native control API, a JSON module and predicate locations in September, the following releases were mostly security: 1.31.6 and 1.30.5 fixed an HTTP/3 buffer overflow (CVE-2026-90439), then 1.31.7 and 1.30.6 fixed five more CVEs including HTTP/3 request body injection. 1.31.8 on October 21 removed the Win32 iocp event module and fixed further HTTP/3 issues.
HTTP/3 has needed fixes in each of the last three mainline releases, two of them CVEs. Mainline is adding features and removing legacy code at the same time, while stable gets the CVE backports.
More HTTP/3 fixes on both lines are likely; on mainline, follow-up work on the control API and JSON module is the next feature thread to watch.
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 NGINX.
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 NGINX alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — security — within Infra & APIs. CrowdSec and NGINX 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 NGINX 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 NGINX alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "NGINX alternatives" section above for the current picks, or visit /alternatives/nginx for the full list with editorial commentary on each.