A · leads
DuckDB
96.0
43,126 stars · MIT
Databases
DuckDB leads by 11.3 · clear
A · leads
96.0
43,126 stars · MIT
B
84.7
28,682 stars · license n/a
DuckDB versus mongo is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in C++. The composite score is 96.0 for DuckDB and 84.7 for mongo.
DuckDB has 43,126 GitHub stars to mongo's 28,682, a gap of 14,444 (1.50×). Forks are 4,214 for DuckDB and 5,916 for mongo. On the log scale used inside this pair, adoption is 100 versus 96, and the fork community is 96 versus 100.
Push history: DuckDB was last pushed on 17 November 2026 (0 days ago), and mongo was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1,261 for DuckDB (0.029 per star) and 45 for mongo (0.002 per star). Issue-health scores are 70 and 96; activity scores are 100 and 100.
DuckDB 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. mongo is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. License scores in this pair are 96 for DuckDB and 30 for mongo. This is a procurement signal, not legal advice.
Only DuckDB is marked self-hostable here (43,126 stars, deploy score 100). mongo is not (28,682 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: DuckDB is open source, mongo is unpriced in this catalog.
The lead is split. DuckDB is furthest ahead on license flexibility (96 to 30), while mongo is furthest ahead on issue health (96 to 70). Choose the dimension a rollout cannot compromise on.
DuckDB finishes ahead at 96.0 against mongo at 84.7, a 11.3 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 | mongo |
|---|---|---|
| GitHub stars | 43,126 | 28,682 |
| Forks | 4,214 | 5,916 |
| Open issues | 1,261 | 45 |
| Adoption | 100 | 96 |
| Activity | 100 | 100 |
| Community | 96 | 100 |
| Issue health | 70 | 96 |
| License | 96 | 30 |
| Self-hosting | 100 | 35 |
| Composite | 96.0 | 84.7 |
DuckDB is an in-process analytical database, often described as SQLite for OLAP. It runs inside the application process and queries local files such as Parquet.
The MongoDB Database
DuckDB has more GitHub stars: 43,126 versus 28,682 for mongo. The gap is 14,444 stars.
Both were last pushed on 17 November 2026.
Only DuckDB is marked self-hostable. mongo is not.
DuckDB 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. mongo is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
DuckDB scores 96.0 and mongo scores 84.7. This page calls that a clear lead for DuckDB.