GravityKit
GravityKit ships weekly across a whole plugin suite, with an MCP server now part of the lineup.
Comparison · Infra & APIs
LibreSpeed vs runc
A side-by-side editorial comparison of LibreSpeed and runc — release velocity, themes, recent moves, and the top alternatives to consider.
LibreSpeed vs runc: 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 runc?
runc now publishes an end-of-life calendar, and three branches shipped the same CVE fix in two days.
1.5.0 in June was the first stable release of the 1.5.z series and the third under runc's formal release and support policy: 1.2.z and earlier are unsupported, 1.3.z receives only high-severity CVE fixes until the end of October 2026, and 1.4.z is limited to security and significant bugfixes. A month later 1.5.1 fixed a real-world regression — the maskPaths optimisation from 1.5.0-rc.3 broke tmpfs mounts with nr_inodes=1 on Ubuntu 20.04 kernels. In mid-June, CVE-2026-41579 was fixed simultaneously across 1.3.6, 1.4.3 and 1.5.0-rc.3 and released with no embargo.
LibreSpeed vs runc: 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.
runc
2.5INFRA · APIS
runc now publishes an end-of-life calendar, and three branches shipped the same CVE fix in two days.
◆ Current state
1.5.0 in June was the first stable release of the 1.5.z series and the third under runc's formal release and support policy: 1.2.z and earlier are unsupported, 1.3.z receives only high-severity CVE fixes until the end of October 2026, and 1.4.z is limited to security and significant bugfixes. A month later 1.5.1 fixed a real-world regression — the maskPaths optimisation from 1.5.0-rc.3 broke tmpfs mounts with nr_inodes=1 on Ubuntu 20.04 kernels. In mid-June, CVE-2026-41579 was fixed simultaneously across 1.3.6, 1.4.3 and 1.5.0-rc.3 and released with no embargo.
◆ Where it's heading
The project is behaving like infrastructure with a contract. Publishing dated support windows and shipping a coordinated fix across every live branch on the same day is the operating posture of a component that sits under every container on a host, where operators need to know what they are still entitled to. The CVE itself is instructive: a /dev symlink escape in the same family as three earlier CVEs, found by re-auditing the rootfs preparation code that had been hardened before.
◆ Prediction
1.5.0's notes state that a 1.6.0 is expected in late October 2026, which is also when 1.3.z support ends — so the next milestone is that pairing. Expect 1.5.z patches until then.
Alternatives to LibreSpeed and runc
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 runc.
Nautobot
A security advisory cycle forced Nautobot to break its REST API on both supported branches at once.
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.
See all LibreSpeed alternatives → · See all runc alternatives →
Recent activity from LibreSpeed and runc
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 15d agoLibreSpeedStandalone connection-stability test and installable PWA support
- 24d agorunctmpfs regression on Ubuntu 20.04 kernels fixed
- 1mo agoruncrunc 1.5.0 stable, with dated support windows for older branches
- 1mo agoruncCVE-2026-41579: /dev symlink host write access fixed
- 1mo agoruncRelease candidate carrying the CVE-2026-41579 fix
- 1mo agoruncCVE-2026-41579 fix backported to the 1.4 branch
- 3mo agoLibreSpeedBugfix on classic design
- 3mo agoLibreSpeedNew design is main now
- 4mo agoruncBuild fixes and seccomp WaitKillableRecv support
- 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 runc?
They serve adjacent needs but don't currently overlap on shipped themes. LibreSpeed and runc are shipping at a similar cadence (velocity 2.5 vs 2.5, 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.
Is LibreSpeed better than runc?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. LibreSpeed and runc are shipping at a similar cadence (velocity 2.5 vs 2.5, both within Sparkpulse's "active" band). 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 runc?
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.