Resend
Resend is wiring itself into every agent runtime it can reach, and now adding the controls to stop a send.
A side-by-side editorial comparison of Dust and Knock — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Dust | Knock |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 8.8 | 6.3 |
| Sparks · 30d | 0 | 1 |
| Top themes | mcp, multi-model, enterprise, agent-capabilities | notifications, developer-infrastructure, rbac, workflow-automation |
| Last editorial update | 2mo ago | 13h 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.
Knock is hardening for enterprise buyers while its agent takes over the analysis work.
Knock ships weekly, in small, legible increments across three lanes: account governance (custom roles, passkeys), workflow primitives (wait-for-event, branch rebasing), and data ingress (Amplitude, Clay). The newest entry adds granular custom roles, which closes the last obvious gap in account-level access control. Alongside that, the in-product agent gained analytics, letting teams interrogate delivery performance without building reports.
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.
Knock ships weekly, in small, legible increments across three lanes: account governance (custom roles, passkeys), workflow primitives (wait-for-event, branch rebasing), and data ingress (Amplitude, Clay). The newest entry adds granular custom roles, which closes the last obvious gap in account-level access control. Alongside that, the in-product agent gained analytics, letting teams interrogate delivery performance without building reports.
Two arcs run in parallel. The infrastructure lane is buying enterprise credibility — roles, passkeys, audit-grade permissions — the checklist items that decide procurement rather than daily use. The data lane keeps widening what can trigger a workflow: product analytics from Amplitude, enriched rows from Clay, internal Slack channels as a destination. Together they push Knock from a notification API toward the messaging control plane, with the agent as the layer that explains what the plane did.
Expect the roles work to continue into audit logs or scoped API keys, since granular permissions without an activity trail is an incomplete enterprise story. More data sources are likely on the same cadence, with the CRM and warehouse categories the obvious remaining gaps.
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 Knock.
Resend is wiring itself into every agent runtime it can reach, and now adding the controls to stop a send.
DNSControl v5 is feature-frozen with a ship date, and rc9 is pure provider cleanup
Casdoor is spending its release cadence moving auth checks from the client to the server
ESPHome ships on a calendar, and the August beta train is now five builds deep
Strimzi's 1.2.0 candidate closes with a logging fix and nothing else
Prowler's assistant decides what to do with findings; the patches keep the scanner honest
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 Knock alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Knock alternatives" section above for the current picks, or visit /alternatives/knock for the full list with editorial commentary on each.