nfs-ganesha
NFS-Ganesha is burning through major versions to migrate management onto gRPC
Comparison · Infra & APIs
Dust vs Merge
A side-by-side editorial comparison of Dust and Merge — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:mcp
Dust vs Merge: at a glance
| Feature | Dust | Merge |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 8.8 | 6.3 |
| Sparks · 30d | 0 | 1 |
| Top themes | mcp, multi-model, enterprise, agent-capabilities | unified-api, agent-infrastructure, mcp, llm-routing |
| Last editorial update | 2mo ago | 4h ago |
| Website | Visit → | — |
What is Dust?
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.
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.
Dust vs Merge: editorial side-by-side
Dust
8.8INFRA · APIS
Dust doubles down on MCP-native agents with multi-model routing and enterprise guardrails.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
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.
Alternatives to Dust and Merge
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 Merge.
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
NetBox
NetBox spent 4.6's patch cycle paying down GraphQL query cost, release after release
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.
Recent activity from Dust and Merge
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 12d agoMergeHundreds of generic MCP connectors land in Agent Handler ⚡
- 19d agoMergeLink setup flow becomes configurable per integration
- 26d agoMergeEmbedded Routing Stack gives Gateway per-customer model controls
- 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
- 2mo agoDustCompact mobile input bar goes voice-first
- 2mo agoDustFrames export as PDF or PNG
- 2mo agoDustInline text editing in frames
- 2mo agoDustGemini 3.5 Flash now available
- 2mo agoDustGrok 4.3 upgrade and Anthropic model migrations
- 3mo agoDustAsana MCP update
Frequently asked questions
What is the difference between Dust and Merge?
Both compete on the same themes — mcp — within Infra & APIs. Dust is currently shipping more aggressively (velocity 8.8 vs 6.3), with 0 editorial sparks in the last 30 days against 1. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is Dust better than Merge?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Dust is currently shipping more aggressively (velocity 8.8 vs 6.3), with 0 editorial sparks in the last 30 days against 1. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
What are the best alternatives to Dust?
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.
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.