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 SuperTokens
A side-by-side editorial comparison of Knock and SuperTokens — release velocity, themes, recent moves, and the top alternatives to consider.
Knock vs SuperTokens: at a glance
| Feature | Knock | SuperTokens |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 6.3 | 2.5 |
| Sparks · 30d | 1 | 0 |
| Top themes | notifications, developer-infrastructure, rbac, workflow-automation | authentication, saml, user-migration, account-linking |
| Last editorial update | 15h ago | 12d 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 SuperTokens?
SuperTokens is hardening SAML and building a migration path off other auth providers.
SuperTokens is an open-source authentication service, and its core repo is running a 12.0 canary line alongside stable patches. The work in this window falls into two piles: SAML security — XML signature wrapping protection in 12.0.2-canary, further hardening in the 12.0.10 release — and migration mode, where new core-user-data records can be created as MIGRATED and the transition is now blocked while inconsistent users exist. Release notes are thin, usually a PR title or two per tag.
Knock vs SuperTokens: 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.
SuperTokens
2.5INFRA · APIS
SuperTokens is hardening SAML and building a migration path off other auth providers.
◆ Current state
SuperTokens is an open-source authentication service, and its core repo is running a 12.0 canary line alongside stable patches. The work in this window falls into two piles: SAML security — XML signature wrapping protection in 12.0.2-canary, further hardening in the 12.0.10 release — and migration mode, where new core-user-data records can be created as MIGRATED and the transition is now blocked while inconsistent users exist. Release notes are thin, usually a PR title or two per tag.
◆ Where it's heading
Migration mode plus account-linking exploration is the tell: this is infrastructure for importing an existing user base from another provider without breaking identity linkage mid-flight, and the guard added in 12.0.5-canary shows they hit the inconsistent-state case in practice. The SAML work runs in parallel because enterprise SAML is what a team is usually migrating toward. Also worth noting: an automated contributor, supertokens-agent-runner, opened its first PRs in this window, so part of the fix and test volume is now agent-authored.
◆ Prediction
A stable 12.x release consolidating the canary migration-mode work is the readable next step, likely once the MIGRATED transition guards have run without incident. More SAML hardening should be expected given two separate fixes landed in this window alone.
Alternatives to Knock and SuperTokens
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 SuperTokens.
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 SuperTokens alternatives →
Recent activity from Knock and SuperTokens
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 agoSuperTokensSAML hardening lands on the stable 12.0 line
- 13d agoKnockAmplitude data source
- 20d agoKnockAnalytics in the Knock agent ⚡
- 21d agoKnockWait for event function
- 1mo agoSuperTokensMigration mode blocks transition while inconsistent users exist
- 1mo agoSuperTokens12.0.4-canary ships with no described changes
- 1mo agoSuperTokensActivity log table put into use
- 2mo agoSuperTokensSAML gains XML signature wrapping protection
- 2mo agoSuperTokensNew core user data records can be created as MIGRATED
Frequently asked questions
What is the difference between Knock and SuperTokens?
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 SuperTokens?
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 SuperTokens?
Top SuperTokens alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "SuperTokens alternatives" section above for the current picks, or visit /alternatives/supertokens for the full list with editorial commentary on each.