A · leads
Metabase
89.4
50,382 stars · AGPL-3.0
Analytics
Metabase leads by 5.3 · narrow
A · leads
89.4
50,382 stars · AGPL-3.0
B
84.1
7,051 stars · Apache-2.0
Metabase versus snowplow 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; snowplow is written mainly in Scala. The composite score is 89.4 for Metabase and 84.1 for snowplow.
Metabase has 50,382 GitHub stars to snowplow's 7,051, a gap of 43,331 (7.15×). Forks are 7,016 for Metabase and 1,171 for snowplow. On the log scale used inside this pair, adoption is 100 versus 82, and the fork community is 100 versus 80.
Push history: Metabase was last pushed on 17 November 2026 (0 days ago), and snowplow was last pushed on 19 October 2026 (28 days ago). Open issues stand at 4,696 for Metabase (0.093 per star) and 59 for snowplow (0.008 per star). Issue-health scores are 52 and 84; activity scores are 100 and 78.
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. snowplow is listed as Apache-2.0, 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 snowplow. This is a procurement signal, not legal advice.
In Analytics, both Metabase (50,382 stars) and snowplow (7,051 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, snowplow is open source.
The lead is split. Metabase is furthest ahead on recent activity (100 to 78), while snowplow is furthest ahead on license flexibility (96 to 52). Choose the dimension a rollout cannot compromise on.
Metabase finishes ahead at 89.4 against snowplow at 84.1, a 5.3 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 | Metabase | snowplow |
|---|---|---|
| GitHub stars | 50,382 | 7,051 |
| Forks | 7,016 | 1,171 |
| Open issues | 4,696 | 59 |
| Adoption | 100 | 82 |
| Activity | 100 | 78 |
| Community | 100 | 80 |
| Issue health | 52 | 84 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 89.4 | 84.1 |
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 leader in Customer Data Infrastructure
Metabase has more GitHub stars: 50,382 versus 7,051 for snowplow. The gap is 43,331 stars.
Metabase was pushed more recently: 17 November 2026 versus 19 October 2026 for snowplow. That is 28 days apart.
Yes. This catalog marks both Metabase and snowplow 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. snowplow is listed as Apache-2.0, 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 snowplow scores 84.1. This page calls that a narrow lead for Metabase.