rrweb
Open-source web session replay library. Pixel-perfect recording and playback APIs used by major platforms (PostHog, OpenReplay and many tools).
Our Verdict
The de facto open-source replay engine, but it's a building block, not a product you deploy to PMs.
Pros
- Battle-tested open-source engine behind major platforms
- Pixel-perfect DOM recording with replay APIs
- Strong community and extension ecosystem
- MIT license lets you build proprietary tools on top
Cons
- Just a library, no storage, UI or analytics included
- You own scaling, privacy masking and retention logic
- Event payloads can be heavy without tuning
- Mobile support requires separate native bridges
Best for: Engineers building custom replay, QA or debugging tooling in-house.
Not for: Non-technical teams expecting a hosted dashboard out of the box.
When to Use rrweb
Good fit if you need
- Pixel-perfect DOM recording for session replay platforms
- Embed session replay into custom analytics products
- Privacy-first recording with configurable field masking
- Open-source replay library powering PostHog and OpenReplay
Lock-in Assessment
Low 5/5
Lock-in Score 5/5
Pricing
Price wrong?rrweb Pricing
- Pricing Model
- free
- Free Tier
- Yes
- Entry Price
- —
- Enterprise Available
- No
- Transparency Score
- —
Beta — estimates may differ from actual pricing
1,000
1001K10K100K1M
Estimated Monthly Cost
$25
Estimated Annual Cost
$300
Estimates are approximate and may not reflect current pricing. Always check the official pricing page.
Project Health
C
Health Score
19.5k 1.6k
Bus Factor
8
Last Commit
1 months
Release Freq
106d
Open Issues
403
Issue Response
N/A
License
MIT
Last checked: 2026-04-21
Community Discussion
Comments powered by Giscus (GitHub Discussions). You need a GitHub account to comment.