A
nao
70.3
2,020 stars · license n/a
Analytics
Umami leads by 28.8 · decisive
A
70.3
2,020 stars · license n/a
B · leads
99.1
40,194 stars · MIT
nao 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 70.3 for nao and 99.1 for Umami.
Umami has 40,194 GitHub stars to nao's 2,020, a gap of 38,174 (19.90×). Forks are 305 for nao and 8,567 for Umami. On the log scale used inside this pair, adoption is 72 versus 100, and the fork community is 63 versus 100.
Push history: nao 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 381 for nao (0.189 per star) and 136 for Umami (0.003 per star). Issue-health scores are 34 and 96; activity scores are 100 and 100.
nao is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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 30 for nao and 96 for Umami. This is a procurement signal, not legal advice.
In Analytics, both nao (2,020 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: nao is unpriced in this catalog, 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 66 points (30 vs 96), and the tightest is self-hosting at 0 points (100 vs 100).
Umami finishes ahead at 99.1 against nao at 70.3, a 28.8 point decisive 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 | nao | Umami |
|---|---|---|
| GitHub stars | 2,020 | 40,194 |
| Forks | 305 | 8,567 |
| Open issues | 381 | 136 |
| Adoption | 72 | 100 |
| Activity | 100 | 100 |
| Community | 63 | 100 |
| Issue health | 34 | 96 |
| License | 30 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 70.3 | 99.1 |
👾 nao is the #1 open source agentic BI. (1) Create context with nao-core cli, (2) deploy nao chat interface for everyone
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 2,020 for nao. The gap is 38,174 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both nao and Umami as self-hostable. Confirm each project's deploy docs before you plan a migration.
nao is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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 nao scores 70.3. This page calls that a decisive lead for Umami.