A · leads
Metabase
87.7
50,382 stars · AGPL-3.0
Analytics
Metabase leads by 22.8 · decisive
A · leads
87.7
50,382 stars · AGPL-3.0
B
64.9
1,272 stars · MIT
Metabase versus pan 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; pan is written mainly in PHP. The composite score is 87.7 for Metabase and 64.9 for pan.
Metabase has 50,382 GitHub stars to pan's 1,272, a gap of 49,110 (39.61×). Forks are 7,016 for Metabase and 63 for pan. On the log scale used inside this pair, adoption is 100 versus 66, and the fork community is 100 versus 47.
Push history: Metabase was last pushed on 17 November 2026 (5 days ago), and pan was last pushed on 12 April 2026 (224 days ago). Open issues stand at 4,696 for Metabase (0.093 per star) and 15 for pan (0.012 per star). Issue-health scores are 52 and 84; activity scores are 92 and 36.
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. pan 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. License scores in this pair are 52 for Metabase and 96 for pan. This is a procurement signal, not legal advice.
In Analytics, both Metabase (50,382 stars) and pan (1,272 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, pan is open source.
The lead is split. Metabase is furthest ahead on recent activity (92 to 36), while pan is furthest ahead on license flexibility (96 to 52). Choose the dimension a rollout cannot compromise on.
Metabase finishes ahead at 87.7 against pan at 64.9, a 22.8 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 | pan |
|---|---|---|
| GitHub stars | 50,382 | 1,272 |
| Forks | 7,016 | 63 |
| Open issues | 4,696 | 15 |
| Adoption | 100 | 66 |
| Activity | 92 | 36 |
| Community | 100 | 47 |
| Issue health | 52 | 84 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 87.7 | 64.9 |
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.
A simple, lightweight, and privacy-focused product analytics php package
Metabase has more GitHub stars: 50,382 versus 1,272 for pan. The gap is 49,110 stars.
Metabase was pushed more recently: 17 November 2026 versus 12 April 2026 for pan. That is 219 days apart.
Yes. This catalog marks both Metabase and pan 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. pan 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Metabase scores 87.7 and pan scores 64.9. This page calls that a decisive lead for Metabase.