A · leads
Metabase
89.4
50,382 stars · AGPL-3.0
Analytics
Metabase leads by 25.4 · decisive
A · leads
89.4
50,382 stars · AGPL-3.0
B
64.0
6,312 stars · Apache-2.0
Metabase versus pachyderm 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; pachyderm is written mainly in Go. The composite score is 89.4 for Metabase and 64.0 for pachyderm.
Metabase has 50,382 GitHub stars to pachyderm's 6,312, a gap of 44,070 (7.98×). Forks are 7,016 for Metabase and 575 for pachyderm. On the log scale used inside this pair, adoption is 100 versus 81, and the fork community is 100 versus 72.
Push history: Metabase was last pushed on 17 November 2026 (0 days ago), and pachyderm was last pushed on 03 February 2025 (651 days ago). Open issues stand at 4,696 for Metabase (0.093 per star) and 939 for pachyderm (0.149 per star). Issue-health scores are 52 and 34; 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. pachyderm 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 pachyderm. This is a procurement signal, not legal advice.
In Analytics, both Metabase (50,382 stars) and pachyderm (6,312 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, pachyderm is open source.
The lead is split. Metabase is furthest ahead on recent activity (100 to 16), while pachyderm is furthest ahead on license flexibility (96 to 52). Choose the dimension a rollout cannot compromise on.
Metabase finishes ahead at 89.4 against pachyderm at 64.0, a 25.4 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 | pachyderm |
|---|---|---|
| GitHub stars | 50,382 | 6,312 |
| Forks | 7,016 | 575 |
| Open issues | 4,696 | 939 |
| Adoption | 100 | 81 |
| Activity | 100 | 16 |
| Community | 100 | 72 |
| Issue health | 52 | 34 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 89.4 | 64.0 |
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.
Data-Centric Pipelines and Data Versioning
Metabase has more GitHub stars: 50,382 versus 6,312 for pachyderm. The gap is 44,070 stars.
Metabase was pushed more recently: 17 November 2026 versus 03 February 2025 for pachyderm. That is 651 days apart.
Yes. This catalog marks both Metabase and pachyderm 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. pachyderm 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 pachyderm scores 64.0. This page calls that a decisive lead for Metabase.