A
lago
86.0
10,891 stars · AGPL-3.0
Analytics
Umami leads by 13.1 · clear
A
86.0
10,891 stars · AGPL-3.0
B · leads
99.1
40,194 stars · MIT
lago versus Umami is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. lago is written mainly in Go; Umami is written mainly in TypeScript. The composite score is 86.0 for lago and 99.1 for Umami.
Umami has 40,194 GitHub stars to lago's 10,891, a gap of 29,303 (3.69×). Forks are 798 for lago and 8,567 for Umami. On the log scale used inside this pair, adoption is 88 versus 100, and the fork community is 74 versus 100.
Push history: lago 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 17 for lago (0.002 per star) and 136 for Umami (0.003 per star). Issue-health scores are 96 and 96; activity scores are 100 and 100.
lago 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 lago and 96 for Umami. This is a procurement signal, not legal advice.
In Analytics, both lago (10,891 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: lago is open source, Umami is open source.
Umami 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 44 points (52 vs 96), and the tightest is self-hosting at 0 points (100 vs 100).
Umami finishes ahead at 99.1 against lago at 86.0, a 13.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 | lago | Umami |
|---|---|---|
| GitHub stars | 10,891 | 40,194 |
| Forks | 798 | 8,567 |
| Open issues | 17 | 136 |
| Adoption | 88 | 100 |
| Activity | 100 | 100 |
| Community | 74 | 100 |
| Issue health | 96 | 96 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 86.0 | 99.1 |
Open Source Metering and Usage Based Billing API ⭐️ Consumption tracking, Subscription management, Pricing iterations, Payment orchestration & Revenue analytics
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 10,891 for lago. The gap is 29,303 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both lago and Umami as self-hostable. Confirm each project's deploy docs before you plan a migration.
lago 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 lago scores 86.0. This page calls that a clear lead for Umami.