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

Replay for clinical apps, without the PHI.

Strict masking is the default: every character is replaced on the device before upload.

Images and canvases are blocked unless allowlisted, and AI runs only inside a PHI enclave. Telehealth workstations record for days in monitor mode.

Signals 0 fired

    Why generated from this session

    Loading explanation…

    A synthetic intake session in strict mode. The clinician's note and the patient's name never left the browser as text.

    Built for the buyer who reads the DPIA.

    • Strict mode by default

      All text masked with layout-preserving glyphs, inputs masked, images blocked. Allowlist a DICOM viewer canvas with a single attribute and it routes through the PHI path.

      Default
    • PHI enclave

      Dedicated processing, dedicated keys, egress allowlists, and AI processing that cannot leave the United States. A tripwire alerts on any attempt otherwise.

      Dedicated keys
    • Six-year audit trail

      Every replay view, export, live-assist action, AI query, and recording-setting change is logged immutably. Masking happens at capture, so there is nothing to unmask later.

      Six years
    • Automatic logoff and MFA

      15-minute idle timeout for HIPAA tenants, passkeys or TOTP required, SSO with SAML or OIDC, SCIM deprovisioning within 60 seconds.

      15 min idle
    • Erasure and DSAR

      Cryptographic erasure per patient identifier and a one-click export for access requests, both with receipts.

      Per patient
    • Self-hosted if you must

      The same Helm chart runs inside your VPC or data center, air-gapped, with your own model endpoint for AI.

      Air-gapped

    Runs for days, recorded for pennies.

    A sitter watches six patient feeds for a twelve-hour shift.

    Recording every frame is expensive and almost all of it is uninteresting. Monitor mode keeps a 60-second pre-roll in memory and uploads only when something happens: a feed drops, a token refresh fails, an alarm fires.

    What the replay shows

    The minute before the feed dropped, the 503 from the streaming service, the WebSocket closing with code 1006, the alarm state on the tile, and the click that recovered it. Idle segments are free.

    Signals 0 fired

      Why generated from this session

      Loading explanation…

      The visit connected. Did it work?

      A telehealth visit that fails is almost never a DOM problem.

      The far end sent no audio, the clinician's camera was held by another application, the hospital network forced media through a relay, or a shared workstation had no CPU left to encode. Backstory records WebRTC state and quality next to the replay, so each of those is a named finding rather than a phone call that ends in a shrug.

      Safe to switch on in a clinical environment

      The visit's audio never leaves the device. Call quality records metrics and state. Pictures of the remote video stay off unless the organization turns them on, including on a strict-privacy project. Candidate addresses are hashed and device labels are masked, because a label like “Dr. Rivera's AirPods” is identifying.

      Thirteen detectors run on every call, including one-way media, freeze, audio dropout, device-in-use, and relay fallback. Each doubles as a monitor-mode trigger, so a dropped patient feed on a telehealth shift records the minute before it happened. How call observability works

      Questions it answers

      • Is it our app or their network?

      • Which sites force a TURN relay?

      • Did this release regress setup time?

      • Are the complaints coming from one device model that cannot encode at the resolution we ask for?

      • Which clinicians are hitting a camera conflict with their other software?

      What we provide, and what you configure.

      Backstory provides

      The BAA, encryption with per-tenant and per-patient keys, the PHI enclave, audit logging, access controls, United States storage, breach-notification procedures, and workforce training evidence for your vendor review.

      You configure

      Masking attributes on the elements that matter, canvas allowlists for imaging viewers, roles for your users, retention per project, and the consent posture for patient-facing surfaces. Privacy Preview shows you the result before a single session is recorded.

      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