nfs-ganesha
NFS-Ganesha is burning through major versions to migrate management onto gRPC
Comparison · Infra & APIs
Merge vs NetBox
A side-by-side editorial comparison of Merge and NetBox — release velocity, themes, recent moves, and the top alternatives to consider.
Merge vs NetBox: at a glance
| Feature | Merge | NetBox |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 6.3 | 5.0 |
| Sparks · 30d | 1 | 0 |
| Top themes | unified-api, agent-infrastructure, mcp, llm-routing | dcim, ipam, graphql, performance |
| Last editorial update | 5h ago | 2h ago |
| Website | — | Visit → |
What is Merge?
Merge is becoming the governance layer for agent tool access, not just a unified data API.
Merge ships a weekly digest split across three lines: the original unified API (HRIS, ATS, CRM, accounting, file storage, ticketing), Agent Handler for AI agent connectors, and Gateway for LLM routing. The unified-API half reads as a maintenance grind — every week is dominated by SharePoint, SAP SuccessFactors, Workday and Dayforce sync reliability, pagination and mapping fixes. All of July's directional news came from the other two lines, ending with hundreds of generic MCP connectors folded into the Agent Handler catalog and an AI Guardrails surface with PII detection.
What is NetBox?
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.
Merge vs NetBox: editorial side-by-side
Merge
6.3INFRA · APIS
Merge is becoming the governance layer for agent tool access, not just a unified data API.
◆ Current state
Merge ships a weekly digest split across three lines: the original unified API (HRIS, ATS, CRM, accounting, file storage, ticketing), Agent Handler for AI agent connectors, and Gateway for LLM routing. The unified-API half reads as a maintenance grind — every week is dominated by SharePoint, SAP SuccessFactors, Workday and Dayforce sync reliability, pagination and mapping fixes. All of July's directional news came from the other two lines, ending with hundreds of generic MCP connectors folded into the Agent Handler catalog and an AI Guardrails surface with PII detection.
◆ Where it's heading
The unified API is being maintained, not expanded — new objects arrive at a trickle (expense reports in early July) while the bulk of each week goes to sync stability across existing connectors. Attention has moved to sitting between agents and the tools they call: Merge now offers auth, access control, governance and guardrails over connectors it did not build. Gateway is moving the same way, from a routing product to multi-tenant infrastructure customers resell, via Embedded Routing Stack, bring-your-own keys and per-customer complexity classifiers.
◆ Prediction
Expect the guardrails surface to deepen — PII detection and pre-run/post-run rule labels shipped in the same month, and the generic MCP connectors currently arrive without the tool safety hints Merge applied to its own catalog. The likely next step is extending that governance tooling to the imported MCP servers.
NetBox
5.0INFRA · APIS
NetBox spent 4.6's patch cycle paying down GraphQL query cost, release after release
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Alternatives to Merge and NetBox
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 Merge or NetBox.
easybuild
EasyBuild opened itself to third-party plugins and went all-in on AMD GPUs
Casdoor
Casdoor ships a version per commit, and this week's commits are org-boundary checks
Hotjar
Hotjar's update feed stops in April 2025 — the arc it captures ended mid-sentence.
Tailscale
Tailscale is turning the tailnet into something you provision by API, not configure by hand.
Daytona
Ten releases in a month, all pointed at making agent sandboxes safe to run in production.
See all Merge alternatives → · See all NetBox alternatives →
Recent activity from Merge and NetBox
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 23h agoNetBoxGraphQL N+1 fixes and permission corrections in 4.6.8
- 8d agoNetBox4.6.8 release candidate refreshes translation strings
- 12d agoMergeHundreds of generic MCP connectors land in Agent Handler ⚡
- 12d agoNetBox4.6.7 trims GraphQL and scope-rebuild query overhead
- 14d agoNetBoxCluster-scoped VLANs, tag "any" lookup, audit-trail hardening
- 19d agoMergeLink setup flow becomes configurable per integration
- 26d agoMergeEmbedded Routing Stack gives Gateway per-customer model controls
- 29d agoNetBoxMDC connectors, script-module REST updates, Korean support
- 1mo agoMergeGPT-5.6, Grok 4.5 join Gateway; new Professional Plan pricing
- 1mo agoMergeiTrent and OmniHR connectors; Slackbot gets its own agent identity
- 1mo agoMergeExpense reports endpoint, iTrent and OmniHR join HRIS
- 1mo agoNetBoxSchema-enum dropdowns and chunked bulk custom-field updates
Frequently asked questions
What is the difference between Merge and NetBox?
They serve adjacent needs but don't currently overlap on shipped themes. Merge 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.
Is Merge better than NetBox?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Merge 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.
What are the best alternatives to Merge?
Top Merge alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Merge alternatives" section above for the current picks, or visit /alternatives/merge-dev for the full list with editorial commentary on each.
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.