LibreSpeed
After a two-year redesign, LibreSpeed is adding tests instead of polishing pixels.
A side-by-side editorial comparison of Nautobot and GravityKit — release velocity, themes, recent moves, and the top alternatives to consider.
A security advisory cycle forced Nautobot to break its REST API on both supported branches at once.
3.2.0 and 2.4.38 shipped the same day in late July carrying CVE fixes that the notes state introduce breaking changes, most often surfacing as unexpected TypeError, AttributeError or KeyError for REST and GraphQL clients. The central change, from advisory GHSA-h8rv-c7c8-cvmx, is that the REST API now enforces object-level view permissions when traversing to related objects via ?depth — beyond depth 1 a related object the caller cannot view is reduced to id, object_type, url and display instead of being serialised in full. 3.2.0 also makes job_kwargs required for create_schedule, enqueue_job, execute_job and run_job_for_testing, with a temporary fallback that warns. 3.1.8 closed an authorization bypass letting a user self-approve a workflow, and 2.4.37 fixed stored XSS in Relationship and Module Family fields.
GravityKit ships weekly across a whole plugin suite, with an MCP server now part of the lineup.
GravityKit publishes a weekly Launch Log covering releases across its Gravity Forms add-on suite — GravityView, GravityEdit, GravityCalendar, GravityCharts, GravityImport, DataTables, Maps, Multiple Forms, Zero Spam, and a Block MCP server. Recent weeks delivered union support for combining entries from multiple forms into one View, rich text inline editing, drag-to-copy in the View editor, and 3D map viewport work. A large share of every week's notes is Gravity Forms 3.0 and WordPress 7.0 compatibility work.
3.2.0 and 2.4.38 shipped the same day in late July carrying CVE fixes that the notes state introduce breaking changes, most often surfacing as unexpected TypeError, AttributeError or KeyError for REST and GraphQL clients. The central change, from advisory GHSA-h8rv-c7c8-cvmx, is that the REST API now enforces object-level view permissions when traversing to related objects via ?depth — beyond depth 1 a related object the caller cannot view is reduced to id, object_type, url and display instead of being serialised in full. 3.2.0 also makes job_kwargs required for create_schedule, enqueue_job, execute_job and run_job_for_testing, with a temporary fallback that warns. 3.1.8 closed an authorization bypass letting a user self-approve a workflow, and 2.4.37 fixed stored XSS in Relationship and Module Family fields.
Nautobot is running two supported lines in parallel and treating them as equals: 3.2.2 and 2.4.39 both shipped on 3 August with the same many-to-many change-logging fix. The security work in this window is not incidental — the advisories cluster around authorization boundaries that the API had been permissive about, and closing them meant accepting a compatibility break rather than preserving behaviour. The documentation change acknowledging that managing a Git repository grants arbitrary code execution on the worker is the same instinct applied to expectations rather than code.
The job_kwargs fallback is explicitly temporary and warns when used, so its removal in a later release is the stated next step. Expect the paired 2.4.z and 3.x releases to continue landing together.
GravityKit publishes a weekly Launch Log covering releases across its Gravity Forms add-on suite — GravityView, GravityEdit, GravityCalendar, GravityCharts, GravityImport, DataTables, Maps, Multiple Forms, Zero Spam, and a Block MCP server. Recent weeks delivered union support for combining entries from multiple forms into one View, rich text inline editing, drag-to-copy in the View editor, and 3D map viewport work. A large share of every week's notes is Gravity Forms 3.0 and WordPress 7.0 compatibility work.
Two things define this suite right now. First, it is absorbing a major upstream break: Gravity Forms 3.0 fixes appear in nearly every Launch Log, which sets the pace regardless of what the roadmap wanted. Second, the View editor is becoming a data-composition tool rather than a display configurator — unions across forms, field-to-field filtering, distance sorting on radius searches, and searchable DataTables all point at users assembling application-like views over form data. Accessibility shows up consistently too, with row headers for screen readers and editor a11y upgrades.
Expect Gravity Forms 3.0 and WordPress 7.0 compatibility to keep consuming release capacity until the upstream transition settles, with union and filtering work continuing on the View editor underneath it. The Block MCP server is the piece to watch — it is the only part of the suite aimed at agents rather than site builders.
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 GravityKit.
After a two-year redesign, LibreSpeed is adding tests instead of polishing pixels.
Gatekeeper grew a package manager for policies — and a benchmark to prove they are not too slow.
GoCD's changelog is one maintainer keeping a 2010s CI server running on current runtimes.
Incus settled its 7.0 LTS, then went straight back to a monthly feature cadence.
Firecracker's microVMs can now grow and shrink devices while running.
runc now publishes an end-of-life calendar, and three branches shipped the same CVE fix in two days.
See all Nautobot alternatives → · See all GravityKit alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Nautobot and GravityKit 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 GravityKit 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 GravityKit alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "GravityKit alternatives" section above for the current picks, or visit /alternatives/gravitykit for the full list with editorial commentary on each.