Backstory
Log in Start free
Menu Home
ProductReplay & DevToolsSignalsCall qualityWhy (AI)Live AssistCanvas recordingPrivacy & complianceSelf-hosted
SolutionsHealthcare & virtual careEngineeringSupportProduct teamsKiosks & monitoring
MorePricingDocsCompareTrust centerGlossaryAboutContactPress kit
Log inStart free
Signals

Find friction before anyone files a ticket.

Deterministic detectors run on every session as it is processed. Issues are clustered by type, selector, route, and error fingerprint, ranked by impact, and routed to Slack, Teams, email, PagerDuty, or a webhook.

Start free Read the docs

Signals 0 fired

    Why generated from this session

    Loading explanation…

    In this session Signals fires an error click, a rage click, a dead click, and form abandonment, each pointing at its moment in the replay.

    Detectors

    Rules first, AI second.

    Deterministic rules are cheap, explainable, and give the AI grounded evidence. Thresholds are tunable per project.

    Signal detectors and their default rules
    SignalRule (defaults)Severity
    Rage click≥ 3 clicks within 1 s on the same element or within 30 pxMedium; High if followed by exit
    Dead clickClick on an interactive-looking element with no DOM change, navigation, or request within 1 sMedium
    Error clickClick followed within 500 ms by a JS error or a failed request it initiatedHigh
    Thrashed cursorFast, high-entropy pointer movement with no clicks for over 3 sLow
    Form abandonmentA field changed, no submit, page left or 60 s idleMedium; High on checkout and intake
    Field struggleSame field edited three or more times, or a validation message appearsMedium
    Failed request4xx or 5xx, or a network error, excluding allowlisted probesHigh for 5xx
    Slow requestOver the endpoint's 7-day p95, or over 3 sLow or Medium
    Frozen UINo paint or mutation for 2 s after an interaction, or a long task over 1 sHigh
    Layout instabilityCLS over 0.25 on a page, or a shift right before a clickMedium
    Slow pageLCP over 4 s or INP over 500 msMedium
    Navigation loopA → B → A → B within 30 sMedium
    Blank pageAlmost no visible text 3 s after loadHigh
    Console error burstMore than 10 console errors in 5 sMedium
    CrashSession ends without pagehide and the next load finds unflushed dataHigh
    Accessibility trapA keyboard user cannot leave an element for 10 sMedium
    Monitor triggerCustom trigger on a kiosk or telehealth visit, with pre-rollHigh
    CustomYour own rules on custom events and propertiesConfigurable

    Also detected: back-button bounce, broken resources, offline periods, consent friction. See the docs for every threshold.

    Clusters

    One issue, not a thousand alerts.

    1. Detect per session, as chunks arrive
    2. Cluster kind + selector + route + fingerprint
    3. Rank count, users, trend, release
    4. Explain AI names it, cites evidence
    5. Route Slack, Teams, email, webhook, Jira
    A cluster carries counts, affected users, first and last seen, releases, a trend line, and an AI explanation shared across every session in it.

    Regression alerts

    A cluster that exceeds three times its 7-day hourly baseline fires once, with counts updated in place on Slack or Teams rather than re-posting.

    Release attribution

    Every issue carries the release it was seen on. New clusters after a deploy are the first thing the digest mentions.

    Lifecycle

    Acknowledge, snooze, assign, resolve, or mute from the notification itself. Two-way sync with Jira and Linear.

    The story behind every bug.

    Free for 1,000 sessions a month. Strict masking, conditional recording, and Signals are all included.

    Start freeBook a demo
    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.

    Start freeBook a demo