A · leads
Metabase
89.4
50,382 stars · AGPL-3.0
Analytics
Metabase leads by 7.5 · clear
A · leads
89.4
50,382 stars · AGPL-3.0
B
81.9
9,535 stars · AGPL-3.0
Metabase versus paradedb 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; paradedb is written mainly in Rust. The composite score is 89.4 for Metabase and 81.9 for paradedb.
Metabase has 50,382 GitHub stars to paradedb's 9,535, a gap of 40,847 (5.28×). Forks are 7,016 for Metabase and 515 for paradedb. On the log scale used inside this pair, adoption is 100 versus 85, and the fork community is 100 versus 70.
Push history: Metabase was last pushed on 17 November 2026 (0 days ago), and paradedb was last pushed on 17 November 2026 (0 days ago). Open issues stand at 4,696 for Metabase (0.093 per star) and 284 for paradedb (0.030 per star). Issue-health scores are 52 and 70; activity scores are 100 and 100.
Both Metabase and paradedb are listed as AGPL-3.0. A network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. The license score is therefore level at 52 versus 52, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In Analytics, both Metabase (50,382 stars) and paradedb (9,535 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, paradedb is open source.
The lead is split. Metabase is furthest ahead on fork community (100 to 70), while paradedb is furthest ahead on issue health (70 to 52). Choose the dimension a rollout cannot compromise on.
Metabase finishes ahead at 89.4 against paradedb at 81.9, a 7.5 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 | paradedb |
|---|---|---|
| GitHub stars | 50,382 | 9,535 |
| Forks | 7,016 | 515 |
| Open issues | 4,696 | 284 |
| Adoption | 100 | 85 |
| Activity | 100 | 100 |
| Community | 100 | 70 |
| Issue health | 52 | 70 |
| License | 52 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 89.4 | 81.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.
One Postgres for your application data, full-text search, vector retrieval, and aggregations. Home of the pg_search extension.
Metabase has more GitHub stars: 50,382 versus 9,535 for paradedb. The gap is 40,847 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Metabase and paradedb 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. paradedb 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Metabase scores 89.4 and paradedb scores 81.9. This page calls that a clear lead for Metabase.