A · leads
Metabase
89.4
50,382 stars · AGPL-3.0
Analytics
Metabase leads by 19.5 · decisive
A · leads
89.4
50,382 stars · AGPL-3.0
B
69.9
2,020 stars · license n/a
Metabase versus nao 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; nao is written mainly in TypeScript. The composite score is 89.4 for Metabase and 69.9 for nao.
Metabase has 50,382 GitHub stars to nao's 2,020, a gap of 48,362 (24.94×). Forks are 7,016 for Metabase and 305 for nao. On the log scale used inside this pair, adoption is 100 versus 70, and the fork community is 100 versus 65.
Push history: Metabase was last pushed on 17 November 2026 (0 days ago), and nao was last pushed on 17 November 2026 (0 days ago). Open issues stand at 4,696 for Metabase (0.093 per star) and 381 for nao (0.189 per star). Issue-health scores are 52 and 34; 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. 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. License scores in this pair are 52 for Metabase and 30 for nao. This is a procurement signal, not legal advice.
In Analytics, both Metabase (50,382 stars) and nao (2,020 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, nao is unpriced in this catalog.
Metabase is ahead on every scored dimension that is not level. Level dimensions: recent activity, self-hosting. The widest gap is fork community at 35 points (100 vs 65), and the tightest is self-hosting at 0 points (100 vs 100).
Metabase finishes ahead at 89.4 against nao at 69.9, a 19.5 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 | Metabase | nao |
|---|---|---|
| GitHub stars | 50,382 | 2,020 |
| Forks | 7,016 | 305 |
| Open issues | 4,696 | 381 |
| Adoption | 100 | 70 |
| Activity | 100 | 100 |
| Community | 100 | 65 |
| Issue health | 52 | 34 |
| License | 52 | 30 |
| Self-hosting | 100 | 100 |
| Composite | 89.4 | 69.9 |
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.
👾 nao is the #1 open source agentic BI. (1) Create context with nao-core cli, (2) deploy nao chat interface for everyone
Metabase has more GitHub stars: 50,382 versus 2,020 for nao. The gap is 48,362 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Metabase and nao 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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Metabase scores 89.4 and nao scores 69.9. This page calls that a decisive lead for Metabase.