A
labml
64.9
2,327 stars · MIT
Analytics
Metabase leads by 24.5 · decisive
A
64.9
2,327 stars · MIT
B · leads
89.4
50,382 stars · AGPL-3.0
labml versus Metabase is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. labml is written mainly in Python; Metabase is written mainly in Clojure. The composite score is 64.9 for labml and 89.4 for Metabase.
Metabase has 50,382 GitHub stars to labml's 2,327, a gap of 48,055 (21.65×). Forks are 152 for labml and 7,016 for Metabase. On the log scale used inside this pair, adoption is 72 versus 100, and the fork community is 57 versus 100.
Push history: labml was last pushed on 10 April 2025 (586 days ago), and Metabase was last pushed on 17 November 2026 (0 days ago). Open issues stand at 6 for labml (0.003 per star) and 4,696 for Metabase (0.093 per star). Issue-health scores are 96 and 52; activity scores are 16 and 100.
labml 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 labml and 52 for Metabase. This is a procurement signal, not legal advice.
In Analytics, both labml (2,327 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: labml is open source, Metabase is freemium.
The lead is split. labml is furthest ahead on issue health (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 labml at 64.9, a 24.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 | labml | Metabase |
|---|---|---|
| GitHub stars | 2,327 | 50,382 |
| Forks | 152 | 7,016 |
| Open issues | 6 | 4,696 |
| Adoption | 72 | 100 |
| Activity | 16 | 100 |
| Community | 57 | 100 |
| Issue health | 96 | 52 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 64.9 | 89.4 |
🔎 Monitor deep learning model training and hardware usage from your mobile phone 📱
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 2,327 for labml. The gap is 48,055 stars.
Metabase was pushed more recently: 17 November 2026 versus 10 April 2025 for labml. That is 586 days apart.
Yes. This catalog marks both labml and Metabase as self-hostable. Confirm each project's deploy docs before you plan a migration.
labml 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 labml scores 64.9. This page calls that a decisive lead for Metabase.