A
Metabase
89.1
50,382 stars · AGPL-3.0
Analytics
Umami leads by 9.3 · clear
A
89.1
50,382 stars · AGPL-3.0
B · leads
98.4
40,194 stars · MIT
Metabase versus Umami is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Metabase is written mainly in Clojure; Umami is written mainly in TypeScript. The composite score is 89.1 for Metabase and 98.4 for Umami.
Metabase has 50,382 GitHub stars to Umami's 40,194, a gap of 10,188 (1.25×). Forks are 7,016 for Metabase and 8,567 for Umami. On the log scale used inside this pair, adoption is 100 versus 98, and the fork community is 98 versus 100.
Push history: Metabase 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 4,696 for Metabase (0.093 per star) and 136 for Umami (0.003 per star). Issue-health scores are 52 and 96; activity scores are 100 and 100.
Metabase 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 Metabase and 96 for Umami. This is a procurement signal, not legal advice.
In Analytics, both Metabase (50,382 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: Metabase is freemium, Umami is open source.
The lead is split. Metabase is furthest ahead on adoption (100 to 98), while Umami is furthest ahead on issue health (96 to 52). Choose the dimension a rollout cannot compromise on.
Umami finishes ahead at 98.4 against Metabase at 89.1, a 9.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 | Metabase | Umami |
|---|---|---|
| GitHub stars | 50,382 | 40,194 |
| Forks | 7,016 | 8,567 |
| Open issues | 4,696 | 136 |
| Adoption | 100 | 98 |
| Activity | 100 | 100 |
| Community | 98 | 100 |
| Issue health | 52 | 96 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 89.1 | 98.4 |
Metabase is a business-intelligence tool that lets teams ask questions of a SQL database without writing a report from scratch. It is commonly self-hosted next to the warehouse it reads.
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.
Metabase has more GitHub stars: 50,382 versus 40,194 for Umami. The gap is 10,188 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Metabase and Umami as self-hostable. Confirm each project's deploy docs before you plan a migration.
Metabase 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 98.4 and Metabase scores 89.1. This page calls that a clear lead for Umami.