A
auto_ml
60.5
1,651 stars · MIT
Analytics
Metabase leads by 28.9 · decisive
A
60.5
1,651 stars · MIT
B · leads
89.4
50,382 stars · AGPL-3.0
auto_ml versus Metabase is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. auto_ml is written mainly in Python; Metabase is written mainly in Clojure. The composite score is 60.5 for auto_ml and 89.4 for Metabase.
Metabase has 50,382 GitHub stars to auto_ml's 1,651, a gap of 48,731 (30.52×). Forks are 304 for auto_ml and 7,016 for Metabase. On the log scale used inside this pair, adoption is 68 versus 100, and the fork community is 65 versus 100.
Push history: auto_ml was last pushed on 10 February 2021 (2106 days ago), and Metabase was last pushed on 17 November 2026 (0 days ago). Open issues stand at 187 for auto_ml (0.113 per star) and 4,696 for Metabase (0.093 per star). Issue-health scores are 52 and 52; activity scores are 16 and 100.
auto_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. 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. License scores in this pair are 96 for auto_ml and 52 for Metabase. This is a procurement signal, not legal advice.
In Analytics, both auto_ml (1,651 stars) and Metabase (50,382 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: auto_ml is open source, Metabase is freemium.
The lead is split. auto_ml is furthest ahead on license flexibility (96 to 52), while Metabase is furthest ahead on recent activity (100 to 16). Choose the dimension a rollout cannot compromise on.
Metabase finishes ahead at 89.4 against auto_ml at 60.5, a 28.9 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 | auto_ml | Metabase |
|---|---|---|
| GitHub stars | 1,651 | 50,382 |
| Forks | 304 | 7,016 |
| Open issues | 187 | 4,696 |
| Adoption | 68 | 100 |
| Activity | 16 | 100 |
| Community | 65 | 100 |
| Issue health | 52 | 52 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 60.5 | 89.4 |
[UNMAINTAINED] Automated machine learning for analytics & production
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.
Metabase has more GitHub stars: 50,382 versus 1,651 for auto_ml. The gap is 48,731 stars.
Metabase was pushed more recently: 17 November 2026 versus 10 February 2021 for auto_ml. That is 2106 days apart.
Yes. This catalog marks both auto_ml and Metabase as self-hostable. Confirm each project's deploy docs before you plan a migration.
auto_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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Metabase scores 89.4 and auto_ml scores 60.5. This page calls that a decisive lead for Metabase.