GravityKit
GravityKit folds every GravityView extension into one Pro plugin.
A side-by-side editorial comparison of KubeVirt and Nautobot — 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.
Nautobot 3.3 alpha 2 adds test helpers and a cable location filter after 3.2.9's token-leak fix.
Nautobot's 3.2 and 2.4 lines still ship same-day security releases every two weeks; on November 9 v3.2.9 and v2.4.46 fixed a flaw where the Export Object List job let users read other users' API token keys. The 3.3 feature line opened the same day with REST API rate limiting and JSON and YAML exports. v3.3.0a2 on November 13 mostly adds Playwright helpers for App test suites, along with a location filter on the cable connection form and a fix for a login page that reloaded every 15 seconds.
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.
Nautobot's 3.2 and 2.4 lines still ship same-day security releases every two weeks; on November 9 v3.2.9 and v2.4.46 fixed a flaw where the Export Object List job let users read other users' API token keys. The 3.3 feature line opened the same day with REST API rate limiting and JSON and YAML exports. v3.3.0a2 on November 13 mostly adds Playwright helpers for App test suites, along with a location filter on the cable connection form and a fix for a login page that reloaded every 15 seconds.
3.3 is moving through alphas quickly, four days apart, while the security audit continues on the stable lines. The Playwright helpers suggest Nautobot wants App developers to test against its UI with shared tooling rather than custom scripts.
More 3.3 alphas or a beta should follow within weeks, alongside the next pair of 3.2.x and 2.4.x security releases on the two-week rhythm.
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 Nautobot.
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.
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.
Velociraptor's recent releases are mostly about patching CVEs.
See all KubeVirt alternatives → · See all Nautobot alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — security — within Infra & APIs. KubeVirt and Nautobot 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 Nautobot 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 Nautobot alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Nautobot alternatives" section above for the current picks, or visit /alternatives/nautobot for the full list with editorial commentary on each.