Summaries and clusters
Sessions with a Signal get a triage pass and a summary. Clusters get a name and an explanation shared across every session in them. Daily digests tell you what changed since the last release.
Why (AI)
Root causes, with receipts.
Every claim cites a moment in the replay, and the Player turns that citation into a jump link. A claim without a citation is never rendered.
Signals 0 fired
Why generated from this session
Loading explanation…
The explanation on the right is produced from this replay. Click any timestamp to jump to the evidence.
The foundation
An answer you can check in one click.
An explanation nobody can verify is worthless on an incident call. Every claim carries a citation, and the citation is a jump link: you land on the moment, watch it, and decide for yourself. Where recording has a gap, the gap is stated rather than filled in with a guess.
Analysis never sees masked text or media. Element labels come from accessible names, test ids, and roles.
Grounding is enforced, not requested
A claim without a citation is rejected before it reaches you. An internal set of cases with known root causes gates every change we ship.
What Why does
Automatic where it is cheap. On demand where it is deep.
Explain this moment
Select a time range. Get what the user tried, what broke, the evidence of impact, the likely root cause with confidence, suggested fixes, and the linked backend trace.
Repro steps and tests
Numbered repro steps and a Playwright test using stable selectors, with masked data replaced by fixtures. Connect GitHub and Why drafts the PR.
Chat with tools
Ask in plain language. Why searches your sessions, gathers the evidence it needs, and answers with jump links.
Natural-language search
"Sessions where clinicians couldn't upload a document on iPad." The interpreted filter is shown, so you can trust the result list.
MCP server
Any MCP client can pull a session's evidence, an error context, or repro steps straight into a coding session with a scoped token.
Residency and cost
Your data stays in your region, and spend has a ceiling.
It stays where you put it
Analysis for a PHI tenant is pinned to that tenant's residency region, with no path out of it, and a tripwire alerts on any attempt otherwise.
Depth where it earns it
Triage, summaries, and cluster explanations are automatic and included. The deep work runs when a person asks for it. Economy mode trades a little speed for a lower bill when you would rather spend less than wait less.
A ceiling you set
A monthly spend cap is a hard stop on metered analysis, and the included AI keeps running underneath it. Bring your own key on Business and Enterprise and the metering stops entirely.
The story behind every bug.
Free for 1,000 sessions a month. Strict masking, conditional recording, and Signals are all included.
Get started
Replay your first session in five minutes.
Free for 1,000 sessions a month, no credit card. Or leave a work email and we will reach out about the private beta for healthcare and support teams.
You're on the list
We'll reach out to about the private beta.
We'll email when Backstory opens.