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 Expo and Knock — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Expo | Knock |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 6.3 | 6.3 |
| Sparks · 30d | 1 | 1 |
| Top themes | react-native, eas, mcp-connectors, agent-strategy | notifications, developer-infrastructure, rbac, workflow-automation |
| Last editorial update | 5d ago | 15h ago |
| Website | — | — |
Expo shut down its own agent and is wiring itself into the ones developers already use.
Expo wound down the Expo Agent closed beta in July, two months after making its MCP server free on every plan, and has now shipped a way to connect Expo from the Claude desktop app. Everything else in the window is core platform work: SDK 56 and 57, EAS Observe scheduled for general availability on August 20, a Maestro test insights dashboard, and automated iOS device registration in EAS Workflows.
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.
Expo wound down the Expo Agent closed beta in July, two months after making its MCP server free on every plan, and has now shipped a way to connect Expo from the Claude desktop app. Everything else in the window is core platform work: SDK 56 and 57, EAS Observe scheduled for general availability on August 20, a Maestro test insights dashboard, and automated iOS device registration in EAS Workflows.
The pattern is conceding the assistant layer and defending the build, test, and deploy pipeline underneath it. Instead of competing for the agent surface, Expo is making project data reachable from whichever assistant a developer already runs — the free MCP server first, now a Claude desktop connection. EAS meanwhile keeps absorbing more of the release pipeline: observability heading to GA, end-to-end test insights, device provisioning automated.
More connector and MCP surface for other assistant hosts is the likely next step, alongside EAS work around what is already in flight — particularly Observe once it reaches GA on August 20. The entries give no indication of whether the SDK release cadence changes as a result.
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 Expo 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. Expo and Knock are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). 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. Expo and Knock are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top Expo alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Expo alternatives" section above for the current picks, or visit /alternatives/expo 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.