A
openobserve
87.8
23,090 stars · AGPL-3.0
Analytics
Umami leads by 11.3 · clear
A
87.8
23,090 stars · AGPL-3.0
B · leads
99.1
40,194 stars · MIT
openobserve versus Umami 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 87.8 for openobserve and 99.1 for Umami.
Umami has 40,194 GitHub stars to openobserve's 23,090, a gap of 17,104 (1.74×). Forks are 1,203 for openobserve and 8,567 for Umami. On the log scale used inside this pair, adoption is 95 versus 100, and the fork community is 78 versus 100.
Push history: openobserve was last pushed on 17 November 2026 (0 days ago), and Umami was last pushed on 17 November 2026 (0 days ago). Open issues stand at 226 for openobserve (0.010 per star) and 136 for Umami (0.003 per star). Issue-health scores are 84 and 96; 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. Umami is listed as MIT, 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 Umami. This is a procurement signal, not legal advice.
In Analytics, both openobserve (23,090 stars) and Umami (40,194 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, Umami is open source.
Umami is ahead on every scored dimension that is not level. Level dimensions: recent activity, self-hosting. The widest gap is license flexibility at 44 points (52 vs 96), and the tightest is self-hosting at 0 points (100 vs 100).
Umami finishes ahead at 99.1 against openobserve at 87.8, a 11.3 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 | openobserve | Umami |
|---|---|---|
| GitHub stars | 23,090 | 40,194 |
| Forks | 1,203 | 8,567 |
| Open issues | 226 | 136 |
| Adoption | 95 | 100 |
| Activity | 100 | 100 |
| Community | 78 | 100 |
| Issue health | 84 | 96 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 87.8 | 99.1 |
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.
Umami is a small web analytics product with a simple dashboard over page and event data. It is MIT-licensed and is usually chosen when a team wants a short self-hosted setup.
Umami has more GitHub stars: 40,194 versus 23,090 for openobserve. The gap is 17,104 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both openobserve and Umami 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. Umami is listed as MIT, 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.
Umami scores 99.1 and openobserve scores 87.8. This page calls that a clear lead for Umami.