Resend
Resend is wiring itself into every agent runtime it can reach, and now adding the controls to stop a send.
Comparison · Infra & APIs
Knock vs Nomad
A side-by-side editorial comparison of Knock and Nomad — release velocity, themes, recent moves, and the top alternatives to consider.
Knock vs Nomad: at a glance
| Feature | Knock | Nomad |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 6.3 | 5.0 |
| Sparks · 30d | 1 | 0 |
| Top themes | notifications, developer-infrastructure, rbac, workflow-automation | orchestration, container-isolation, cve-response, namespace-boundaries |
| Last editorial update | 15h ago | 16d ago |
| Website | — | Visit → |
What is Knock?
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.
What is Nomad?
Nomad's July release closed two Docker CVEs that let tasks escape their own driver configuration.
HashiCorp is cutting 1.11.x and 1.10.x Enterprise releases in matched pairs, seconds apart, with identical content. July's pair carried two Docker CVEs — one where allowed_modes or allow_privileged was not enforced before setting host namespace modes, one where a symlink let a task bypass volumes.enabled=false — plus a dynamic host volume bug that let a namespace-scoped delete permission remove another namespace's claims.
Knock vs Nomad: editorial side-by-side
Knock
6.3INFRA · APIS
Knock is hardening for enterprise buyers while its agent takes over the analysis work.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Nomad
5.0INFRA · APIS
Nomad's July release closed two Docker CVEs that let tasks escape their own driver configuration.
◆ Current state
HashiCorp is cutting 1.11.x and 1.10.x Enterprise releases in matched pairs, seconds apart, with identical content. July's pair carried two Docker CVEs — one where allowed_modes or allow_privileged was not enforced before setting host namespace modes, one where a symlink let a task bypass volumes.enabled=false — plus a dynamic host volume bug that let a namespace-scoped delete permission remove another namespace's claims.
◆ Where it's heading
All three July fixes are the same failure: a boundary that was declared in configuration but not enforced at the point of use. Alongside that, the improvements are about degraded-mode operation — falling back to the client agent's Consul token when workload identity is unavailable, Vault token renewal retries, an optional Init hook for task driver plugins. Nomad is hardening the seams between the scheduler and the systems it delegates to.
◆ Prediction
Expect the paired Enterprise releases to continue at monthly cadence, with further fixes concentrated in the Docker driver and dynamic host volumes, where the isolation boundaries are newest.
Alternatives to Knock and Nomad
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 Nomad.
DNSControl
DNSControl v5 is feature-frozen with a ship date, and rc9 is pure provider cleanup
Casdoor
Casdoor is spending its release cadence moving auth checks from the client to the server
ESPHome
ESPHome ships on a calendar, and the August beta train is now five builds deep
Strimzi
Strimzi's 1.2.0 candidate closes with a logging fix and nothing else
Prowler
Prowler's assistant decides what to do with findings; the patches keep the scanner honest
Recent activity from Knock and Nomad
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoKnockCustom roles and permissions
- 6d agoKnockPower internal Slack alerts
- 7d agoKnockCategory + tag management
- 13d agoKnockAmplitude data source
- 20d agoKnockAnalytics in the Knock agent ⚡
- 21d agoKnockWait for event function
- 1mo agoNomadTwo Docker CVEs and a cross-namespace volume delete
- 1mo agoNomadSame CVE batch backported to the 1.10 line
- 2mo agoNomadDebug bundle redaction, Vault retries, template restart fix
- 2mo agoNomad1.11 twin of the June maintenance release
- 2mo agoNomadThree web UI rendering fixes
- 2mo agoNomad1.11 twin of the May UI fix release
Frequently asked questions
What is the difference between Knock and Nomad?
They serve adjacent needs but don't currently overlap on shipped themes. Knock is currently shipping more aggressively (velocity 6.3 vs 5.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.
Is Knock better than Nomad?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Knock is currently shipping more aggressively (velocity 6.3 vs 5.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.
What are the best alternatives to Knock?
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.
What are the best alternatives to Nomad?
Top Nomad alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Nomad alternatives" section above for the current picks, or visit /alternatives/nomad for the full list with editorial commentary on each.