DNSControl
DNSControl v5 is feature-frozen with a ship date, and rc9 is pure provider cleanup
A side-by-side editorial comparison of Dub and NetBox — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Dub | NetBox |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 0.0 | 6.3 |
| Sparks · 30d | 0 | 1 |
| Top themes | partner programs, affiliate marketing, link management, attribution | dcim, cooling, liquid-cooling, breaking-changes |
| Last editorial update | 3mo ago | 4h ago |
| Website | — | Visit → |
Dub keeps building Dub Partners into a serious partner-program OS — staggered rewards, group rules, analytics depth.
Dub is in a sustained build-out of Dub Partners alongside the original link product. The recent window added staggered reward durations (e.g. 25% for the first 12 months, 10% after), automatic group moves when partners hit performance milestones with audit history, bulk partner invites with customizable emails, multi/negative analytics filters across partners and links, Stripe free-trial tracking as lead events, and Viewer/Billing workspace roles for finer-grained access.
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.
Dub is in a sustained build-out of Dub Partners alongside the original link product. The recent window added staggered reward durations (e.g. 25% for the first 12 months, 10% after), automatic group moves when partners hit performance milestones with audit history, bulk partner invites with customizable emails, multi/negative analytics filters across partners and links, Stripe free-trial tracking as lead events, and Viewer/Billing workspace roles for finer-grained access.
The partner program is becoming the gravity well. Each release either deepens program operators' control (commission shapes, automated tiering, role-based access) or improves the analytics layer that justifies those decisions. The Stripe trial tracking suggests Dub wants to own the full attribution chain from click to subscription, not just clicks. Cadence is steady and clearly themed.
Expect more commission/tiering primitives — bonuses, tier overrides, retroactive adjustments — and tighter Stripe/attribution coupling that handles refunds and churn natively. A formal marketplace for discovering vetted partners is plausible once individual-partner-page features mature.
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 Dub 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
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 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.
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.
Top Dub alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Dub alternatives" section above for the current picks, or visit /alternatives/dub 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.