A
openreplay
83.9
13,157 stars · license n/a
Analytics
PostHog leads by 10.8 · clear
A
83.9
13,157 stars · license n/a
B · leads
94.7
40,849 stars · MIT
openreplay versus PostHog is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. openreplay is written mainly in TypeScript; PostHog is written mainly in Python. The composite score is 83.9 for openreplay and 94.7 for PostHog.
PostHog has 40,849 GitHub stars to openreplay's 13,157, a gap of 27,692 (3.10×). Forks are 891 for openreplay and 3,696 for PostHog. On the log scale used inside this pair, adoption is 89 versus 100, and the fork community is 83 versus 100.
Push history: openreplay was last pushed on 17 November 2026 (0 days ago), and PostHog was last pushed on 17 November 2026 (0 days ago). Open issues stand at 193 for openreplay (0.015 per star) and 4,463 for PostHog (0.109 per star). Issue-health scores are 84 and 52; activity scores are 100 and 100.
openreplay is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. PostHog is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. License scores in this pair are 30 for openreplay and 96 for PostHog. This is a procurement signal, not legal advice.
In Analytics, both openreplay (13,157 stars) and PostHog (40,849 stars) are marked self-hostable. Deploy scores are 100 and 100. Running either one means you own upgrades, backups, and the license duties that follow a modified copy. Pricing labels on file: openreplay is unpriced in this catalog, PostHog is freemium.
The lead is split. openreplay is furthest ahead on issue health (84 to 52), while PostHog is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.
PostHog finishes ahead at 94.7 against openreplay at 83.9, a 10.8 point clear margin under the published weights.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | openreplay | PostHog |
|---|---|---|
| GitHub stars | 13,157 | 40,849 |
| Forks | 891 | 3,696 |
| Open issues | 193 | 4,463 |
| Adoption | 89 | 100 |
| Activity | 100 | 100 |
| Community | 83 | 100 |
| Issue health | 84 | 52 |
| License | 30 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 83.9 | 94.7 |
Session replay, cobrowsing and product analytics you can self-host. Best for reproducing issues and iterating on your product.
PostHog is a product-analytics suite: events, funnels, session replay, and feature flags. The core is open source and most teams choose between self-hosting and PostHog Cloud.
PostHog has more GitHub stars: 40,849 versus 13,157 for openreplay. The gap is 27,692 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both openreplay and PostHog as self-hostable. Confirm each project's deploy docs before you plan a migration.
openreplay is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. PostHog is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
PostHog scores 94.7 and openreplay scores 83.9. This page calls that a clear lead for PostHog.