A
openreplay
87.6
13,157 stars · license n/a
Analytics
OpenSearch leads by 5.3 · narrow
A
87.6
13,157 stars · license n/a
B · leads
92.9
14,016 stars · Apache-2.0
openreplay versus OpenSearch 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; OpenSearch is written mainly in Java. The composite score is 87.6 for openreplay and 92.9 for OpenSearch.
OpenSearch has 14,016 GitHub stars to openreplay's 13,157, a gap of 859 (1.07×). Forks are 891 for openreplay and 3,088 for OpenSearch. On the log scale used inside this pair, adoption is 99 versus 100, and the fork community is 84 versus 100.
Push history: openreplay was last pushed on 17 November 2026 (0 days ago), and OpenSearch was last pushed on 17 November 2026 (0 days ago). Open issues stand at 193 for openreplay (0.015 per star) and 3,385 for OpenSearch (0.242 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. OpenSearch 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 OpenSearch. This is a procurement signal, not legal advice.
In Analytics, both openreplay (13,157 stars) and OpenSearch (14,016 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, OpenSearch is open source.
The lead is split. openreplay is furthest ahead on issue health (84 to 34), while OpenSearch is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.
OpenSearch finishes ahead at 92.9 against openreplay at 87.6, a 5.3 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 | OpenSearch |
|---|---|---|
| GitHub stars | 13,157 | 14,016 |
| Forks | 891 | 3,088 |
| Open issues | 193 | 3,385 |
| Adoption | 99 | 100 |
| Activity | 100 | 100 |
| Community | 84 | 100 |
| Issue health | 84 | 34 |
| License | 30 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 87.6 | 92.9 |
Session replay, cobrowsing and product analytics you can self-host. Best for reproducing issues and iterating on your product.
🔎 Open source distributed and RESTful search engine.
OpenSearch has more GitHub stars: 14,016 versus 13,157 for openreplay. The gap is 859 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both openreplay and OpenSearch 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. OpenSearch 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.
OpenSearch scores 92.9 and openreplay scores 87.6. This page calls that a narrow lead for OpenSearch.