A
dragonfly
81.9
31,878 stars · license n/a
Databases
DuckDB leads by 14.6 · clear
A
81.9
31,878 stars · license n/a
B · leads
96.5
43,126 stars · MIT
dragonfly versus DuckDB 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 81.9 for dragonfly and 96.5 for DuckDB.
DuckDB has 43,126 GitHub stars to dragonfly's 31,878, a gap of 11,248 (1.35×). Forks are 1,294 for dragonfly and 4,214 for DuckDB. On the log scale used inside this pair, adoption is 97 versus 100, and the fork community is 86 versus 100.
Push history: dragonfly was last pushed on 17 November 2026 (0 days ago), and DuckDB was last pushed on 17 November 2026 (0 days ago). Open issues stand at 209 for dragonfly (0.007 per star) and 1,261 for DuckDB (0.029 per star). Issue-health scores are 84 and 70; activity scores are 100 and 100.
dragonfly 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. 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. License scores in this pair are 30 for dragonfly and 96 for DuckDB. This is a procurement signal, not legal advice.
Only DuckDB is marked self-hostable here (43,126 stars, deploy score 100). dragonfly is not (31,878 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: dragonfly is unpriced in this catalog, DuckDB is open source.
The lead is split. dragonfly is furthest ahead on issue health (84 to 70), while DuckDB is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.
DuckDB finishes ahead at 96.5 against dragonfly at 81.9, a 14.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 | dragonfly | DuckDB |
|---|---|---|
| GitHub stars | 31,878 | 43,126 |
| Forks | 1,294 | 4,214 |
| Open issues | 209 | 1,261 |
| Adoption | 97 | 100 |
| Activity | 100 | 100 |
| Community | 86 | 100 |
| Issue health | 84 | 70 |
| License | 30 | 96 |
| Self-hosting | 35 | 100 |
| Composite | 81.9 | 96.5 |
A modern replacement for Redis and Memcached
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.
DuckDB has more GitHub stars: 43,126 versus 31,878 for dragonfly. The gap is 11,248 stars.
Both were last pushed on 17 November 2026.
Only DuckDB is marked self-hostable. dragonfly is not.
dragonfly 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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
DuckDB scores 96.5 and dragonfly scores 81.9. This page calls that a clear lead for DuckDB.