OpenStatus
openstatus is adding the enterprise surface without giving up the self-host story
Comparison · Infra & APIs
SuperTokens vs incident.io
A side-by-side editorial comparison of SuperTokens and incident.io — release velocity, themes, recent moves, and the top alternatives to consider.
SuperTokens vs incident.io: at a glance
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 incident.io?
Weekly shipping turned incident.io into an on-call platform with an agent on every surface.
incident.io publishes a changelog nearly every week, and the last two months read as three parallel builds: on-call operations (escalation reassignment, shift swapping, vacation conflict policy), alerting as a first-class object (grouping without an incident, private alerts, alert notes, Insights coverage), and an AI layer (Scribe, plus the agent reachable from anywhere in the web app). Access control appears in almost every release — private incidents scoped to teams, team-based permissions on alerts and escalations. Surfaces are widening past Slack: a macOS app from public beta to GA, WhatsApp as a notification channel, and an MCP server now generally available.
SuperTokens vs incident.io: 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.
incident.io
6.3INFRA · APIS
Weekly shipping turned incident.io into an on-call platform with an agent on every surface.
◆ Current state
incident.io publishes a changelog nearly every week, and the last two months read as three parallel builds: on-call operations (escalation reassignment, shift swapping, vacation conflict policy), alerting as a first-class object (grouping without an incident, private alerts, alert notes, Insights coverage), and an AI layer (Scribe, plus the agent reachable from anywhere in the web app). Access control appears in almost every release — private incidents scoped to teams, team-based permissions on alerts and escalations. Surfaces are widening past Slack: a macOS app from public beta to GA, WhatsApp as a notification channel, and an MCP server now generally available.
◆ Where it's heading
The product is moving from incident channels in Slack to a full on-call and alerting platform that happens to have started in Slack. Alerts are being decoupled from incidents, workflows are gaining lifecycle triggers and outbound credentials, and the agent is being placed wherever a responder already is. The steady permissions work suggests the buyer is shifting upmarket, toward organizations where incident visibility has to be restricted rather than shared by default.
◆ Prediction
Expect the alert layer to keep detaching from incidents — routing and grouping rules that stand on their own — and the agent to move out of the web app into the macOS app and the notification channels incident.io now supports.
Alternatives to SuperTokens and incident.io
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 incident.io.
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 incident.io alternatives →
Recent activity from SuperTokens and incident.io
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2d agoincident.ioReassign escalations
- 8d agoincident.ioMore powerful workflows
- 14d agoincident.ioUpcoming navigation changes ⚡
- 15d agoincident.ioPrivate incidents for teams
- 21d agoincident.ioAlert grouping improvements
- 22d agoSuperTokensMigration mode blocked while inconsistent users exist
- 29d agoincident.ioAccess the agent from everywhere
- 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 incident.io?
They serve adjacent needs but don't currently overlap on shipped themes. incident.io 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 incident.io?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. incident.io 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 incident.io?
Top incident.io alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "incident.io alternatives" section above for the current picks, or visit /alternatives/incident-io for the full list with editorial commentary on each.