A
ClickHouse
92.9
50,970 stars · Apache-2.0
Databases
DuckDB leads by 1.9 · narrow
A
92.9
50,970 stars · Apache-2.0
B · leads
94.8
43,126 stars · MIT
ClickHouse 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 92.9 for ClickHouse and 94.8 for DuckDB.
ClickHouse has 50,970 GitHub stars to DuckDB's 43,126, a gap of 7,844 (1.18×). Forks are 9,275 for ClickHouse and 4,214 for DuckDB. On the log scale used inside this pair, adoption is 100 versus 98, and the fork community is 100 versus 91.
Push history: ClickHouse 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 9,191 for ClickHouse (0.180 per star) and 1,261 for DuckDB (0.029 per star). Issue-health scores are 34 and 70; activity scores are 100 and 100.
ClickHouse is listed as Apache-2.0, 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. 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 96 for ClickHouse and 96 for DuckDB. This is a procurement signal, not legal advice.
In Databases, both ClickHouse (50,970 stars) and DuckDB (43,126 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: ClickHouse is open source, DuckDB is open source.
The lead is split. ClickHouse is furthest ahead on fork community (100 to 91), while DuckDB is furthest ahead on issue health (70 to 34). Choose the dimension a rollout cannot compromise on.
DuckDB finishes ahead at 94.8 against ClickHouse at 92.9, a 1.9 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 | ClickHouse | DuckDB |
|---|---|---|
| GitHub stars | 50,970 | 43,126 |
| Forks | 9,275 | 4,214 |
| Open issues | 9,191 | 1,261 |
| Adoption | 100 | 98 |
| Activity | 100 | 100 |
| Community | 100 | 91 |
| Issue health | 34 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 92.9 | 94.8 |
ClickHouse is a columnar OLAP database built for fast analytical queries on large event tables. It is common as the store behind product analytics and observability.
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.
ClickHouse has more GitHub stars: 50,970 versus 43,126 for DuckDB. The gap is 7,844 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both ClickHouse and DuckDB as self-hostable. Confirm each project's deploy docs before you plan a migration.
ClickHouse is listed as Apache-2.0, 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. 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 94.8 and ClickHouse scores 92.9. This page calls that a narrow lead for DuckDB.