A · level
openreplay
90.0
13,157 stars · license n/a
Analytics
Too close to call · 90.0 to 90.6
A · level
90.0
13,157 stars · license n/a
B · level
90.6
13,328 stars · AGPL-3.0
openreplay versus rybbit is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in TypeScript. The composite score is 90.0 for openreplay and 90.6 for rybbit.
rybbit has 13,328 GitHub stars to openreplay's 13,157, a gap of 171 (1.01×). Forks are 891 for openreplay and 791 for rybbit. On the log scale used inside this pair, adoption is 100 versus 100, and the fork community is 100 versus 98.
Push history: openreplay was last pushed on 17 November 2026 (0 days ago), and rybbit was last pushed on 13 November 2026 (4 days ago). Open issues stand at 193 for openreplay (0.015 per star) and 212 for rybbit (0.016 per star). Issue-health scores are 84 and 84; activity scores are 100 and 92.
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. rybbit is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. License scores in this pair are 30 for openreplay and 52 for rybbit. This is a procurement signal, not legal advice.
In Analytics, both openreplay (13,157 stars) and rybbit (13,328 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, rybbit is open source.
The lead is split. openreplay is furthest ahead on recent activity (100 to 92), while rybbit is furthest ahead on license flexibility (52 to 30). Choose the dimension a rollout cannot compromise on.
Composite score: openreplay 90.0, rybbit 90.6. The margin is under one point, so this page calls a tie. Use the dimension breakdown rather than the headline number.
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 | rybbit |
|---|---|---|
| GitHub stars | 13,157 | 13,328 |
| Forks | 891 | 791 |
| Open issues | 193 | 212 |
| Adoption | 100 | 100 |
| Activity | 100 | 92 |
| Community | 100 | 98 |
| Issue health | 84 | 84 |
| License | 30 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 90.0 | 90.6 |
Session replay, cobrowsing and product analytics you can self-host. Best for reproducing issues and iterating on your product.
🐸 Rybbit - open-source and privacy-friendly alternative to Google Analytics that is 10x more intuitive.
rybbit has more GitHub stars: 13,328 versus 13,157 for openreplay. The gap is 171 stars.
openreplay was pushed more recently: 17 November 2026 versus 13 November 2026 for rybbit. That is 4 days apart.
Yes. This catalog marks both openreplay and rybbit 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. rybbit is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Neither tool clears a one-point margin. openreplay scores 90.0 and rybbit scores 90.6.