A · leads
Metabase
89.4
50,382 stars · AGPL-3.0
Analytics
Metabase leads by 9.8 · clear
A · leads
89.4
50,382 stars · AGPL-3.0
B
79.6
3,031 stars · MIT
Metabase versus stats 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; stats is written mainly in Go. The composite score is 89.4 for Metabase and 79.6 for stats.
Metabase has 50,382 GitHub stars to stats's 3,031, a gap of 47,351 (16.62×). Forks are 7,016 for Metabase and 178 for stats. On the log scale used inside this pair, adoption is 100 versus 74, and the fork community is 100 versus 59.
Push history: Metabase was last pushed on 17 November 2026 (0 days ago), and stats was last pushed on 25 October 2026 (23 days ago). Open issues stand at 4,696 for Metabase (0.093 per star) and 2 for stats (0.001 per star). Issue-health scores are 52 and 96; activity scores are 100 and 78.
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. stats 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 stats. This is a procurement signal, not legal advice.
In Analytics, both Metabase (50,382 stars) and stats (3,031 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, stats is open source.
The lead is split. Metabase is furthest ahead on fork community (100 to 59), while stats is furthest ahead on issue health (96 to 52). Choose the dimension a rollout cannot compromise on.
Metabase finishes ahead at 89.4 against stats at 79.6, a 9.8 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 | stats |
|---|---|---|
| GitHub stars | 50,382 | 3,031 |
| Forks | 7,016 | 178 |
| Open issues | 4,696 | 2 |
| Adoption | 100 | 74 |
| Activity | 100 | 78 |
| Community | 100 | 59 |
| Issue health | 52 | 96 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 89.4 | 79.6 |
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.
A well tested and comprehensive Golang statistics library package with no dependencies.
Metabase has more GitHub stars: 50,382 versus 3,031 for stats. The gap is 47,351 stars.
Metabase was pushed more recently: 17 November 2026 versus 25 October 2026 for stats. That is 23 days apart.
Yes. This catalog marks both Metabase and stats 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. stats 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.
Metabase scores 89.4 and stats scores 79.6. This page calls that a clear lead for Metabase.