OSI-licensed only · self-hostable
LogRocket records user sessions and ties them to errors, network requests and performance data. Open-source tools cover the same ground, from full self-hosted replay platforms to the rrweb library that many of them are built around.
Every project below is under an OSI-approved licence (MIT, AGPL-3.0), checked against its repository. PostHog and OpenReplay keep enterprise folders under other licences, noted where relevant. Sentry also offers session replay but its licence is not OSI-approved.
Licences checked against each repository on November 7, 2026.
| Tool | Best for | Licence | Runs as |
|---|---|---|---|
| PostHog | Replay plus product analytics | MIT | Docker |
| OpenReplay | Self-hosted session replay for debugging | AGPL-3.0 | Docker |
| HyperDX | Replay joined with logs and traces | MIT | Docker |
| rrweb | Record and replay library to build your own | MIT | Server |
| OpenObserve | Frontend monitoring with replay in an observability stack | AGPL-3.0 | Docker |
Best for: Replay plus product analytics
An all-in-one product platform with analytics, session replay, feature flags and experiments. Content outside the ee/ directory is MIT.
Best for: Self-hosted session replay for debugging
A session replay and product analytics tool aimed at developers, with replay, dev tools and error tracking. Defaults to AGPL-3.0 with ee/ and some MIT directories.
Best for: Replay joined with logs and traces
An observability platform that correlates session replay with logs, traces and metrics in one search interface.
Best for: Record and replay library to build your own
A library for recording and replaying web sessions by capturing DOM changes. Many replay tools build on it.
Best for: Frontend monitoring with replay in an observability stack
An observability platform whose README lists real user monitoring with Core Web Vitals, error tracking and session replay alongside logs, metrics and traces.
One email a week with the open-source projects, launches and releases added to TechLogHub. Unsubscribe in one click.
One email a week: new and trending developer tools, fresh comparisons, and what shipped. Unsubscribe in one click.
| If you need… | Start with |
|---|---|
| Replay plus product analytics | PostHog |
| Developer-first self-hosted replay | OpenReplay |
| Replay tied to backend traces | HyperDX |
| Build your own recorder | rrweb |
| Frontend monitoring in a wider observability stack | OpenObserve |
Public source code, but under licences the Open Source Initiative doesn't approve. Fine to use; read the terms first.
Source is public and self-hosting is allowed, but the Functional Source License restricts competing uses, so it is not OSI-approved. Each version converts to Apache-2.0 after two years.
Quick answers to common questions
Yes. OpenReplay and PostHog both offer self-hostable session replay, and rrweb is the underlying recording library many tools use.
Sentry's repository uses the Functional Source License (FSL-1.1-Apache-2.0), which is not an OSI-approved licence.
It can be. Mask sensitive inputs and apply consent rules for your region. Self-hosting keeps recordings on your servers.
Yes. With rrweb or a self-hosted platform, recordings are stored on infrastructure you control.
Hosting costs and complexity vary. PostHog and OpenReplay document Docker or Kubernetes setups, while rrweb needs you to build storage and UI yourself.
List it on TechLogHub and we'll review it for this page.
