nfs-ganesha
NFS-Ganesha is burning through major versions to migrate management onto gRPC
A side-by-side editorial comparison of Dust and NetBox — release velocity, themes, recent moves, and the top alternatives to consider.
Dust doubles down on MCP-native agents with multi-model routing and enterprise guardrails.
Dust is building an MCP-native agent platform with broad model coverage and growing enterprise depth. The May cadence shows parallel investment in agent capability (vision via MCP tools, context compaction, frame editing/export) and operational readiness (audit logs, SIEM streaming, protocol migrations). Mobile is getting a voice-first input redesign.
NetBox spent 4.6's patch cycle paying down GraphQL query cost, release after release
NetBox 4.6 shipped its feature payload in May — virtual machine types, cable bundles, rack groups, ETags and cursor pagination on the REST API — and every patch since has been consolidation. The 4.6.8 release on August 11 has no enhancements section at all: four performance fixes and eleven bug fixes. Three of those four performance items are GraphQL, continuing a thread that runs unbroken back through 4.6.7, 4.6.5 and 4.6.1.
Dust is building an MCP-native agent platform with broad model coverage and growing enterprise depth. The May cadence shows parallel investment in agent capability (vision via MCP tools, context compaction, frame editing/export) and operational readiness (audit logs, SIEM streaming, protocol migrations). Mobile is getting a voice-first input redesign.
The product is converging on agents-in-the-enterprise via MCP, with multi-model routing as table stakes. MCP V2 migrations and image returns from MCP tools point to the protocol becoming Dust's integration backbone. The model-refresh cadence — three vendors in 48 hours — suggests model routing is now a core competency, not a feature.
Expect more MCP V2 connector migrations and richer MCP return types beyond images. The voice-first mobile input bar likely precedes a deeper voice-mode agent surface.
NetBox 4.6 shipped its feature payload in May — virtual machine types, cable bundles, rack groups, ETags and cursor pagination on the REST API — and every patch since has been consolidation. The 4.6.8 release on August 11 has no enhancements section at all: four performance fixes and eleven bug fixes. Three of those four performance items are GraphQL, continuing a thread that runs unbroken back through 4.6.7, 4.6.5 and 4.6.1.
The recurring target is N+1 queries in the GraphQL layer — generic relations, custom fields, to-one prefetching, tags. That is the signature of an API surface meeting production-scale data and being profiled against it, not speculative optimization. Alongside it runs a quieter permissions-correctness thread: object permissions on script writes, audit-trail immutability, LDAP evaluation cost, superuser bypass checks.
Expect 4.6.9 to continue the same pattern — GraphQL query-cost fixes and permission-enforcement corrections, no new models. The next feature payload most likely arrives with a 4.7 minor rather than anywhere in this patch line.
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 Dust or NetBox.
NFS-Ganesha is burning through major versions to migrate management onto gRPC
EasyBuild opened itself to third-party plugins and went all-in on AMD GPUs
Casdoor ships a version per commit, and this week's commits are org-boundary checks
Hotjar's update feed stops in April 2025 — the arc it captures ended mid-sentence.
Tailscale is turning the tailnet into something you provision by API, not configure by hand.
Merge is becoming the governance layer for agent tool access, not just a unified data API.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Dust is currently shipping more aggressively (velocity 8.8 vs 5.0), with 0 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. Dust is currently shipping more aggressively (velocity 8.8 vs 5.0), with 0 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 Dust alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Dust alternatives" section above for the current picks, or visit /alternatives/dust 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.