A
cockroach
77.2
32,622 stars · license n/a
Databases
DuckDB leads by 19.3 · decisive
A
77.2
32,622 stars · license n/a
B · leads
96.5
43,126 stars · MIT
cockroach versus DuckDB is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. cockroach is written mainly in Go; DuckDB is written mainly in C++. The composite score is 77.2 for cockroach and 96.5 for DuckDB.
DuckDB has 43,126 GitHub stars to cockroach's 32,622, a gap of 10,504 (1.32×). Forks are 4,236 for cockroach and 4,214 for DuckDB. On the log scale used inside this pair, adoption is 97 versus 100, and the fork community is 100 versus 100.
Push history: cockroach was last pushed on 11 November 2026 (6 days ago), and DuckDB was last pushed on 17 November 2026 (0 days ago). Open issues stand at 8,042 for cockroach (0.247 per star) and 1,261 for DuckDB (0.029 per star). Issue-health scores are 34 and 70; activity scores are 92 and 100.
cockroach 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 cockroach 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). cockroach is not (32,622 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: cockroach is unpriced in this catalog, DuckDB is open source.
The lead is split. cockroach is furthest ahead on fork community (100 to 100), 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 cockroach at 77.2, a 19.3 point decisive 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 | cockroach | DuckDB |
|---|---|---|
| GitHub stars | 32,622 | 43,126 |
| Forks | 4,236 | 4,214 |
| Open issues | 8,042 | 1,261 |
| Adoption | 97 | 100 |
| Activity | 92 | 100 |
| Community | 100 | 100 |
| Issue health | 34 | 70 |
| License | 30 | 96 |
| Self-hosting | 35 | 100 |
| Composite | 77.2 | 96.5 |
CockroachDB — the cloud native, distributed SQL database designed for high availability, effortless scale, and control over data placement.
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 32,622 for cockroach. The gap is 10,504 stars.
DuckDB was pushed more recently: 17 November 2026 versus 11 November 2026 for cockroach. That is 6 days apart.
Only DuckDB is marked self-hostable. cockroach is not.
cockroach 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 cockroach scores 77.2. This page calls that a decisive lead for DuckDB.