A
openreplay
88.1
13,157 stars · license n/a
Analytics
starrocks leads by 4.6 · narrow
A
88.1
13,157 stars · license n/a
B · leads
92.7
12,261 stars · Apache-2.0
openreplay versus starrocks 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; starrocks is written mainly in Java. The composite score is 88.1 for openreplay and 92.7 for starrocks.
openreplay has 13,157 GitHub stars to starrocks's 12,261, a gap of 896 (1.07×). Forks are 891 for openreplay and 2,679 for starrocks. On the log scale used inside this pair, adoption is 100 versus 99, and the fork community is 86 versus 100.
Push history: openreplay was last pushed on 17 November 2026 (0 days ago), and starrocks was last pushed on 17 November 2026 (0 days ago). Open issues stand at 193 for openreplay (0.015 per star) and 1,753 for starrocks (0.143 per star). Issue-health scores are 84 and 34; 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. starrocks 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 starrocks. This is a procurement signal, not legal advice.
In Analytics, both openreplay (13,157 stars) and starrocks (12,261 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, starrocks is open source.
The lead is split. openreplay is furthest ahead on issue health (84 to 34), while starrocks is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.
starrocks finishes ahead at 92.7 against openreplay at 88.1, a 4.6 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 | starrocks |
|---|---|---|
| GitHub stars | 13,157 | 12,261 |
| Forks | 891 | 2,679 |
| Open issues | 193 | 1,753 |
| Adoption | 100 | 99 |
| Activity | 100 | 100 |
| Community | 86 | 100 |
| Issue health | 84 | 34 |
| License | 30 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 88.1 | 92.7 |
Session replay, cobrowsing and product analytics you can self-host. Best for reproducing issues and iterating on your product.
The world's fastest open query engine for sub-second analytics both on and off the data lakehouse. With the flexibility to support nearly any scenario, StarRocks provides best-in-class performance for multi-dimensional analytics, real-time analytics, and ad-hoc queries. A Linux Foundation project.
openreplay has more GitHub stars: 13,157 versus 12,261 for starrocks. The gap is 896 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both openreplay and starrocks 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. starrocks 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.
starrocks scores 92.7 and openreplay scores 88.1. This page calls that a narrow lead for starrocks.