Backstory vs Sentry Replay
Sentry Session Replay attaches short replays to Sentry errors and performance issues, inside the Sentry error-monitoring workflow.
Best for: Teams already standardized on Sentry who want replay context on errors. Last verified 2026-09-12.
Capability by capability.
How to read the table
"Partial" means the capability exists in some form but with material differences in scope, defaults, or depth as we understand them. Capabilities, not pricing, are compared; competitor pricing changes too often to state responsibly.
| Capability | Backstory | Sentry Replay |
|---|---|---|
| DOM-based session replay | Yes | Yes |
| DevTools panels synced to the scrubber (Elements, Console, Network, Performance, State) | Yes | Partial |
| Canvas and WebGL recordingVisible canvases only; adaptive quality ladder | Yes | Partial |
| Automatic friction and error detection22 detectors, clustered across sessions | Yes | Partial |
| AI explanations with per-claim citations to replay moments | Yes | Partial |
| AI repro steps and generated Playwright tests | Yes | No |
| MCP server for coding agents | Yes | Partial |
| OpenTelemetry trace linkage | Yes | Yes |
| Live assist with explicit consentOne Support access grant covers chat, annotation, and control; voice is separate | Yes | No |
| Consented remote control | Yes | No |
| Masking on the device before upload | Yes | Yes |
| HIPAA BAA availableEnterprise plan | Yes | Yes |
| Cryptographic erasure per end user | Yes | Partial |
| Self-hosted optionHelm chart, no broker required | Yes | Yes |
| Bounded recorder memory with graceful degradationGovernor with explicit gap markers | Yes | Partial |
| Multi-day visits (kiosks, telehealth)Monitor mode with pre-roll | Yes | No |
| Conditional recording (pay only for stored sessions) | Yes | Yes |
| SSO (SAML/OIDC) | Yes | Yes |
| WebRTC call quality observability (loss, latency, freezes, device errors) on the replay timelineTeam and above. Multi-party groups on Business and Enterprise. Audio is never captured. Sparse pictures of the remote video are a separate opt-in. | Yes | Not the focus |
Where Backstory differs.
Backstory records whole visits, stitched from 4-hour segments, rather than error-centric clips with a short maximum duration.
Backstory adds Signals for friction that never throws an error (rage clicks, dead clicks, form abandonment, frozen UI).
Backstory includes heatmaps, time on page, funnels, Live Assist, canvas, self-hosting, and grounded AI with repro generation.
Backstory and Sentry can sit side by side. Signals cover friction that never becomes a Sentry error.
Product updates by email.
Leave a work email and we will tell you when something ships. Or book a demo with an engineer.
You are on the list.
Product updates will go to .
Free for 1,000 stored sessions a month, with unlimited seats. Create a workspace and add one script tag.
Start