A · leads
Metabase
89.4
50,382 stars · AGPL-3.0
Analytics
Metabase leads by 26.7 · decisive
A · leads
89.4
50,382 stars · AGPL-3.0
B
62.7
2,004 stars · MIT
Metabase versus tokencost 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; tokencost is written mainly in Python. The composite score is 89.4 for Metabase and 62.7 for tokencost.
Metabase has 50,382 GitHub stars to tokencost's 2,004, a gap of 48,378 (25.14×). Forks are 7,016 for Metabase and 109 for tokencost. On the log scale used inside this pair, adoption is 100 versus 70, and the fork community is 100 versus 53.
Push history: Metabase was last pushed on 17 November 2026 (0 days ago), and tokencost was last pushed on 05 September 2025 (438 days ago). Open issues stand at 4,696 for Metabase (0.093 per star) and 31 for tokencost (0.015 per star). Issue-health scores are 52 and 84; activity scores are 100 and 16.
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. tokencost 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 tokencost. This is a procurement signal, not legal advice.
In Analytics, both Metabase (50,382 stars) and tokencost (2,004 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, tokencost is open source.
The lead is split. Metabase is furthest ahead on recent activity (100 to 16), while tokencost is furthest ahead on license flexibility (96 to 52). Choose the dimension a rollout cannot compromise on.
Metabase finishes ahead at 89.4 against tokencost at 62.7, a 26.7 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 | tokencost |
|---|---|---|
| GitHub stars | 50,382 | 2,004 |
| Forks | 7,016 | 109 |
| Open issues | 4,696 | 31 |
| Adoption | 100 | 70 |
| Activity | 100 | 16 |
| Community | 100 | 53 |
| Issue health | 52 | 84 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 89.4 | 62.7 |
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.
Easy token price estimates for 400+ LLMs. TokenOps.
Metabase has more GitHub stars: 50,382 versus 2,004 for tokencost. The gap is 48,378 stars.
Metabase was pushed more recently: 17 November 2026 versus 05 September 2025 for tokencost. That is 438 days apart.
Yes. This catalog marks both Metabase and tokencost 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. tokencost 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 tokencost scores 62.7. This page calls that a decisive lead for Metabase.