GravityKit
GravityKit folds every GravityView extension into one Pro plugin.
A side-by-side editorial comparison of KubeVirt and Wazuh — release velocity, themes, recent moves, and the top alternatives to consider.
KubeVirt 1.10 hits rc.1 with incremental VM backup in beta and a port-forward CVE fixed.
KubeVirt runs a long pre-release cycle per minor version, and 1.10 is now at rc.1 (12 November) with 1,761 changes from 104 contributors since 1.9.1. The cycle centres on VM data protection: incremental backup and the backup API move to beta, offline incremental backup and an External snapshot mode arrive. rc.1 also lists a fix for an SSRF flaw (CVE-2026-13318) that let a malicious guest agent redirect virtctl port-forward and ssh traffic.
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.
KubeVirt runs a long pre-release cycle per minor version, and 1.10 is now at rc.1 (12 November) with 1,761 changes from 104 contributors since 1.9.1. The cycle centres on VM data protection: incremental backup and the backup API move to beta, offline incremental backup and an External snapshot mode arrive. rc.1 also lists a fix for an SSRF flaw (CVE-2026-13318) that let a malicious guest agent redirect virtctl port-forward and ssh traffic.
1.10 is turning KubeVirt's backup story from experimental into something operators can plan around, while DRA-based networking and CPU allocation move it closer to how Kubernetes now hands out hardware. Lower overhead is a side thread: virt-launcher-monitor was rewritten in C to use about 2 MiB. Based on the 1.9 cycle, which went rc.0 to rc.2 in four weeks, the final release is likely a few weeks out.
Expect at least one more 1.10 release candidate, then the final, with incremental backup as the headline beta feature.
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 KubeVirt 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 KubeVirt 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. KubeVirt 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. KubeVirt 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 KubeVirt alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "KubeVirt alternatives" section above for the current picks, or visit /alternatives/kubevirt 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.