GravityKit
GravityKit folds every GravityView extension into one Pro plugin.
A side-by-side editorial comparison of Icinga and Wazuh — release velocity, themes, recent moves, and the top alternatives to consider.
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.
Wazuh hardens its 4.14 line while 5.0 rebuilds how agents talk to the manager.
Wazuh ships 4.14 patch releases roughly every two to three weeks, and almost all of the content is security hardening: path traversal and command injection fixes, input validation in the cluster code, connection deadlines and memory leak fixes. 4.14.10 also added memory limits for oversized rulesets and queue warnings for the vulnerability scanner. In parallel, 5.0.0 reached its second release candidate on October 30.
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.
Wazuh ships 4.14 patch releases roughly every two to three weeks, and almost all of the content is security hardening: path traversal and command injection fixes, input validation in the cluster code, connection deadlines and memory leak fixes. 4.14.10 also added memory limits for oversized rulesets and queue warnings for the vulnerability scanner. In parallel, 5.0.0 reached its second release candidate on October 30.
5.0 is the real change: agents move to HTTPS for talking to the manager, a new detection engine replaces the 4.x analysis daemon, and every server install becomes a cluster node. The 4.14 branch, meanwhile, reads like a security audit being worked through release by release, which keeps current installs safe while 5.0 settles.
More 5.0 release candidates are likely before a final release, and 4.14 patch releases with security fixes should keep coming every few weeks; a 5.0 GA date is not stated in these entries.
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 Icinga or Wazuh.
GravityKit folds every GravityView extension into one Pro plugin.
Payload's v4 beta.9 keeps every past image crop and raises the Node floor again.
Nautobot 3.3 alpha 2 adds test helpers and a cable location filter after 3.2.9's token-leak fix.
Clair 4.10 RC can read SBOMs to match Java vulnerabilities.
Shuffle tags builds almost daily, but the notes are empty.
KrakenD's community edition is shipping only dependency bumps.
See all Icinga alternatives → · See all Wazuh alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Icinga and Wazuh 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. Icinga and Wazuh 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 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.
Top Wazuh alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Wazuh alternatives" section above for the current picks, or visit /alternatives/wazuh for the full list with editorial commentary on each.