A · leads
openobserve
92.6
23,090 stars · AGPL-3.0
Analytics
openobserve leads by 5.1 · narrow
A · leads
92.6
23,090 stars · AGPL-3.0
B
87.5
13,157 stars · license n/a
openobserve versus openreplay 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 92.6 for openobserve and 87.5 for openreplay.
openobserve has 23,090 GitHub stars to openreplay's 13,157, a gap of 9,933 (1.75×). Forks are 1,203 for openobserve and 891 for openreplay. On the log scale used inside this pair, adoption is 100 versus 94, and the fork community is 100 versus 96.
Push history: openobserve was last pushed on 17 November 2026 (0 days ago), and openreplay was last pushed on 17 November 2026 (0 days ago). Open issues stand at 226 for openobserve (0.010 per star) and 193 for openreplay (0.015 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.
openobserve is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. 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 52 for openobserve and 30 for openreplay. This is a procurement signal, not legal advice.
In Analytics, both openobserve (23,090 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: openobserve is open source, openreplay is unpriced in this catalog.
openobserve is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, self-hosting. The widest gap is license flexibility at 22 points (52 vs 30), and the tightest is self-hosting at 0 points (100 vs 100).
openobserve finishes ahead at 92.6 against openreplay at 87.5, a 5.1 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 | openobserve | openreplay |
|---|---|---|
| GitHub stars | 23,090 | 13,157 |
| Forks | 1,203 | 891 |
| Open issues | 226 | 193 |
| Adoption | 100 | 94 |
| Activity | 100 | 100 |
| Community | 100 | 96 |
| Issue health | 84 | 84 |
| License | 52 | 30 |
| Self-hosting | 100 | 100 |
| Composite | 92.6 | 87.5 |
Open source observability platform for logs, metrics, traces, RUM (web, android, ios), Session replay, pipelines, SLO and LLM observability. A sophisticated, simple and highly performant alternative to Datadog, Splunk, and Elasticsearch with 140x lower storage costs and single binary deployment.
Session replay, cobrowsing and product analytics you can self-host. Best for reproducing issues and iterating on your product.
openobserve has more GitHub stars: 23,090 versus 13,157 for openreplay. The gap is 9,933 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both openobserve and openreplay as self-hostable. Confirm each project's deploy docs before you plan a migration.
openobserve is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. 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.
openobserve scores 92.6 and openreplay scores 87.5. This page calls that a narrow lead for openobserve.