Merge vs Dust
Side-by-side trajectory, velocity, and editorial themes.
Merge is building an AI-infrastructure stack alongside its unified-API core, with Gateway emerging as a safety/governance layer.
Merge Unified continues a weekly cadence of API maintenance and connector expansion, with Oracle Fusion Cloud ERP launching for Accounting in beta. Merge Agent Handler — the MCP/agent-tools product — is shipping new connectors almost weekly and added Scoped Access Keys for least-privilege agent runtimes. Merge Gateway, the LLM gateway, just shipped Prompt Injection Protection, DLP, RBAC, audit trails, model pinning, and provider-free routing in back-to-back weeks.
Merge is no longer just a unified-API company. Two adjacent products — Agent Handler and Gateway — are getting the heaviest investment, while Unified gets steady connector and reliability work. The Gateway moves into safety and governance target enterprise AI deployments where native provider safety isn't enough. Agent Handler's connector pace suggests Merge wants to be the default tool-pack provider for agent builders.
Expect more Gateway governance features (custom DLP rules, broader vendor support, finer role-based controls) and continued weekly connector drops in Agent Handler — most likely targeting enterprise-SaaS gaps. The Unified roadmap may start incorporating agent-shaped endpoints, blurring lines between Unified and Agent Handler.
Dust is widening the agent-platform surface: multimodal tools, enterprise audit, model breadth.
Dust is shipping at a fast clip on three fronts that together define a serious agent platform: model breadth (Gemini 3.5 Flash, Grok 4.3, refreshed Anthropic lineup), agent capability (MCP tools can now return images the agent can actually see, plus context compaction for long runs), and enterprise readiness (workspace audit logs streamable to Datadog, Splunk, or any HTTPS sink). Integrations are getting versioned upgrades on the side (Asana MCP v2, Gmail labels and archive). The product is moving from 'chat with an agent' toward 'run agents in production with observability and multimodal I/O.'
Two clear directions: deeper enterprise GTM via SIEM-grade audit, and a more capable agent runtime that can see, remember, and act inside third-party SaaS. The MCP-image release in particular treats Model Context Protocol as a real I/O surface rather than a text-only RPC, which is where the broader MCP ecosystem is heading. Frequent model rotations suggest Dust is positioning as model-agnostic infrastructure rather than locking into one provider.
Next moves likely lean into the same arc: more MCP integrations with action verbs (write/delete/transition states), expanded multimodal returns (audio, structured documents), and finer-grained admin controls layered on top of the audit foundation - tool-usage policies, per-agent egress rules, or approval workflows.
See more alternatives to Merge →
See more alternatives to Dust →