A · leads
DuckDB
96.5
43,126 stars · MIT
Databases
DuckDB leads by 3.1 · narrow
A · leads
96.5
43,126 stars · MIT
B
93.4
27,730 stars · BSD-3-Clause
DuckDB versus Valkey is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. DuckDB is written mainly in C++; Valkey is written mainly in C. The composite score is 96.5 for DuckDB and 93.4 for Valkey.
DuckDB has 43,126 GitHub stars to Valkey's 27,730, a gap of 15,396 (1.56×). Forks are 4,214 for DuckDB and 1,540 for Valkey. On the log scale used inside this pair, adoption is 100 versus 96, and the fork community is 100 versus 88.
Push history: DuckDB was last pushed on 17 November 2026 (0 days ago), and Valkey was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1,261 for DuckDB (0.029 per star) and 1,045 for Valkey (0.038 per star). Issue-health scores are 70 and 70; 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. Valkey is listed as BSD-3-Clause, 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 96 for DuckDB and 96 for Valkey. This is a procurement signal, not legal advice.
In Databases, both DuckDB (43,126 stars) and Valkey (27,730 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 is open source, Valkey is open source.
DuckDB is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, license flexibility, self-hosting. The widest gap is fork community at 12 points (100 vs 88), and the tightest is self-hosting at 0 points (100 vs 100).
DuckDB finishes ahead at 96.5 against Valkey at 93.4, a 3.1 point narrow 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 | Valkey |
|---|---|---|
| GitHub stars | 43,126 | 27,730 |
| Forks | 4,214 | 1,540 |
| Open issues | 1,261 | 1,045 |
| Adoption | 100 | 96 |
| Activity | 100 | 100 |
| Community | 100 | 88 |
| Issue health | 70 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 96.5 | 93.4 |
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.
Valkey is a Linux Foundation key-value store forked from Redis. It is used as a cache, queue, and ephemeral data store under a permissive license.
DuckDB has more GitHub stars: 43,126 versus 27,730 for Valkey. The gap is 15,396 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both DuckDB and Valkey as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. Valkey is listed as BSD-3-Clause, 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 Valkey scores 93.4. This page calls that a narrow lead for DuckDB.