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 Knock and Raycast — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Knock | Raycast |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 6.3 | 0.0 |
| Sparks · 30d | 1 | 0 |
| Top themes | notifications, developer-infrastructure, rbac, workflow-automation | ai-orchestration, byok, local-models, agentic-workflows |
| Last editorial update | 15h ago | 3mo ago |
| Website | — | — |
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.
Raycast is no longer a launcher — it's a Mac-native AI orchestration layer.
Raycast spent 2025 converting itself from a keyboard launcher into a full AI client: model marketplace via BYOK and Ollama, AI Extensions that hook into apps, an iOS companion, and a Granola-powered meeting transcriber. The launcher chrome is intact, but the product's gravity now sits on the AI tab. Every recent release either adds models, adds context surfaces, or polishes the OS shell around them.
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.
Raycast spent 2025 converting itself from a keyboard launcher into a full AI client: model marketplace via BYOK and Ollama, AI Extensions that hook into apps, an iOS companion, and a Granola-powered meeting transcriber. The launcher chrome is intact, but the product's gravity now sits on the AI tab. Every recent release either adds models, adds context surfaces, or polishes the OS shell around them.
The clear arc is moving AI usage out of subscription-locked credits and into user-owned plumbing — local models via Ollama, customer keys for the major frontier providers, free-tier credits to seed adoption, and extensions that turn third-party apps into MCP-like tools. Raycast is positioning itself as the most opinionated AI client on macOS, betting that distribution and UX are durable even as model access commoditizes.
Expect deeper agentic flows next: Auto Models and Chat Branching are foundations for multi-step background agents, and the Granola integration suggests more vertical productivity bundles (calendar, mail, browsing) will be wired into AI Extensions before any new launcher feature ships.
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 Knock or Raycast.
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
See all Knock alternatives → · See all Raycast alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Knock is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 editorial sparks in the last 30 days against 0. 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. Knock is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
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.
Top Raycast alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Raycast alternatives" section above for the current picks, or visit /alternatives/raycast for the full list with editorial commentary on each.