PRODUCT · OBSERVE
ReplayOps
Turn frustrated sessions into resolved tickets.
Records every web session, scores user frustration automatically and routes the worst sessions to your team as support tickets, with GDPR/KVKK masking and a fully self-hosted option.
- Who it is for
- Support and product teams that want to see what users could not describe, and organizations whose recordings must stay on their own servers.
- Last updated
What it is
ReplayOps is a self-hosted session replay and support intelligence product. It records every session with rrweb, detects rage clicks, dead clicks and errors, distills them into a 0 to 100 frustration score and turns the worst sessions into support tickets and tracker issues with the replay attached. Dynamic masking removes names, e-mails, national IDs and card numbers before storage.
What it does
Session replay + signals
Pixel-perfect replays with automatic rage-click, dead-click and error detection, distilled into a frustration score.
Tickets from sessions
One click turns a frustrated session into a support ticket or a Jira/GitHub issue with the replay, signals and customer attached.
Error inbox and alerts
JS, console and network errors grouped by signature across sessions, and threshold alerts to Slack, Teams or the in-app bell.
Dynamic GDPR/KVKK masking
A named-entity model detects names, e-mails, Turkish national IDs, phone numbers, IBANs and cards in the recording itself and masks them before storage or egress.
Live co-browsing and tester mode
Watch active users in real time and message them; testers annotate the screen and file bugs with console and network trail attached.
Self-hosted and air-gapped
Single-tenant, offline-capable, zero third-party egress: Postgres and Redis are enough, with S3, MinIO, Ceph or local disk for recordings.
How it works
- 01
Install the SDK
One script tag or npm package; recording starts immediately with no code changes.
- 02
Capture and score
Every session is recorded, its errors extracted and its frustration scored automatically.
- 03
Triage and resolve
The worst sessions surface as tickets and alerts; watch the replay, push the bug to Jira or GitHub and close the loop.
Where it sits in the lifecycle
ReplayOps watches the Monitor stage: real sessions are scored and friction becomes a finding that flows back to the TestingOps agents; with CoverOps each recorded session is joined to the code it ran.
Where it runs
Cloud, or entirely on your own infrastructure: single-tenant, air-gapped if needed, with data residency in Türkiye or anywhere else.
Works with
Slack, Microsoft Teams, Jira, Freshdesk, ServiceNow, GitHub, GitLab, Datadog, New Relic, Google Analytics, FullStory, LogRocket, Sentry, Segment; SSO over OIDC (Entra ID, Okta, Keycloak, ADFS).
Frequently asked questions
- Where is the recorded data stored?
- In the cloud service, or entirely on your own servers: recordings on S3, MinIO, Ceph or local disk, with no third-party egress in the self-hosted deployment.
- Are names, e-mails and card numbers recorded?
- A named-entity model detects personal data in page text, form values and request URLs and replaces it before storage or egress, in Turkish and English. On Enterprise, masking runs before the recording is written.
- Can we run it on our own servers?
- Yes. The whole platform runs single-tenant inside your network, air-gapped if needed, on Postgres and Redis; S3, SQS and OpenSearch are optional upgrades.
- How much does it slow the site down?
- The SDK is one script tag or npm package built on rrweb; recording starts immediately and runs alongside the page without code changes.
- How is it priced?
- A free tier with 1,000 sessions a month and 7-day retention; Startup, Pro, Business and Enterprise plans scale sessions, projects, retention, integrations, masking and SSO. Prices are on request.
Other products in the family
See it on your own stack.
A short call with the team: your setup, your volumes, where the product would run.