Postman vs Dust
Side-by-side trajectory, velocity, and editorial themes.
Postman is on a steady weekly bug-fix cadence with quiet expansion in Monitors and API governance.
The 12.8.x and 12.9.x release stream is dominated by minor bug fixes with the occasional substantive change folded in: Monitor regions expanded across APAC and Europe, Flows canvas regression fixed, and changelog version tagging added so API spec changes can be labeled by release. The publication style is uniformly version-only with sparse content, which masks what's actually shipping in any given build.
Postman is making small, steady investments in the API-platform half of the product (governance across workspaces, changelog tagging, more Monitor regions) while the client app collects routine fixes. The cadence and content suggest no near-term overhaul, but a maturing focus on governance for teams that manage many APIs across many workspaces.
Expect more API Governance scope expansions (likely org-level reporting on top of the cross-workspace visibility) and additional Monitor regions to follow user demand. The release notes themselves will probably stay terse without a process change.
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 Postman →
See more alternatives to Dust →