GravityKit
GravityKit ships weekly across a whole plugin suite, with an MCP server now part of the lineup.
Comparison · Infra & APIs
LibreSpeed vs Nautobot
A side-by-side editorial comparison of LibreSpeed and Nautobot — release velocity, themes, recent moves, and the top alternatives to consider.
LibreSpeed vs Nautobot: at a glance
What is LibreSpeed?
After a two-year redesign, LibreSpeed is adding tests instead of polishing pixels.
LibreSpeed is a self-hosted speed test that spent roughly two years landing a new frontend design, shipped it behind a feature switch, then promoted it to default in 6.0.0. With that out of the way, 6.2.0 turns to capability: a standalone connection-stability test with live latency charting, packet-loss tracking, alerts and CSV export, plus PWA metadata so the tool can be installed from a browser. Docker deployment has been reworked in parallel, including a port change and PHP limits that were silently rejecting default upload chunks.
What is Nautobot?
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.
LibreSpeed vs Nautobot: editorial side-by-side
LibreSpeed
2.5INFRA · APIS
After a two-year redesign, LibreSpeed is adding tests instead of polishing pixels.
◆ Current state
LibreSpeed is a self-hosted speed test that spent roughly two years landing a new frontend design, shipped it behind a feature switch, then promoted it to default in 6.0.0. With that out of the way, 6.2.0 turns to capability: a standalone connection-stability test with live latency charting, packet-loss tracking, alerts and CSV export, plus PWA metadata so the tool can be installed from a browser. Docker deployment has been reworked in parallel, including a port change and PHP limits that were silently rejecting default upload chunks.
◆ Where it's heading
The redesign was the blocker; now that it is default, releases are moving outward — a second measurement mode, installability, better multi-server list handling. The Docker thread runs alongside and is where the breaking changes live: default port moved from 80 to 8080 in preparation for rootless operation, post_max_size raised to accept the tool's own 20 MiB chunks, Alpine base updated. Much of the recent throughput comes from outside contributors and automated agents rather than a single maintainer.
◆ Prediction
Expect the stability test to gain the configuration and server-side plumbing the main speed test already has, and the rootless-container work that the port change was preparation for to land next. Nothing in the entries suggests a change to the project's self-hosted, no-backend-dependency positioning.
Nautobot
5.0INFRA · APIS
A security advisory cycle forced Nautobot to break its REST API on both supported branches at once.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Alternatives to LibreSpeed and Nautobot
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 LibreSpeed or Nautobot.
Gatekeeper
Gatekeeper grew a package manager for policies — and a benchmark to prove they are not too slow.
GoCD
GoCD's changelog is one maintainer keeping a 2010s CI server running on current runtimes.
Incus
Incus settled its 7.0 LTS, then went straight back to a monthly feature cadence.
Firecracker
Firecracker's microVMs can now grow and shrink devices while running.
runc
runc now publishes an end-of-life calendar, and three branches shipped the same CVE fix in two days.
See all LibreSpeed alternatives → · See all Nautobot alternatives →
Recent activity from LibreSpeed and Nautobot
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 3d agoNautobotCable termination filter and GraphQL OpenTelemetry corrections
- 4d agoNautobotMany-to-many change logging and GitRepository sync permissions
- 10d agoNautobotPublic API constants and a widened cryptography range
- 11d agoNautobotREST API permission enforcement on related objects; job_kwargs required
- 11d agoNautobotSecurity-driven breaking API changes on the 2.4 branch
- 14d agoNautobotDependency updates mitigating CVEs
- 15d agoLibreSpeedStandalone connection-stability test and installable PWA support
- 3mo agoLibreSpeedBugfix on classic design
- 3mo agoLibreSpeedNew design is main now
- 6mo agoLibreSpeedHotfix for SQLite database matching in the Docker entrypoint
- 7mo agoLibreSpeedPre-release puts the new design behind a feature switch
- 7mo agoLibreSpeedFinal 5.x release moves the Docker port to 8080
Frequently asked questions
What is the difference between LibreSpeed and Nautobot?
They serve adjacent needs but don't currently overlap on shipped themes. Nautobot is currently shipping more aggressively (velocity 5.0 vs 2.5), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is LibreSpeed better than Nautobot?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Nautobot is currently shipping more aggressively (velocity 5.0 vs 2.5), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
What are the best alternatives to LibreSpeed?
Top LibreSpeed alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "LibreSpeed alternatives" section above for the current picks, or visit /alternatives/librespeed for the full list with editorial commentary on each.
What are the best alternatives to Nautobot?
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.