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

Screens run for weeks. Replay the minute.

Other platforms cut sessions at four hours because their players and pipelines need it.

Backstory keeps the visit unbounded and splits storage into segments at checkpoint boundaries, so the seam is invisible. Monitor mode makes the idle hours nearly free.

Signals 0 fired

    Why generated from this session

    Loading explanation…

    Forty-two quiet minutes, then a lost feed. The pre-roll shows the feed was healthy until the token refresh failed.

    When nobody is touching the screen.

    Normal mode versus monitor mode
    AspectNormal modeMonitor mode
    InactivityEnds the visit after 30 minutesNever ends the visit; only closing the tab does
    DOMFull mutation streamMutations still recorded; checkpoint every 30 minutes
    Canvas and mediaQuality ladder L0–L4Keyframe on interaction, alarm, or error; otherwise one every 10 minutes
    Pointer, scrollThinned by the governorOff until interaction
    Errors, failures, disconnectsRecordedRecorded, and each triggers a 60-second full-fidelity burst plus the pre-roll
    Pre-rolln/a60-second in-memory ring buffer uploaded only on a trigger
    BillingOne stored session per active 4-hour segmentIdle segments are free; at most 6 billable per visit per day

    Why the four-hour cut exists.

    An engineering convenience, not a user need.

    • Replay is a causal chain

      Playback must apply every change since the last snapshot. Without a bound, seeking into hour thirty loads hours of mutations. Segments and checkpoints solve this without cutting the visit.

    • Pipelines run at session end

      Compilation, indexing, and detection trigger when a session closes. Segments close every four hours, so a three-day visit is searchable every four hours.

    • Recorder hygiene

      Node maps and clocks drift in a tab that never reloads. The Recorder Worker is recycled and the clock resynchronized at every segment boundary.

    Product updates by email.

    Leave a work email and we will tell you when something ships. Or book a demo with an engineer.

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

    Start