A
duckdb-wasm
79.6
2,172 stars · MIT
Analytics
Metabase leads by 9.8 · clear
A
79.6
2,172 stars · MIT
B · leads
89.4
50,382 stars · AGPL-3.0
duckdb-wasm versus Metabase is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. duckdb-wasm is written mainly in TypeScript; Metabase is written mainly in Clojure. The composite score is 79.6 for duckdb-wasm and 89.4 for Metabase.
Metabase has 50,382 GitHub stars to duckdb-wasm's 2,172, a gap of 48,210 (23.20×). Forks are 244 for duckdb-wasm and 7,016 for Metabase. On the log scale used inside this pair, adoption is 71 versus 100, and the fork community is 62 versus 100.
Push history: duckdb-wasm was last pushed on 16 November 2026 (1 day ago), and Metabase was last pushed on 17 November 2026 (0 days ago). Open issues stand at 218 for duckdb-wasm (0.100 per star) and 4,696 for Metabase (0.093 per star). Issue-health scores are 52 and 52; activity scores are 100 and 100.
duckdb-wasm 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. 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. License scores in this pair are 96 for duckdb-wasm and 52 for Metabase. This is a procurement signal, not legal advice.
In Analytics, both duckdb-wasm (2,172 stars) and Metabase (50,382 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: duckdb-wasm is open source, Metabase is freemium.
The lead is split. duckdb-wasm is furthest ahead on license flexibility (96 to 52), while Metabase is furthest ahead on fork community (100 to 62). Choose the dimension a rollout cannot compromise on.
Metabase finishes ahead at 89.4 against duckdb-wasm at 79.6, a 9.8 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 | duckdb-wasm | Metabase |
|---|---|---|
| GitHub stars | 2,172 | 50,382 |
| Forks | 244 | 7,016 |
| Open issues | 218 | 4,696 |
| Adoption | 71 | 100 |
| Activity | 100 | 100 |
| Community | 62 | 100 |
| Issue health | 52 | 52 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 79.6 | 89.4 |
WebAssembly version of DuckDB
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.
Metabase has more GitHub stars: 50,382 versus 2,172 for duckdb-wasm. The gap is 48,210 stars.
Metabase was pushed more recently: 17 November 2026 versus 16 November 2026 for duckdb-wasm. That is 1 days apart.
Yes. This catalog marks both duckdb-wasm and Metabase as self-hostable. Confirm each project's deploy docs before you plan a migration.
duckdb-wasm 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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Metabase scores 89.4 and duckdb-wasm scores 79.6. This page calls that a clear lead for Metabase.