A
openreplay
84.7
13,157 stars · license n/a
Analytics
redash leads by 11.8 · clear
A
84.7
13,157 stars · license n/a
B · leads
96.5
28,887 stars · BSD-2-Clause
openreplay versus redash 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 84.7 for openreplay and 96.5 for redash.
redash has 28,887 GitHub stars to openreplay's 13,157, a gap of 15,730 (2.20×). Forks are 891 for openreplay and 4,645 for redash. On the log scale used inside this pair, adoption is 92 versus 100, and the fork community is 80 versus 100.
Push history: openreplay was last pushed on 17 November 2026 (0 days ago), and redash was last pushed on 14 November 2026 (3 days ago). Open issues stand at 193 for openreplay (0.015 per star) and 780 for redash (0.027 per star). Issue-health scores are 84 and 70; 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. redash is listed as BSD-2-Clause, 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 redash. This is a procurement signal, not legal advice.
In Analytics, both openreplay (13,157 stars) and redash (28,887 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, redash is open source.
The lead is split. openreplay is furthest ahead on issue health (84 to 70), while redash is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.
redash finishes ahead at 96.5 against openreplay at 84.7, a 11.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 | redash |
|---|---|---|
| GitHub stars | 13,157 | 28,887 |
| Forks | 891 | 4,645 |
| Open issues | 193 | 780 |
| Adoption | 92 | 100 |
| Activity | 100 | 100 |
| Community | 80 | 100 |
| Issue health | 84 | 70 |
| License | 30 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 84.7 | 96.5 |
Session replay, cobrowsing and product analytics you can self-host. Best for reproducing issues and iterating on your product.
Make Your Company Data Driven. Connect to any data source, easily visualize, dashboard and share your data.
redash has more GitHub stars: 28,887 versus 13,157 for openreplay. The gap is 15,730 stars.
openreplay was pushed more recently: 17 November 2026 versus 14 November 2026 for redash. That is 3 days apart.
Yes. This catalog marks both openreplay and redash 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. redash is listed as BSD-2-Clause, 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.
redash scores 96.5 and openreplay scores 84.7. This page calls that a clear lead for redash.