A
OpenSearch
88.0
14,016 stars · Apache-2.0
Analytics
Umami leads by 11.1 · clear
A
88.0
14,016 stars · Apache-2.0
B · leads
99.1
40,194 stars · MIT
OpenSearch versus Umami is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. OpenSearch is written mainly in Java; Umami is written mainly in TypeScript. The composite score is 88.0 for OpenSearch and 99.1 for Umami.
Umami has 40,194 GitHub stars to OpenSearch's 14,016, a gap of 26,178 (2.87×). Forks are 3,088 for OpenSearch and 8,567 for Umami. On the log scale used inside this pair, adoption is 90 versus 100, and the fork community is 89 versus 100.
Push history: OpenSearch 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 3,385 for OpenSearch (0.242 per star) and 136 for Umami (0.003 per star). Issue-health scores are 34 and 96; activity scores are 100 and 100.
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. 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 96 for OpenSearch and 96 for Umami. This is a procurement signal, not legal advice.
In Analytics, both OpenSearch (14,016 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: OpenSearch is open source, Umami is open source.
Umami is ahead on every scored dimension that is not level. Level dimensions: recent activity, license flexibility, self-hosting. The widest gap is issue health at 62 points (34 vs 96), and the tightest is self-hosting at 0 points (100 vs 100).
Umami finishes ahead at 99.1 against OpenSearch at 88.0, a 11.1 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 | OpenSearch | Umami |
|---|---|---|
| GitHub stars | 14,016 | 40,194 |
| Forks | 3,088 | 8,567 |
| Open issues | 3,385 | 136 |
| Adoption | 90 | 100 |
| Activity | 100 | 100 |
| Community | 89 | 100 |
| Issue health | 34 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 88.0 | 99.1 |
🔎 Open source distributed and RESTful search engine.
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 14,016 for OpenSearch. The gap is 26,178 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both OpenSearch and Umami as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. 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 OpenSearch scores 88.0. This page calls that a clear lead for Umami.