OpenReplay
OpenReplay is a self-hosted, open-source platform for session replay, debugging, product analytics and live cobrowsing.
- Verified facts
- 7
- Offers
- 1
- Sources
- 4
- Pricing
- Free offer
Overview
What it records
OpenReplay is an open-source experience platform that you host on your own infrastructure. It replays user sessions, adds debugging context such as network activity, console logs, JS errors and store state, analyses product usage through funnels, trends, journeys, heatmaps and web analytics, and lets support teams co-browse with users over a WebRTC call.
Because it records what users do on screen, its privacy controls carry weight. The README describes masking, obscuring or skipping data at capture time, a private mode that masks all text and inputs by default, and role-based access with SSO through SAML and OIDC; it does not say which of these features sit in the commercially licensed ee/ directory. Native session replay covers iOS and Android, while React Native support is marked as beta.
Read the full editorial overview
Hosting requirements and editions
Self-hosting is free. The README's baseline is a single VM with 2 vCPUs, 8 GB of RAM and 50 GB of storage, with deployment guides for AWS, Google Cloud, Azure, DigitalOcean, Scaleway, OVHcloud, Kubernetes with Helm, Docker, Ubuntu and source builds.
Most of the code is AGPLv3, some directories are MIT, and everything under ee/, the Enterprise Edition, is under a separate commercial licence. OpenReplay also sells Serverless, Dedicated and Bring-Your-Own-Cloud hosting. No prices for those were captured, and the SOC 2 Type II claim applies to OpenReplay Cloud, not to a deployment you run yourself.
Maintenance and evidence
The openreplay/openreplay repository was not archived and was last pushed on 6 November 2026 when checked on 8 November 2026. Its latest GitHub release, v1.28.0, was published on 25 September 2026, yet the v1.28.0 tag pointed to a commit dated 5 November 2026 when first captured and to one dated 6 November 2026 when captured again on 8 November 2026, which suggests the tag is moved as patches land; the README was the same at both commits.
No installation, replay or performance test was carried out for this profile. The README's comparison table with other vendors is the publisher's view and was not checked.
Sources
OpenReplay: openreplay-project · Evidence: documentation · Not checked
Plans & prices
Prices as listed by OpenReplay, before any tax or fee the pricing page does not state.
Scroll the table sideways for every column.
| Plan | Rate period not stated | Retention |
|---|---|---|
| Plan: Self-hosted | FreeTax: Confirm at checkoutUpfront: not established ConditionsDated publisher project README captured on 5 November 2026; supplier description, not a deployment or independent test. Infrastructure, accounts, third-party services and managed offerings have separate costs and terms. Applies to self-hosting the open-source code outside the commercially licensed ee/ directory; Enterprise Edition and OpenReplay Cloud (Serverless, Dedicated, BYOC) prices were not captured. | On a self-hosted instance, recording files are deleted after 180 days by a default MinIO lifecycle policy, while session metadata stays in the PostgreSQL database indefinitely.ConditionsOpenReplay documentation (openreplay/documentation, Cleanup Storage page at commit bd5b3132) captured on 8 November 2026. The same page documents changing the lifecycle period and a CLI cleanup command (for example openreplay --cleanup 14). Applies to the default MinIO storage of the self-hosted edition; OpenReplay Cloud retention is outside this statement. Not a hands-on test. |
OpenReplay: openreplay-project · OpenReplay: openreplay-cleanup-project
Documented facts
Each fact comes from official documentation and shows when it was verified.
Who it is for
OpenReplay is a self-hosted, open-source platform for session replay, debugging, product analytics and live cobrowsing.
Coverage limits
The README's baseline for self-hosting is a single VM with 2 vCPUs, 8 GB of RAM and 50 GB of storage.
Events
Session replays can be searched and filtered by almost any user action, session attribute or technical event without extra instrumentation; the DevTools view adds network activity, console logs, JS errors, store actions/state and 40+ performance metrics.
Dated publisher project README (release v1.28.0) captured on 8 November 2026; supplier description, not a hands-on test. Product analytics (funnels, trends, journeys, heatmaps, web analytics) is described separately in the same README.
Privacy
OpenReplay can mask elements by CSS selector, redact inputs and sanitize network payloads at capture time, before data reaches the server; a private mode masks all text and inputs by default.
Dated publisher project README (release v1.28.0) captured on 8 November 2026; supplier description, not a privacy audit or legal-compliance finding. The README links both to the SDK documentation (Data Sanitization, Private Mode); how they are enabled was not checked.
Exports
OpenReplay Enterprise Edition includes connectors that export captured user-behaviour and technical-issue data to Amazon Redshift, Google BigQuery, PostgreSQL, Snowflake or ClickHouse.
OpenReplay documentation (openreplay/documentation, Exported Data page at commit bd5b3132) captured on 8 November 2026. Enterprise Edition only (the commercially licensed ee/ code); the free open-source edition is not stated to include these connectors, and Enterprise pricing was not captured. Not a hands-on test.
Applies to the facts above: Dated publisher project README captured on 5 November 2026; supplier description, not a deployment or independent test. Infrastructure, accounts, third-party services and managed offerings have separate costs and terms.
Not confirmed in our sources
We have not confirmed these terms for OpenReplay in the linked documentation. That does not mean OpenReplay lacks them; confirm them before you rely on them.
- Sites
- Projects
Sources & methodology
Facts come from the linked documentation. Documentation checks are not hands-on tests, and readable sources can have incomplete coverage.
Discovered an undocumented discrepancy or pricing shift? Submit a correction request.
Submit correctionOpenReplay alternatives
Other analytics tools to weigh. Different billing units do not establish a cost winner, so compare plans side by side.
Plausible Analytics
Analytics
Website analytics with a compact dashboard, goals and custom events. · Evidence needs recheck
Documented price9.00/mo (currency not stated)Price needs recheckPrice terms
Documented price: 9.00/mo (currency not stated) · Plan: Starter · commitment not established
Fathom Analytics
Analytics
Website analytics with pageviews, custom events, campaign tracking and reports. · Evidence needs recheck
Documented price$15/moPrice needs recheckPrice terms
Documented price: $15/mo · Plan: 100,000 monthly pageviews · commitment not established
PostHog
Analytics
Analytics based on events, alongside separately metered replay, feature flags and other products. · Evidence needs recheck
Documented price$50 per 1,000,000 headline analytics events in the 1–2M monthly tier overagePrice needs recheckPrice terms
Documented price: $50 per 1,000,000 headline analytics events in the 1–2M monthly tier overage · Plan: Pay-as-you-go · no minimum commitment
OpenReplay comparisons
Compare two products in the same category using their documented terms and sources.
- OpenReplay vs Ackee
- OpenReplay vs Aptabase
- OpenReplay vs Cloudflare Web Analytics
- OpenReplay vs Countly
- OpenReplay vs Fathom Analytics
- OpenReplay vs GoAccess
- OpenReplay vs GoatCounter
- OpenReplay vs Liwan
- OpenReplay vs Matomo
- OpenReplay vs Medama
- OpenReplay vs Offen Fair Web Analytics
- OpenReplay vs OpenPanel
- OpenReplay vs Plausible Analytics
- OpenReplay vs PostHog
- OpenReplay vs Rybbit Cloud
- OpenReplay vs Swetrix
- OpenReplay vs Tianji
- OpenReplay vs Open Web Analytics
- OpenReplay vs Pirsch Analytics
- OpenReplay vs Umami