A
dashboards
80.0
11,031 stars · MIT
Analytics
openreplay leads by 9.1 · clear
A
80.0
11,031 stars · MIT
B · leads
89.1
13,157 stars · license n/a
dashboards versus openreplay is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. dashboards is written mainly in HTML; openreplay is written mainly in TypeScript. The composite score is 80.0 for dashboards and 89.1 for openreplay.
openreplay has 13,157 GitHub stars to dashboards's 11,031, a gap of 2,126 (1.19×). Forks are 1,386 for dashboards and 891 for openreplay. On the log scale used inside this pair, adoption is 98 versus 100, and the fork community is 100 versus 94.
Push history: dashboards was last pushed on 02 November 2021 (1841 days ago), and openreplay was last pushed on 17 November 2026 (0 days ago). Open issues stand at 6 for dashboards (0.001 per star) and 193 for openreplay (0.015 per star). Issue-health scores are 96 and 84; activity scores are 16 and 100.
dashboards 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. 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. License scores in this pair are 96 for dashboards and 30 for openreplay. This is a procurement signal, not legal advice.
In Analytics, both dashboards (11,031 stars) and openreplay (13,157 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: dashboards is open source, openreplay is unpriced in this catalog.
The lead is split. dashboards is furthest ahead on license flexibility (96 to 30), while openreplay is furthest ahead on recent activity (100 to 16). Choose the dimension a rollout cannot compromise on.
openreplay finishes ahead at 89.1 against dashboards at 80.0, a 9.1 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 | dashboards | openreplay |
|---|---|---|
| GitHub stars | 11,031 | 13,157 |
| Forks | 1,386 | 891 |
| Open issues | 6 | 193 |
| Adoption | 98 | 100 |
| Activity | 16 | 100 |
| Community | 100 | 94 |
| Issue health | 96 | 84 |
| License | 96 | 30 |
| Self-hosting | 100 | 100 |
| Composite | 80.0 | 89.1 |
Responsive dashboard templates 📊✨
Session replay, cobrowsing and product analytics you can self-host. Best for reproducing issues and iterating on your product.
openreplay has more GitHub stars: 13,157 versus 11,031 for dashboards. The gap is 2,126 stars.
openreplay was pushed more recently: 17 November 2026 versus 02 November 2021 for dashboards. That is 1841 days apart.
Yes. This catalog marks both dashboards and openreplay as self-hostable. Confirm each project's deploy docs before you plan a migration.
dashboards 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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
openreplay scores 89.1 and dashboards scores 80.0. This page calls that a clear lead for openreplay.