Stytch
Now inside Twilio, Stytch's independent cadence has slowed to a trickle.
A side-by-side editorial comparison of Dust and Depot — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Dust | Depot |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 8.8 | 6.3 |
| Sparks · 30d | 0 | 1 |
| Top themes | mcp, multi-model, enterprise, agent-capabilities | ci-cd, container-builds, sandboxes, ai-agents |
| Last editorial update | 1mo ago | 2d ago |
| Website | Visit → | — |
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.
Depot is growing from a build accelerator into a full CI and agent-sandbox platform.
Depot's recent releases cluster around its CI product reaching general availability (API and CLI GA, native step retries, durable cache disks, test-result ingestion) plus a Sandbox SDK for running agent-generated code. The company is clearly broadening past its original remote-build-cache niche. The cadence is high and feature-dense.
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.
Depot's recent releases cluster around its CI product reaching general availability (API and CLI GA, native step retries, durable cache disks, test-result ingestion) plus a Sandbox SDK for running agent-generated code. The company is clearly broadening past its original remote-build-cache niche. The cadence is high and feature-dense.
Two arcs are visible: hardening CI into a complete, programmable system (retries, caching, test reporting, an OpenAPI-described API), and staking out the agent-execution space with an ephemeral Sandbox SDK. Both target teams that want builds, CI, and untrusted-code execution from one vendor. Expect the Sandbox SDK to move toward GA and CI to keep filling parity gaps with incumbents.
Next likely: the Sandbox SDK exits private beta, and CI adds more of the surface teams expect (broader test-framework ingestion, richer run analytics) now that its API and CLI are GA.
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 Depot.
Now inside Twilio, Stytch's independent cadence has slowed to a trickle.
Resend ships a tight, frequent changelog: richer email content and deeper dev-tool reach
Unleash reframes feature flags as agentic 'runtime control,' aimed straight at LaunchDarkly.
ToolJet widens its data-source layer — AI sources included — on a fast LTS/beta release train.
GitHub bends toward enterprise AI governance while retiring its standalone Models offering.
BugSnag is compounding on mobile observability and AI-assisted debugging
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 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.
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.
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 Depot alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Depot alternatives" section above for the current picks, or visit /alternatives/depot for the full list with editorial commentary on each.