Resend
Resend is wiring itself into every agent runtime it can reach, and now adding the controls to stop a send.
Comparison · Infra & APIs
NetBox vs Rhino
A side-by-side editorial comparison of NetBox and Rhino — release velocity, themes, recent moves, and the top alternatives to consider.
NetBox vs Rhino: at a glance
What is NetBox?
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.
What is Rhino?
Rhino's release line runs on release candidates, and 1.12 makes room for coding agents.
Rhino publishes only release candidates to this feed — every entry back to 1.9 is an -rc tag, with no final release ever appearing. The 1.12.0 candidate is the first in the window with user-visible substance: a `use` function that scaffolds an AGENTS.md file carrying Rhino-specific instructions, plus a `use` function for the CI template. The rest is maintenance: covr-based test coverage, e2e tests, Node dependency updates, and a maintainer handover.
NetBox vs Rhino: editorial side-by-side
NetBox
6.3INFRA · APIS
NetBox adds a cooling data model — the first new infrastructure domain since power
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Rhino
0.0INFRA · APIS
Rhino's release line runs on release candidates, and 1.12 makes room for coding agents.
◆ Current state
Rhino publishes only release candidates to this feed — every entry back to 1.9 is an -rc tag, with no final release ever appearing. The 1.12.0 candidate is the first in the window with user-visible substance: a `use` function that scaffolds an AGENTS.md file carrying Rhino-specific instructions, plus a `use` function for the CI template. The rest is maintenance: covr-based test coverage, e2e tests, Node dependency updates, and a maintainer handover.
◆ Where it's heading
Rhino is converging on scaffolding as its main surface — the framework's value is increasingly in what it generates for you rather than what it does at runtime, and 1.12 extends that generation to instructions meant for AI coding agents rather than humans. The maintainer change and the CI/coverage work in the same release read as consolidation after a long gap: 1.11 shipped in April 2025, 1.12 not until June 2026.
◆ Prediction
More `use_*` scaffolding functions are the obvious next increment, since two arrived in a single release. Whether the AGENTS.md instructions grow into deeper agent tooling is not something these entries settle.
Alternatives to NetBox and Rhino
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 Rhino.
DNSControl
DNSControl v5 is feature-frozen with a ship date, and rc9 is pure provider cleanup
Casdoor
Casdoor is spending its release cadence moving auth checks from the client to the server
ESPHome
ESPHome ships on a calendar, and the August beta train is now five builds deep
Strimzi
Strimzi's 1.2.0 candidate closes with a logging fix and nothing else
Prowler
Prowler's assistant decides what to do with findings; the patches keep the scanner honest
See all NetBox alternatives → · See all Rhino alternatives →
Recent activity from NetBox and Rhino
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoNetBoxNetBox 4.7 beta models cooling plant the way it models power ⚡
- 7d agoNetBoxGraphQL N+1 fixes and permission corrections in 4.6.8
- 15d agoNetBox4.6.8 release candidate refreshes translation strings
- 19d agoNetBox4.6.7 trims GraphQL and scope-rebuild query overhead
- 21d agoNetBoxCluster-scoped VLANs, tag "any" lookup, audit-trail hardening
- 1mo agoNetBoxMDC connectors, script-module REST updates, Korean support
- 2mo agoRhinoRhino 1.12 adds AGENTS.md and CI-template scaffolding
- 1y agoRhinoRhino 1.11.0 release candidate
- 1y agoRhinoRhino 1.10.0 release candidate
- 2y agoRhinoRhino 1.9 adds bslib support and prettier formatting
Frequently asked questions
What is the difference between NetBox and Rhino?
They serve adjacent needs but don't currently overlap on shipped themes. NetBox is currently shipping more aggressively (velocity 6.3 vs 0.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.
Is NetBox better than Rhino?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. NetBox is currently shipping more aggressively (velocity 6.3 vs 0.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.
What are the best alternatives to NetBox?
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.
What are the best alternatives to Rhino?
Top Rhino alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Rhino alternatives" section above for the current picks, or visit /alternatives/rhino-r for the full list with editorial commentary on each.