A
openobserve
89.7
23,090 stars · AGPL-3.0
Analytics
redash leads by 6.8 · narrow
A
89.7
23,090 stars · AGPL-3.0
B · leads
96.5
28,887 stars · BSD-2-Clause
openobserve versus redash 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 89.7 for openobserve and 96.5 for redash.
redash has 28,887 GitHub stars to openobserve's 23,090, a gap of 5,797 (1.25×). Forks are 1,203 for openobserve and 4,645 for redash. On the log scale used inside this pair, adoption is 98 versus 100, and the fork community is 84 versus 100.
Push history: openobserve was last pushed on 17 November 2026 (0 days ago), and redash was last pushed on 14 November 2026 (3 days ago). Open issues stand at 226 for openobserve (0.010 per star) and 780 for redash (0.027 per star). Issue-health scores are 84 and 70; 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. redash is listed as BSD-2-Clause, 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 52 for openobserve and 96 for redash. This is a procurement signal, not legal advice.
In Analytics, both openobserve (23,090 stars) and redash (28,887 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, redash is open source.
The lead is split. openobserve is furthest ahead on issue health (84 to 70), while redash is furthest ahead on license flexibility (96 to 52). Choose the dimension a rollout cannot compromise on.
redash finishes ahead at 96.5 against openobserve at 89.7, a 6.8 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 | redash |
|---|---|---|
| GitHub stars | 23,090 | 28,887 |
| Forks | 1,203 | 4,645 |
| Open issues | 226 | 780 |
| Adoption | 98 | 100 |
| Activity | 100 | 100 |
| Community | 84 | 100 |
| Issue health | 84 | 70 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 89.7 | 96.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.
Make Your Company Data Driven. Connect to any data source, easily visualize, dashboard and share your data.
redash has more GitHub stars: 28,887 versus 23,090 for openobserve. The gap is 5,797 stars.
openobserve was pushed more recently: 17 November 2026 versus 14 November 2026 for redash. That is 3 days apart.
Yes. This catalog marks both openobserve and redash 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. redash is listed as BSD-2-Clause, 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.
redash scores 96.5 and openobserve scores 89.7. This page calls that a narrow lead for redash.