OpenStatus
openstatus is adding the enterprise surface without giving up the self-host story
Comparison · Infra & APIs
SuperTokens vs Knock
A side-by-side editorial comparison of SuperTokens and Knock — release velocity, themes, recent moves, and the top alternatives to consider.
SuperTokens vs Knock: at a glance
| Feature | SuperTokens | Knock |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 2.5 | 6.3 |
| Sparks · 30d | 0 | 1 |
| Top themes | authentication, account-linking, user-migration, saml | notification-infrastructure, no-code-controls, environments-and-branching, enterprise-auth |
| Last editorial update | 2h ago | 20h ago |
| Website | Visit → | — |
What is SuperTokens?
SuperTokens is building v12 in canary around one hard problem: migrating existing users
The visible releases are all v12.0.x canary builds — no stable v12 in the window. The work concentrates on account linking and a MIGRATED mode for core user directories, with supporting changes for SAML signature-wrapping protection, an activity_log table, and OpenTelemetry span annotations.
What is Knock?
Knock is moving notification control out of the codebase and into the dashboard.
Knock is shipping weekly, and the releases cluster into three groups: workflow tooling that borrows from git (branch rebasing, sandbox test runs that skip delay steps), enterprise account hardening (passkeys, TOTP multi-factor with account-wide enforcement), and dashboard surface that non-engineers can actually operate — tags and saved views, schema management for how properties appear in preview and condition builders, a hosted preference center configurable without engineering. The newest entry adds Clay tables as a data source that creates users and triggers messaging as rows finish enriching.
SuperTokens vs Knock: editorial side-by-side
SuperTokens
2.5INFRA · APIS
SuperTokens is building v12 in canary around one hard problem: migrating existing users
◆ Current state
The visible releases are all v12.0.x canary builds — no stable v12 in the window. The work concentrates on account linking and a MIGRATED mode for core user directories, with supporting changes for SAML signature-wrapping protection, an activity_log table, and OpenTelemetry span annotations.
◆ Where it's heading
The migration-mode thread is the spine here. First new core user directories were allowed to be created as MIGRATED, then the transition into MIGRATED was blocked while inconsistent users exist, then account linking itself was reopened for exploration. That sequence reads as a team discovering that letting a running deployment switch identity models mid-flight is where the correctness risk lives, and adding guardrails before shipping it. Everything else in the window is scaffolding around that: audit-shaped activity logging, tracing annotations, and CI cleanup.
◆ Prediction
A stable v12 looks gated on the account-linking and migration-mode work settling; expect further canaries tightening the conditions under which a deployment is allowed to change modes before any general release.
Knock
6.3INFRA · APIS
Knock is moving notification control out of the codebase and into the dashboard.
◆ Current state
Knock is shipping weekly, and the releases cluster into three groups: workflow tooling that borrows from git (branch rebasing, sandbox test runs that skip delay steps), enterprise account hardening (passkeys, TOTP multi-factor with account-wide enforcement), and dashboard surface that non-engineers can actually operate — tags and saved views, schema management for how properties appear in preview and condition builders, a hosted preference center configurable without engineering. The newest entry adds Clay tables as a data source that creates users and triggers messaging as rows finish enriching.
◆ Where it's heading
The through-line is who holds the controls. Knock started as notification infrastructure a developer wires up, and nearly every recent release moves a piece of that — templates, preferences, property schemas, view organization, now the trigger source itself — into a dashboard a lifecycle or GTM operator can use without a deploy. The developer surface is not being abandoned; it is being restructured into environments and branches so that operator edits have a safe review path.
◆ Prediction
Expect more data sources alongside Clay, and further dashboard controls for the branch and environment workflow now that rebasing exists. The warehouse export landing in the same month suggests message events flowing both directions is the next area of work.
Alternatives to SuperTokens and Knock
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 SuperTokens or Knock.
Casdoor
Casdoor ships a minor version per commit, and every one of them is login-flow repair
Authelia
Authelia's 4.39 line is a long hardening run, not a feature line
Buildkite
Buildkite is rebuilding its CI surface for agents first and clearing the v3 baseline out of the way.
Semgrep
Semgrep is spending its releases on parser breadth and scan startup, not new product surface.
Unleash
A marketing blog, not a changelog: Unleash is recasting feature flags as agent governance
See all SuperTokens alternatives → · See all Knock alternatives →
Recent activity from SuperTokens and Knock
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoKnockClay data source ⚡
- 6d agoKnockRedesigned template editor
- 13d agoKnockBranch rebasing
- 15d agoKnockPasskey authentication
- 20d agoKnockSaved views and tags
- 21d agoKnockSchema management
- 22d agoSuperTokensMigration mode blocked while inconsistent users exist
- 1mo agoSuperTokensv12.0.4-canary
- 1mo agoSuperTokensActivity log table put to use
- 1mo agoSuperTokensSAML signature-wrapping protection added
- 1mo agoSuperTokensNew core user directories can start in MIGRATED mode
Frequently asked questions
What is the difference between SuperTokens and Knock?
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 SuperTokens better than Knock?
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 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.
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.