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 Semgrep
A side-by-side editorial comparison of Knock and Semgrep — release velocity, themes, recent moves, and the top alternatives to consider.
Knock vs Semgrep: at a glance
| Feature | Knock | Semgrep |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 6.3 | 5.0 |
| Sparks · 30d | 1 | 0 |
| Top themes | notifications, developer-infrastructure, rbac, workflow-automation | static-analysis, language-coverage, scan-performance, large-repo-scaling |
| Last editorial update | 15h ago | 5d 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 Semgrep?
Semgrep keeps spending releases on parser breadth and large-repo throughput, not new surface.
Ten consecutive releases have gone into the engine rather than the product. The recurring shape is a parser refresh (Solidity, Ruby, Dart), a scan-performance change, and a batch of correctness fixes for Pro analysis. Nothing in this window changes what a team buys Semgrep for; it changes how reliably a scan finishes on a large repository.
Knock vs Semgrep: 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.
Semgrep
5.0INFRA · APIS
Semgrep keeps spending releases on parser breadth and large-repo throughput, not new surface.
◆ Current state
Ten consecutive releases have gone into the engine rather than the product. The recurring shape is a parser refresh (Solidity, Ruby, Dart), a scan-performance change, and a batch of correctness fixes for Pro analysis. Nothing in this window changes what a team buys Semgrep for; it changes how reliably a scan finishes on a large repository.
◆ Where it's heading
The performance work is converging on one problem: very large monorepos. File targeting now batches path filtering across worker domains, rule parsing shards by bytes instead of worker count, and a new Pro memory policy lets a scan trade RAM for skipping on-disk caching. Running alongside it is a quieter thread of trust work, and the 1.173.0 fix for silently dropped targets belongs to it: a file whose path filtering failed appeared in neither the findings nor the skipped list, which is the kind of gap that undermines a scan report more than any missing rule.
◆ Prediction
Expect the parser-refresh-plus-throughput cadence to continue, with the memory policy and the dependency-path output likely graduating out of experimental once large-repo users report back on them.
Alternatives to Knock and Semgrep
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 Semgrep.
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 Semgrep alternatives →
Recent activity from Knock and Semgrep
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoKnockCustom roles and permissions
- 5d agoSemgrepSolidity parser refresh; batched targeting for very large repos
- 6d agoKnockPower internal Slack alerts
- 7d agoKnockCategory + tag management
- 13d agoKnockAmplitude data source
- 20d agoKnockAnalytics in the Knock agent ⚡
- 21d agoKnockWait for event function
- 21d agoSemgrepOpenTofu files scanned as Terraform; Ruby parser updated
- 27d agoSemgrepBuild moves to a patched OCaml compiler to stop rare crashes
- 1mo agoSemgrepPro C/C++ scans skip statically-dead preprocessor branches
- 1mo agoSemgrepDart parser updated to a newer upstream version
- 1mo agoSemgrepExperimental flag exposes full paths for transitive dependency findings
Frequently asked questions
What is the difference between Knock and Semgrep?
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 Semgrep?
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 Semgrep?
Top Semgrep alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Semgrep alternatives" section above for the current picks, or visit /alternatives/semgrep for the full list with editorial commentary on each.