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 Nebula
A side-by-side editorial comparison of Knock and Nebula — release velocity, themes, recent moves, and the top alternatives to consider.
Knock vs Nebula: at a glance
| Feature | Knock | Nebula |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 6.3 | 2.5 |
| Sparks · 30d | 1 | 0 |
| Top themes | notifications, developer-infrastructure, rbac, workflow-automation | mesh-vpn, overlay-network, certificates, ipv6 |
| Last editorial update | 15h ago | 7d 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 Nebula?
Overlay network that rewrote its certificate format, then spent a year fixing what it exposed.
Nebula is a peer-to-peer mesh VPN built around a certificate authority model. The v1.10.0 release was the pivot: IPv6 and multiple addresses in the overlay, plus a new v2 ASN.1 certificate format with a unified interface for external implementations. Everything since has been consequence management — a P256 signature malleability issue that allowed blocklist bypass, a source-IP acceptance flaw tied to the new multi-address certificates, and a run of fixes around route tables and Windows listeners.
Knock vs Nebula: 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.
Nebula
2.5INFRA · APIS
Overlay network that rewrote its certificate format, then spent a year fixing what it exposed.
◆ Current state
Nebula is a peer-to-peer mesh VPN built around a certificate authority model. The v1.10.0 release was the pivot: IPv6 and multiple addresses in the overlay, plus a new v2 ASN.1 certificate format with a unified interface for external implementations. Everything since has been consequence management — a P256 signature malleability issue that allowed blocklist bypass, a source-IP acceptance flaw tied to the new multi-address certificates, and a run of fixes around route tables and Windows listeners.
◆ Where it's heading
The project has moved from single-IPv4-per-node assumptions toward a genuinely flexible addressing model, and the security fixes since v1.10.0 map directly onto that change — the new certificate features widened what the code has to validate. v1.11.0 shifts attention to the operational surface instead: structured logging, corrected firewall reject-versus-drop semantics, and Windows WFP filters installed by default.
◆ Prediction
The stated plan to assert low-s signature form when validating certificates is the concrete next step visible in these entries; expect it to land as a breaking validation change in a future release.
Alternatives to Knock and Nebula
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 Nebula.
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
See all Knock alternatives → · See all Nebula alternatives →
Recent activity from Knock and Nebula
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
- 26d agoNebulaBreaking: slog logging, corrected firewall reject/drop directions, Windows WFP filters
- 6mo agoNebulaP256 signature malleability allowed blocklist bypass
- 6mo agoNebulaFix panic in use_system_route_table introduced by the previous release
- 7mo agoNebulaRoute-reload, handshake, and Windows listener fixes after the v1.10 rework
- 8mo agoNebulaIPv6 and multiple addresses in the overlay, plus a v2 certificate format ⚡
- 10mo agoNebulaPackets accepted from erroneous source IPs with unsafe_routes or multi-IP certificates
Frequently asked questions
What is the difference between Knock and Nebula?
They serve adjacent needs but don't currently overlap on shipped themes. Knock is currently shipping more aggressively (velocity 6.3 vs 2.5), 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 Nebula?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Knock is currently shipping more aggressively (velocity 6.3 vs 2.5), 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 Nebula?
Top Nebula alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Nebula alternatives" section above for the current picks, or visit /alternatives/nebula-networking for the full list with editorial commentary on each.