Backstory
Talk to sales Start free
Menu
ProductReplay & DevToolsSignalsCall qualityWhy (AI)Live AssistCanvas recordingPrivacy & complianceSelf-hosted
SolutionsHealthcare & virtual careEngineeringSupportProduct teamsKiosks & monitoring
MorePricingDocsCompareTrust centerChangelogGlossaryAboutContactPress kit
Start free Talk to sales Log in

why it broke.

Session replay that explains every bug and cites the moment it happened.

Sessions today
Demo sessions. Names were masked on the device.Choose a session to watch it.

Masked on the device before upload, so it is safe for patient data.

Start free Read the quickstart

Click a claim. Land on the moment.

Signals 0 fired

    Why generated from this session

    Loading explanation…

    A front desk walks a new patient through details and insurance, then a card photo the server rejects. Names were masked on the device, so they replay as dots.

    1. From a click to a fix

      Demo session 7F3K 14:02
      Patient
      •••• ••••••
      Member ID
      •••••••••
      Events
      126
      Masked on the device

      First it is recorded, masked. Text, typing and images are replaced on the device before anything is sent. The server never receives them.

    2. Demo session 7F3K 14:02
      Patient
      •••• ••••••
      Request
      POST 413 0:13
      Rage click
      3× 0:14
      4 signals fired

      Then a signal fires. Twenty-two detectors watch every session for rage clicks, dead clicks, failed requests, frozen screens and abandoned forms.

    3. Demo session 7F3K 14:02
      Broke
      Upload over 10 MB 0:13
      Cause
      No size check
      Confidence
      86%
      Explained, 4 citations

      Then Why explains it. Every claim links to the moment, the request or the line of code it came from. Click one and the replay jumps there.

    4. Demo session 7F3K 14:02
      Repro
      Playwright test
      Fix
      Check size first
      Same issue
      143 this week
      Ready to fix

      Then you fix it. Send repro steps and a Playwright test to your tracker, or hand the session to a coding agent over MCP.

    The whole story in one panel.

    Network and consoleEvery request with its status and timing, every error, in step with the replay. Masked fieldsNames and IDs were replaced on the device. Nobody can unmask what never arrived. Repro testA Playwright test with stable selectors, masked values swapped for fixtures.
    Demo session 7F3K 0:18
    Signals
    Failed request, high
    Rage click on Choose file
    Dead click on Continue
    Network
    POST /api/documents 413, 1.2 s
    GET /api/insurance 200, 180 ms
    Fields
    First name
    Member ID
    Why
    The upload was over 10 MB and nothing checked first.
    Next
    Generate Playwright testJoin the session live
    SignalsFriction and errors found by rules, ranked by how many sessions share them. WhyA cause with its confidence. Each claim cites a moment you can jump to. Live AssistIf they are still there, see the page live and help, with their consent.

    When watching is not enough, step in.

    Each stop on this line is a separate request the user can refuse or end.

    1. Co-browseSee the page live, from the same masked stream as the recording. No screen share, nothing new leaves the device.
    2. VoiceAn audio-only call through a relay that works from hospital and corporate networks. Recording it is a separate consent.
    3. AnnotateCircle the right button or draw an arrow. Drawings fade after ten seconds and cannot click or type.
    4. ActTake control and fix it for them. They watch you do it and can take control back at any time.

    How Live Assist works

    You have been recorded since you arrived.

    Your pointer, your scrolling, and the changes this page made to itself, kept in this tab and never uploaded. Replay it and see what the recorder would flag.

    Move your pointer over the page

    Recording locally… move, scroll, and click around this page.

    0 pointer samples, 0 clicks, 0% deepest scroll, in the last 30 seconds.

    Signals from your session 0

      Nothing has fired yet. The recorder is watching for:

      • Rage clickThree clicks within a second in one spot.
      • Dead clickA click on something that does nothing.
      • Thrashed cursorFast, aimless movement with no click.
      • Scroll depthPast three quarters of the page.

      Everything here stays in this tab. The stage is this page's own DOM, rebuilt from a local snapshot with form values masked and then replayed from the changes the page made to itself — the same reconstruction the player does for a recorded session — and the signals are the recorder's rules running against your own movements.

      Plans

      Free

      For one app and the first bugs worth knowing about.

      1,000 stored sessions and 100,000 custom events a month, 7-day retention, the full Player, Signals, heatmaps and Slack alerts, $5 of AI credit, unlimited seats. Add a card later for 4¢ per extra session.

      $0a month

      Start free

      Team

      For a product with real traffic and people who need answers today.

      10,000 stored sessions and 2,000,000 custom events a month, 30-day retention, $50 of AI credit with automatic explanations, funnels, Jira, Linear and GitHub, the MCP server, 1,000 Live Assist minutes, 5 projects. No seat fees. Extra sessions 1.5¢ each.

      $199a month

      Choose Team Business and Enterprise

      Calling at

      Free for 1,000 stored sessions a month, with unlimited seats. Create a workspace and add one script tag.

       Start