OpenReplay

A self-hosted session replay, co-browsing and product analytics platform, so users' data never leaves your infrastructure.

13.1k stars, 878 forks TypeScript On GitHub since April 2021

Visit website View on GitHub How to run it

What is OpenReplay?

OpenReplay records how users move through your web app and replays each session with full technical context: console logs, network requests, errors and performance data, so developers can reproduce bugs. Co-browsing lets support staff see and guide a user's screen live, and product analytics shows funnels and journeys. Data can be sanitized before it leaves the browser, and everything runs on your own servers or Kubernetes.

Good fit if

  • You debug front-end issues and want to see exactly what users did.
  • Privacy or regulation requires session data to stay in-house.

Look elsewhere if

  • You want analytics, flags and replays together: PostHog.
  • You want a small install: the compose setup runs about 25 services.

Before you adopt it

OpenReplay moved from MIT to AGPL-3.0 in August 2024. The ee directory holds enterprise features under a separate license, and contributors sign a CLA.

Drafted with AI from the project's README and repository data, then checked against that data on 30 October 2026. Report a correction

OpenReplay health: is it still maintained?

76 of 100, actively developed

  • Activity
    282 commits in the last 90 days, the latest on 30 October 2026.
    30 / 30
  • Contributors
    11 people wrote the latest 100 commits; the most active wrote 22% of them.
    14 / 20
  • Releases
    6 releases in the last 12 months; the latest, v1.28.0, on 25 September 2026.
    10 / 20
  • Replies to issues
    Maintainers answered 57% of recent issues, with a median first reply after 13 hours.
    17 / 20
  • Security practices
    No OpenSSF Scorecard for this repository yet, so this part gets a neutral score.
    5 / 10

Read from GitHub on 1 November 2026. How the score works

OpenReplay license: is it open source?

OpenReplay uses AGPL-3.0, an open-source license approved by the OSI. Some features sit under a separate paid license inside the same repository. Contributors sign a contributor license agreement, which lets the owner relicense their work later.

  1. April 2021First published on GitHub under MIT.
  2. 30 August 2024Changed to AGPL-3.0. Commit: Change to AGPL v3
  3. TodayAGPL-3.0, with paid parts: license file assigns a different licence to part of the code; directory ee/; separate license ee/LICENSE.md. A contributor license agreement is required.

How to run OpenReplay yourself

Docker
Dockerfile or compose file in the repository
Compose file
scripts/docker-compose/docker-compose.yaml: 25 services (postgres, clickhouse, redis, minio, proxy)
Setup effort
5 of 5, judged from the compose file
Kubernetes
Helm chart in the repository
Desktop and mobile
No app builds in GitHub releases
Interface languages
7 languages

Install instructions: openreplay.com or the README on GitHub.

Alternatives to OpenReplay

  • PostHogPostHog is the leading platform for building self-driving products. Our developer tools – AI observability,… 80 health · MIT · 40.6k stars
  • UmamiUmami is a privacy-first web and product analytics platform. Traffic, campaigns, behavior, conversions, and… 79 health · MIT · 39.8k stars
  • Highlighthighlight.io: The open source, full-stack monitoring platform. Error monitoring, session replay, logging,… 25 health · Apache-2.0 · 9.4k stars
  • RybbitRybbit - open-source and privacy-friendly alternative to Google Analytics that is 10x more intuitive. 68 health · AGPL-3.0 · 13.2k stars
  • CountlyCountly is a privacy-first, AI-powered analytics and engagement platform for understanding and optimizing… 66 health · Countly Product Analytics - Countly Lite License · 5.9k stars

All 24 projects in Web analytics

Questions about OpenReplay

Is OpenReplay open source?

Yes. OpenReplay is published under AGPL-3.0, an OSI-approved open-source license. Some features are kept under a separate paid license in the same repository.

Is OpenReplay still maintained?

Its health score is 76 of 100 (actively developed). It had 282 commits in the last 90 days, the latest on 30 October 2026, and its latest release came out on 25 September 2026.

Did OpenReplay change its license?

Yes. It moved from MIT to AGPL-3.0 on 30 August 2024.

How do I run OpenReplay?

You can run it with Docker, on Kubernetes with the Helm chart in the repository. The README on GitHub has the exact steps.

What are the alternatives to OpenReplay?

Close alternatives in the Web analytics category include PostHog, Umami, Highlight.