A
openreplay
82.9
13,157 stars · license n/a
Analytics
Umami leads by 16.2 · decisive
A
82.9
13,157 stars · license n/a
B · leads
99.1
40,194 stars · MIT
openreplay versus Umami 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 82.9 for openreplay and 99.1 for Umami.
Umami has 40,194 GitHub stars to openreplay's 13,157, a gap of 27,037 (3.05×). Forks are 891 for openreplay and 8,567 for Umami. On the log scale used inside this pair, adoption is 90 versus 100, and the fork community is 75 versus 100.
Push history: openreplay was last pushed on 17 November 2026 (0 days ago), and Umami was last pushed on 17 November 2026 (0 days ago). Open issues stand at 193 for openreplay (0.015 per star) and 136 for Umami (0.003 per star). Issue-health scores are 84 and 96; 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. Umami 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 Umami. This is a procurement signal, not legal advice.
In Analytics, both openreplay (13,157 stars) and Umami (40,194 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, Umami is open source.
Umami is ahead on every scored dimension that is not level. Level dimensions: recent activity, self-hosting. The widest gap is license flexibility at 66 points (30 vs 96), and the tightest is self-hosting at 0 points (100 vs 100).
Umami finishes ahead at 99.1 against openreplay at 82.9, a 16.2 point decisive 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 | Umami |
|---|---|---|
| GitHub stars | 13,157 | 40,194 |
| Forks | 891 | 8,567 |
| Open issues | 193 | 136 |
| Adoption | 90 | 100 |
| Activity | 100 | 100 |
| Community | 75 | 100 |
| Issue health | 84 | 96 |
| License | 30 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 82.9 | 99.1 |
Session replay, cobrowsing and product analytics you can self-host. Best for reproducing issues and iterating on your product.
Umami is a small web analytics product with a simple dashboard over page and event data. It is MIT-licensed and is usually chosen when a team wants a short self-hosted setup.
Umami has more GitHub stars: 40,194 versus 13,157 for openreplay. The gap is 27,037 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both openreplay and Umami 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. Umami 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.
Umami scores 99.1 and openreplay scores 82.9. This page calls that a decisive lead for Umami.