A
openreplay
90.0
13,157 stars · license n/a
Analytics
uPlot leads by 5.9 · narrow
A
90.0
13,157 stars · license n/a
B · leads
95.9
10,650 stars · MIT
openreplay versus uPlot 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; uPlot is written mainly in JavaScript. The composite score is 90.0 for openreplay and 95.9 for uPlot.
openreplay has 13,157 GitHub stars to uPlot's 10,650, a gap of 2,507 (1.24×). Forks are 891 for openreplay and 472 for uPlot. On the log scale used inside this pair, adoption is 100 versus 98, and the fork community is 100 versus 91.
Push history: openreplay was last pushed on 17 November 2026 (0 days ago), and uPlot was last pushed on 17 November 2026 (0 days ago). Open issues stand at 193 for openreplay (0.015 per star) and 132 for uPlot (0.012 per star). Issue-health scores are 84 and 84; 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. uPlot 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 uPlot. This is a procurement signal, not legal advice.
In Analytics, both openreplay (13,157 stars) and uPlot (10,650 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, uPlot is open source.
The lead is split. openreplay is furthest ahead on fork community (100 to 91), while uPlot is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.
uPlot finishes ahead at 95.9 against openreplay at 90.0, a 5.9 point narrow 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 | uPlot |
|---|---|---|
| GitHub stars | 13,157 | 10,650 |
| Forks | 891 | 472 |
| Open issues | 193 | 132 |
| Adoption | 100 | 98 |
| Activity | 100 | 100 |
| Community | 100 | 91 |
| Issue health | 84 | 84 |
| License | 30 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 90.0 | 95.9 |
Session replay, cobrowsing and product analytics you can self-host. Best for reproducing issues and iterating on your product.
📈 A small, fast chart for time series, lines, areas, ohlc & bars
openreplay has more GitHub stars: 13,157 versus 10,650 for uPlot. The gap is 2,507 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both openreplay and uPlot 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. uPlot 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.
uPlot scores 95.9 and openreplay scores 90.0. This page calls that a narrow lead for uPlot.