DNSControl
DNSControl v5 is feature-frozen with a ship date, and rc9 is pure provider cleanup
A side-by-side editorial comparison of LibreSpeed and NetBox — release velocity, themes, recent moves, and the top alternatives to consider.
LibreSpeed finished its design migration and is now hardening what it measures.
LibreSpeed spent late 2025 and early 2026 landing a rewritten frontend that had been in progress for roughly two years, moving it from a feature-switch pre-release to the default in 6.0.0. With that migration behind it, the 6.2.x line has turned to measurement itself and to deployment robustness — a dedicated connection-stability test, installable PWA packaging, and a string of Docker and asset-layout fixes.
NetBox adds a cooling data model — the first new infrastructure domain since power
After a 4.6 patch cycle spent almost entirely on GraphQL query cost and permission correctness, NetBox has opened its 4.7 line with a beta that is the opposite kind of release. It introduces cooling infrastructure as a first-class modeling domain, migrates nested group models off django-mptt onto a PostgreSQL ltree column, replaces the Service protocol/ports fields with a unified port_mappings structure, and raises the floor to PostgreSQL 15 and Redis 6. The breaking-change list runs longer than most NetBox releases run in total.
LibreSpeed spent late 2025 and early 2026 landing a rewritten frontend that had been in progress for roughly two years, moving it from a feature-switch pre-release to the default in 6.0.0. With that migration behind it, the 6.2.x line has turned to measurement itself and to deployment robustness — a dedicated connection-stability test, installable PWA packaging, and a string of Docker and asset-layout fixes.
The most interesting shift is scope. LibreSpeed was a one-shot bandwidth benchmark; 6.2.0 added a standalone stability test with live latency charting, packet-loss tracking, and CSV export, which is a different job — watching a connection over time rather than scoring it once. The 6.2.1 follow-up shows the maintainers treating measurement accuracy as the product: upload results were being inflated when a request came back with an HTTP error, and the client now waits for a successful status before starting a replacement. Deployment work runs continuously alongside, mostly making Docker and non-Docker layouts behave identically.
The stability test is new enough that its server selection and timeout handling are still being fixed, so expect the next releases to keep refining it rather than opening another surface. Docker and asset-layout parity looks like the other ongoing thread.
After a 4.6 patch cycle spent almost entirely on GraphQL query cost and permission correctness, NetBox has opened its 4.7 line with a beta that is the opposite kind of release. It introduces cooling infrastructure as a first-class modeling domain, migrates nested group models off django-mptt onto a PostgreSQL ltree column, replaces the Service protocol/ports fields with a unified port_mappings structure, and raises the floor to PostgreSQL 15 and Redis 6. The breaking-change list runs longer than most NetBox releases run in total.
The cooling model is deliberately shaped as a mirror of the existing power model — CoolingSource and CoolingFeed parallel PowerPanel and PowerFeed, CoolingIntake and CoolingOutflow parallel PowerPort and PowerOutlet, with CDUs and manifolds modeled as ordinary devices carrying those components. That symmetry says NetBox intends liquid cooling to be documented with the same rigor as power distribution, not bolted on as attributes. Underneath it, the ltree migration and the deferred search-index rebuild continue the performance thread of 4.6 by other means: instead of trimming queries inside the ORM, 4.7 is changing what the ORM sits on.
Expect at least one more 4.7 beta or release candidate before general availability, with the deprecated NestedGroupModel base class and the retained protocol/ports API fields the most likely sources of follow-up fixes as plugins migrate.
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 NetBox.
DNSControl v5 is feature-frozen with a ship date, and rc9 is pure provider cleanup
Casdoor is spending its release cadence moving auth checks from the client to the server
ESPHome ships on a calendar, and the August beta train is now five builds deep
Strimzi's 1.2.0 candidate closes with a logging fix and nothing else
Prowler's assistant decides what to do with findings; the patches keep the scanner honest
Two parallel trains, and the 'maintenance' label is now hiding real feature work
See all LibreSpeed alternatives → · See all NetBox alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. NetBox is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. NetBox is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 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.
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.
Top NetBox alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "NetBox alternatives" section above for the current picks, or visit /alternatives/netbox for the full list with editorial commentary on each.