DNSControl
DNSControl v5 is feature-frozen with a ship date, and rc9 is pure provider cleanup
A side-by-side editorial comparison of NetBox and OpenStatus — release velocity, themes, recent moves, and the top alternatives to consider.
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.
openstatus is adding the enterprise surface without giving up the self-host story
openstatus is an open-source uptime monitoring and status page platform, shipping small, well-scoped features every week or two. The recent run covers SAML single sign-on, a command menu in the dashboard, CSS-variable theming for status pages, Python and PHP SDKs, and social cross-posting of status updates. Underneath it, an AI chat assistant added in May was made self-hostable against any OpenAI-compatible model in July.
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.
openstatus is an open-source uptime monitoring and status page platform, shipping small, well-scoped features every week or two. The recent run covers SAML single sign-on, a command menu in the dashboard, CSS-variable theming for status pages, Python and PHP SDKs, and social cross-posting of status updates. Underneath it, an AI chat assistant added in May was made self-hostable against any OpenAI-compatible model in July.
Two lines are running in parallel and they point the same way. One is enterprise readiness — SAML against Okta and Entra ID, configurable history retention, component-level impact on incident updates. The other is keeping every one of those capabilities available to self-hosters, most pointedly by letting the AI assistant run on NVIDIA NIM, vLLM or Ollama instead of a hosted API. openstatus is positioning as the status page you can run yourself without accepting a stripped-down version.
SAML usually arrives with the rest of the enterprise access package close behind, so directory provisioning or role-based permissions are the likely next additions; the SDK line (Python, PHP) also looks unfinished at two languages.
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 NetBox or OpenStatus.
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 NetBox alternatives → · See all OpenStatus alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. NetBox and OpenStatus are shipping at a similar cadence (velocity 6.3 vs 6.3, 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. NetBox and OpenStatus are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
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.
Top OpenStatus alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "OpenStatus alternatives" section above for the current picks, or visit /alternatives/openstatus for the full list with editorial commentary on each.