A · leads
Metabase
89.4
50,382 stars · AGPL-3.0
Analytics
Metabase leads by 13.2 · clear
A · leads
89.4
50,382 stars · AGPL-3.0
B
76.2
2,214 stars · MIT
Metabase versus ML 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; ML is written mainly in PHP. The composite score is 89.4 for Metabase and 76.2 for ML.
Metabase has 50,382 GitHub stars to ML's 2,214, a gap of 48,168 (22.76×). Forks are 7,016 for Metabase and 196 for ML. On the log scale used inside this pair, adoption is 100 versus 71, and the fork community is 100 versus 60.
Push history: Metabase was last pushed on 17 November 2026 (0 days ago), and ML was last pushed on 27 October 2026 (20 days ago). Open issues stand at 4,696 for Metabase (0.093 per star) and 65 for ML (0.029 per star). Issue-health scores are 52 and 70; 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. ML 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 ML. This is a procurement signal, not legal advice.
In Analytics, both Metabase (50,382 stars) and ML (2,214 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, ML is open source.
The lead is split. Metabase is furthest ahead on fork community (100 to 60), while ML is furthest ahead on license flexibility (96 to 52). Choose the dimension a rollout cannot compromise on.
Metabase finishes ahead at 89.4 against ML at 76.2, a 13.2 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 | ML |
|---|---|---|
| GitHub stars | 50,382 | 2,214 |
| Forks | 7,016 | 196 |
| Open issues | 4,696 | 65 |
| Adoption | 100 | 71 |
| Activity | 100 | 78 |
| Community | 100 | 60 |
| Issue health | 52 | 70 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 89.4 | 76.2 |
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 high-level machine learning and deep learning library for the PHP language.
Metabase has more GitHub stars: 50,382 versus 2,214 for ML. The gap is 48,168 stars.
Metabase was pushed more recently: 17 November 2026 versus 27 October 2026 for ML. That is 20 days apart.
Yes. This catalog marks both Metabase and ML 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. ML 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 ML scores 76.2. This page calls that a clear lead for Metabase.