A
openreplay
89.2
13,157 stars · license n/a
Analytics
perspective leads by 9.4 · clear
A
89.2
13,157 stars · license n/a
B · leads
98.6
11,436 stars · Apache-2.0
openreplay versus perspective 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; perspective is written mainly in Rust. The composite score is 89.2 for openreplay and 98.6 for perspective.
openreplay has 13,157 GitHub stars to perspective's 11,436, a gap of 1,721 (1.15×). Forks are 891 for openreplay and 1,358 for perspective. On the log scale used inside this pair, adoption is 100 versus 98, and the fork community is 94 versus 100.
Push history: openreplay was last pushed on 17 November 2026 (0 days ago), and perspective was last pushed on 16 November 2026 (1 day ago). Open issues stand at 193 for openreplay (0.015 per star) and 29 for perspective (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. perspective is listed as Apache-2.0, 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 perspective. This is a procurement signal, not legal advice.
In Analytics, both openreplay (13,157 stars) and perspective (11,436 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, perspective is open source.
The lead is split. openreplay is furthest ahead on adoption (100 to 98), while perspective is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.
perspective finishes ahead at 98.6 against openreplay at 89.2, a 9.4 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 | perspective |
|---|---|---|
| GitHub stars | 13,157 | 11,436 |
| Forks | 891 | 1,358 |
| Open issues | 193 | 29 |
| Adoption | 100 | 98 |
| Activity | 100 | 100 |
| Community | 94 | 100 |
| Issue health | 84 | 96 |
| License | 30 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 89.2 | 98.6 |
Session replay, cobrowsing and product analytics you can self-host. Best for reproducing issues and iterating on your product.
A data visualization and analytics component, especially well-suited for large and/or streaming datasets.
openreplay has more GitHub stars: 13,157 versus 11,436 for perspective. The gap is 1,721 stars.
openreplay was pushed more recently: 17 November 2026 versus 16 November 2026 for perspective. That is 1 days apart.
Yes. This catalog marks both openreplay and perspective 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. perspective is listed as Apache-2.0, 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.
perspective scores 98.6 and openreplay scores 89.2. This page calls that a clear lead for perspective.