GravityKit
GravityKit folds every GravityView extension into one Pro plugin.
A side-by-side editorial comparison of k0s and Wazuh — release velocity, themes, recent moves, and the top alternatives to consider.
k0s ships another four-branch patch round, with an IPv6 service CIDR fix on 1.37 and 1.36.
On November 3 k0s released v1.37.2, 1.36.6, 1.35.10 and 1.34.13 within minutes of each other. The 1.37 and 1.36 releases remove a size limit on IPv6 service CIDRs and update containerd to 2.3.6; 1.37.2 also bumps kine, ORAS and troubleshoot. The 1.35 and 1.34 branches take only Kubernetes patch updates.
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.
On November 3 k0s released v1.37.2, 1.36.6, 1.35.10 and 1.34.13 within minutes of each other. The 1.37 and 1.36 releases remove a size limit on IPv6 service CIDRs and update containerd to 2.3.6; 1.37.2 also bumps kine, ORAS and troubleshoot. The 1.35 and 1.34 branches take only Kubernetes patch updates.
k0s now maintains four branches on a shared patch cadence, roughly one coordinated round a week after the 1.37 line opened on October 27. Fixes and dependency updates land on the newest two branches, while older ones receive only Kubernetes patches, which indicates where active support is concentrated.
Expect the next coordinated round to follow upstream Kubernetes patch releases, with 1.34 likely to stop receiving updates as 1.37 matures.
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 k0s 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.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. k0s 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. k0s 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 k0s alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "k0s alternatives" section above for the current picks, or visit /alternatives/k0s 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.