A · leads
Metabase
89.4
50,382 stars · AGPL-3.0
Analytics
Metabase leads by 31.0 · decisive
A · leads
89.4
50,382 stars · AGPL-3.0
B
58.4
1,755 stars · AGPL-3.0
Metabase versus stampede 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; stampede is written mainly in Java. The composite score is 89.4 for Metabase and 58.4 for stampede.
Metabase has 50,382 GitHub stars to stampede's 1,755, a gap of 48,627 (28.71×). Forks are 7,016 for Metabase and 116 for stampede. On the log scale used inside this pair, adoption is 100 versus 69, and the fork community is 100 versus 54.
Push history: Metabase was last pushed on 17 November 2026 (0 days ago), and stampede was last pushed on 25 October 2018 (2945 days ago). Open issues stand at 4,696 for Metabase (0.093 per star) and 6 for stampede (0.003 per star). Issue-health scores are 52 and 96; activity scores are 100 and 16.
Both Metabase and stampede are listed as AGPL-3.0. A network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. The license score is therefore level at 52 versus 52, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In Analytics, both Metabase (50,382 stars) and stampede (1,755 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, stampede is open source.
The lead is split. Metabase is furthest ahead on recent activity (100 to 16), while stampede is furthest ahead on issue health (96 to 52). Choose the dimension a rollout cannot compromise on.
Metabase finishes ahead at 89.4 against stampede at 58.4, a 31.0 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 | stampede |
|---|---|---|
| GitHub stars | 50,382 | 1,755 |
| Forks | 7,016 | 116 |
| Open issues | 4,696 | 6 |
| Adoption | 100 | 69 |
| Activity | 100 | 16 |
| Community | 100 | 54 |
| Issue health | 52 | 96 |
| License | 52 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 89.4 | 58.4 |
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.
The ToroDB solution to provide better analytics on top of MongoDB and make it easier to migrate from MongoDB to SQL
Metabase has more GitHub stars: 50,382 versus 1,755 for stampede. The gap is 48,627 stars.
Metabase was pushed more recently: 17 November 2026 versus 25 October 2018 for stampede. That is 2945 days apart.
Yes. This catalog marks both Metabase and stampede 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. stampede 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 stampede scores 58.4. This page calls that a decisive lead for Metabase.