A
GrowthBook
85.9
8,603 stars · MIT
Analytics
Metabase leads by 3.5 · narrow
A
85.9
8,603 stars · MIT
B · leads
89.4
50,382 stars · AGPL-3.0
GrowthBook versus Metabase is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. GrowthBook is written mainly in TypeScript; Metabase is written mainly in Clojure. The composite score is 85.9 for GrowthBook and 89.4 for Metabase.
Metabase has 50,382 GitHub stars to GrowthBook's 8,603, a gap of 41,779 (5.86×). Forks are 906 for GrowthBook and 7,016 for Metabase. On the log scale used inside this pair, adoption is 84 versus 100, and the fork community is 77 versus 100.
Push history: GrowthBook was last pushed on 17 November 2026 (0 days ago), and Metabase was last pushed on 17 November 2026 (0 days ago). Open issues stand at 918 for GrowthBook (0.107 per star) and 4,696 for Metabase (0.093 per star). Issue-health scores are 52 and 52; activity scores are 100 and 100.
GrowthBook 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 GrowthBook and 52 for Metabase. This is a procurement signal, not legal advice.
In Analytics, both GrowthBook (8,603 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: GrowthBook is freemium, Metabase is freemium.
The lead is split. GrowthBook is furthest ahead on license flexibility (96 to 52), while Metabase is furthest ahead on fork community (100 to 77). Choose the dimension a rollout cannot compromise on.
Metabase finishes ahead at 89.4 against GrowthBook at 85.9, a 3.5 point narrow 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 | GrowthBook | Metabase |
|---|---|---|
| GitHub stars | 8,603 | 50,382 |
| Forks | 906 | 7,016 |
| Open issues | 918 | 4,696 |
| Adoption | 84 | 100 |
| Activity | 100 | 100 |
| Community | 77 | 100 |
| Issue health | 52 | 52 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 85.9 | 89.4 |
GrowthBook is a feature-flag and experimentation tool. It is aimed at product teams that want A/B tests and flags without sending every decision to a closed vendor.
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 8,603 for GrowthBook. The gap is 41,779 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both GrowthBook and Metabase as self-hostable. Confirm each project's deploy docs before you plan a migration.
GrowthBook 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 GrowthBook scores 85.9. This page calls that a narrow lead for Metabase.