GravityKit
GravityKit folds every GravityView extension into one Pro plugin.
A side-by-side editorial comparison of Nautobot and runc — release velocity, themes, recent moves, and the top alternatives to consider.
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.
runc patches one restore bug across four release lines at once.
runc shipped 1.5.3, 1.4.4, 1.3.7 and 1.6.0-rc.2 on the same day, all fixing CVE-2026-119101: a crafted image could make runc restore bind-mount any host directory into a restored container, read-write. Only people who checkpoint and later restore untrusted containers as root are exposed. The 1.6.0 candidate also changes how mount destinations that start with the rootfs path are read, following the runtime spec literally.
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.
runc shipped 1.5.3, 1.4.4, 1.3.7 and 1.6.0-rc.2 on the same day, all fixing CVE-2026-119101: a crafted image could make runc restore bind-mount any host directory into a restored container, read-write. Only people who checkpoint and later restore untrusted containers as root are exposed. The 1.6.0 candidate also changes how mount destinations that start with the rootfs path are read, following the runtime spec literally.
The project now maintains four supported branches and backports security work to each one in lockstep, while 1.6.0 keeps trading quiet tolerance for strict spec behaviour: refused read-only configs in rc.1, literal mount paths in rc.2. Users relying on runc's old lenient handling will feel 1.6.0 more than any feature it adds.
Expect 1.6.0 final after one more candidate, with 1.3.z ending since 1.3.7 is labelled the probable last patch.
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 Nautobot or runc.
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 Nautobot alternatives → · See all runc alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — security — within Infra & APIs. Nautobot and runc 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. Nautobot and runc 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 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.
Top runc alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "runc alternatives" section above for the current picks, or visit /alternatives/runc for the full list with editorial commentary on each.