OpenReplay
Open-source session replay and product analytics you can self-host — full data ownership for debugging teams.
About
OpenReplay is the leading open-source answer to FullStory and Hotjar: pixel-perfect session replay plus product analytics, designed to be self-hosted so session data never leaves your infrastructure. The GitHub repository carries 12,991 stars (verified via the GitHub API on 2026-10-16, pushed the same day) and 867 forks. The core is AGPL-licensed with a proprietary enterprise edition for advanced features; a managed cloud exists for teams that do not want to operate it.
The developer tooling is the differentiator: each replay captures network activity, console logs, JavaScript errors, Redux/VueX/MobX/NgRx/Pinia/Zustand state changes, and Web Vitals alongside the DOM recording, with omni-search to filter sessions by actions or technical events. Assist adds live session viewing and WebRTC co-browsing. The honest costs: self-hosting is heavy (a third-party guide recommends 4 cores and 8 GB RAM minimum for 10,000 sessions a day), AGPL copyleft gives some legal teams pause, and advanced features sit in the proprietary edition.
What it can do
- Self-hosted pixel-perfect session replay with full data ownership
- DevTools capture: network, console, JS errors, framework state, Web Vitals
- Assist live session viewing and WebRTC co-browsing
- Omni-search across sessions by actions, attributes, and technical events
- Product analytics module with funnel and issue-impact analysis
- Fine-grained privacy controls with tracker-level masking before ingestion
Setup
- Self-host via Docker/Kubernetes (or start on the managed cloud).
- Install the tracker: npm install @openreplay/tracker, with your project key and ingest point.
- Set input masking defaults and metadata (user ID, plan) for segmentation.
- Use omni-search to find sessions by actions or errors; share replays with annotations.
Prerequisites
Infrastructure to self-host (4+ cores, 8+ GB RAM recommended for moderate volume) or a cloud plan; legal comfort with AGPL for the core.
Use cases
Works with
Trust score — 9/10
Scored 9/10 (VERIFIED tier, metrics-v1). Evidence: 12,991 GitHub stars and 867 forks verified via GitHub API 2026-10-16 (repo pushed the same day); documented DevTools capture depth across independent guides; both self-host and cloud options live. Strengths: strongest open-source replay option, serious developer tooling, true data ownership. Docked for: (1) self-hosting is infrastructure-heavy, not a weekend project; (2) AGPL copyleft requires legal review at some companies; (3) advanced features are proprietary EE, not open source. License: AGPL-3.0 core with proprietary enterprise edition.
★ 12,991 GitHub stars
How the trust score is built
Full methodology →- Adoption · stars/downloads, log-scaled vs peers
- 8.0/10
- Maintenance · recency, releases, issue load
- 9.0/10
- Openness · license + docs
- 9.0/10
- Manual review · sanity read + red-flag check
- 8.5/10
- · 12,991 GitHub stars, 867 forks (API-verified 2026-10-16)
- · AGPL core plus proprietary EE; self-host or managed cloud
- · Heavy self-host footprint; AGPL needs legal review at some companies
Sources
Every fact above was checked against these sources. Where a claim comes from the provider and couldn't be independently verified, the text says so.