A · leads
Metabase
87.7
50,382 stars · AGPL-3.0
Analytics
Metabase leads by 12.6 · clear
A · leads
87.7
50,382 stars · AGPL-3.0
B
75.1
1,282 stars · MPL-2.0
Metabase versus shaper 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; shaper is written mainly in Go. The composite score is 87.7 for Metabase and 75.1 for shaper.
Metabase has 50,382 GitHub stars to shaper's 1,282, a gap of 49,100 (39.30×). Forks are 7,016 for Metabase and 53 for shaper. On the log scale used inside this pair, adoption is 100 versus 66, and the fork community is 100 versus 45.
Push history: Metabase was last pushed on 17 November 2026 (5 days ago), and shaper was last pushed on 20 November 2026 (2 days ago). Open issues stand at 4,696 for Metabase (0.093 per star) and 29 for shaper (0.023 per star). Issue-health scores are 52 and 70; activity scores are 92 and 100.
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. shaper is listed as MPL-2.0, which this catalog treats as a weak-copyleft grant. Commercial use is generally expected, and source duties tend to follow modified copies of this project rather than the entire surrounding application. License scores in this pair are 52 for Metabase and 78 for shaper. This is a procurement signal, not legal advice.
In Analytics, both Metabase (50,382 stars) and shaper (1,282 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, shaper is open source.
The lead is split. Metabase is furthest ahead on fork community (100 to 45), while shaper is furthest ahead on license flexibility (78 to 52). Choose the dimension a rollout cannot compromise on.
Metabase finishes ahead at 87.7 against shaper at 75.1, a 12.6 point clear 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 | shaper |
|---|---|---|
| GitHub stars | 50,382 | 1,282 |
| Forks | 7,016 | 53 |
| Open issues | 4,696 | 29 |
| Adoption | 100 | 66 |
| Activity | 92 | 100 |
| Community | 100 | 45 |
| Issue health | 52 | 70 |
| License | 52 | 78 |
| Self-hosting | 100 | 100 |
| Composite | 87.7 | 75.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.
Visualize and share your data. All in SQL. Powered by DuckDB.
Metabase has more GitHub stars: 50,382 versus 1,282 for shaper. The gap is 49,100 stars.
shaper was pushed more recently: 20 November 2026 versus 17 November 2026 for Metabase. That is 3 days apart.
Yes. This catalog marks both Metabase and shaper 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. shaper is listed as MPL-2.0, which this catalog treats as a weak-copyleft grant. Commercial use is generally expected, and source duties tend to follow modified copies of this project rather than the entire surrounding application. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Metabase scores 87.7 and shaper scores 75.1. This page calls that a clear lead for Metabase.