A
chartbrew
73.8
4,097 stars · license n/a
Analytics
Metabase leads by 15.6 · decisive
A
73.8
4,097 stars · license n/a
B · leads
89.4
50,382 stars · AGPL-3.0
chartbrew versus Metabase is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. chartbrew is written mainly in JavaScript; Metabase is written mainly in Clojure. The composite score is 73.8 for chartbrew and 89.4 for Metabase.
Metabase has 50,382 GitHub stars to chartbrew's 4,097, a gap of 46,285 (12.30×). Forks are 458 for chartbrew and 7,016 for Metabase. On the log scale used inside this pair, adoption is 77 versus 100, and the fork community is 69 versus 100.
Push history: chartbrew was last pushed on 14 November 2026 (3 days ago), and Metabase was last pushed on 17 November 2026 (0 days ago). Open issues stand at 2 for chartbrew (0.000 per star) and 4,696 for Metabase (0.093 per star). Issue-health scores are 96 and 52; activity scores are 100 and 100.
chartbrew is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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 30 for chartbrew and 52 for Metabase. This is a procurement signal, not legal advice.
Only Metabase is marked self-hostable here (50,382 stars, deploy score 100). chartbrew is not (4,097 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: chartbrew is unpriced in this catalog, Metabase is freemium.
The lead is split. chartbrew is furthest ahead on issue health (96 to 52), while Metabase is furthest ahead on self-hosting (100 to 35). Choose the dimension a rollout cannot compromise on.
Metabase finishes ahead at 89.4 against chartbrew at 73.8, a 15.6 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 | chartbrew | Metabase |
|---|---|---|
| GitHub stars | 4,097 | 50,382 |
| Forks | 458 | 7,016 |
| Open issues | 2 | 4,696 |
| Adoption | 77 | 100 |
| Activity | 100 | 100 |
| Community | 69 | 100 |
| Issue health | 96 | 52 |
| License | 30 | 52 |
| Self-hosting | 35 | 100 |
| Composite | 73.8 | 89.4 |
Open-source reporting platform to build and share live dashboards from APIs, SQL and NoSQL databases, with powerful AI assistant, scheduling, and embeddable charts 📈📊
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 4,097 for chartbrew. The gap is 46,285 stars.
Metabase was pushed more recently: 17 November 2026 versus 14 November 2026 for chartbrew. That is 3 days apart.
Only Metabase is marked self-hostable. chartbrew is not.
chartbrew is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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 chartbrew scores 73.8. This page calls that a decisive lead for Metabase.