A · leads
Metabase
89.4
50,382 stars · AGPL-3.0
Analytics
Metabase leads by 8.7 · clear
A · leads
89.4
50,382 stars · AGPL-3.0
B
80.7
2,015 stars · MIT
Metabase versus pg_mooncake 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; pg_mooncake is written mainly in Rust. The composite score is 89.4 for Metabase and 80.7 for pg_mooncake.
Metabase has 50,382 GitHub stars to pg_mooncake's 2,015, a gap of 48,367 (25.00×). Forks are 7,016 for Metabase and 77 for pg_mooncake. On the log scale used inside this pair, adoption is 100 versus 70, and the fork community is 100 versus 49.
Push history: Metabase was last pushed on 17 November 2026 (0 days ago), and pg_mooncake was last pushed on 17 November 2026 (0 days ago). Open issues stand at 4,696 for Metabase (0.093 per star) and 17 for pg_mooncake (0.008 per star). Issue-health scores are 52 and 84; activity scores are 100 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. pg_mooncake 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 pg_mooncake. This is a procurement signal, not legal advice.
In Analytics, both Metabase (50,382 stars) and pg_mooncake (2,015 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, pg_mooncake is open source.
The lead is split. Metabase is furthest ahead on fork community (100 to 49), while pg_mooncake is furthest ahead on license flexibility (96 to 52). Choose the dimension a rollout cannot compromise on.
Metabase finishes ahead at 89.4 against pg_mooncake at 80.7, a 8.7 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 | pg_mooncake |
|---|---|---|
| GitHub stars | 50,382 | 2,015 |
| Forks | 7,016 | 77 |
| Open issues | 4,696 | 17 |
| Adoption | 100 | 70 |
| Activity | 100 | 100 |
| Community | 100 | 49 |
| Issue health | 52 | 84 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 89.4 | 80.7 |
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.
Real-time analytics on Postgres tables
Metabase has more GitHub stars: 50,382 versus 2,015 for pg_mooncake. The gap is 48,367 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Metabase and pg_mooncake 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. pg_mooncake 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 89.4 and pg_mooncake scores 80.7. This page calls that a clear lead for Metabase.