A · leads
ClickHouse
92.9
50,970 stars · Apache-2.0
Databases
ClickHouse leads by 12.6 · clear
A · leads
92.9
50,970 stars · Apache-2.0
B
80.3
31,878 stars · license n/a
ClickHouse versus dragonfly 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 80.3 for dragonfly.
ClickHouse has 50,970 GitHub stars to dragonfly's 31,878, a gap of 19,092 (1.60×). Forks are 9,275 for ClickHouse and 1,294 for dragonfly. On the log scale used inside this pair, adoption is 100 versus 96, and the fork community is 100 versus 78.
Push history: ClickHouse was last pushed on 17 November 2026 (0 days ago), and dragonfly was last pushed on 17 November 2026 (0 days ago). Open issues stand at 9,191 for ClickHouse (0.180 per star) and 209 for dragonfly (0.007 per star). Issue-health scores are 34 and 84; 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. 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. License scores in this pair are 96 for ClickHouse and 30 for dragonfly. This is a procurement signal, not legal advice.
Only ClickHouse is marked self-hostable here (50,970 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: ClickHouse is open source, dragonfly is unpriced in this catalog.
The lead is split. ClickHouse is furthest ahead on license flexibility (96 to 30), while dragonfly is furthest ahead on issue health (84 to 34). Choose the dimension a rollout cannot compromise on.
ClickHouse finishes ahead at 92.9 against dragonfly at 80.3, a 12.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 | ClickHouse | dragonfly |
|---|---|---|
| GitHub stars | 50,970 | 31,878 |
| Forks | 9,275 | 1,294 |
| Open issues | 9,191 | 209 |
| Adoption | 100 | 96 |
| Activity | 100 | 100 |
| Community | 100 | 78 |
| Issue health | 34 | 84 |
| License | 96 | 30 |
| Self-hosting | 100 | 35 |
| Composite | 92.9 | 80.3 |
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.
A modern replacement for Redis and Memcached
ClickHouse has more GitHub stars: 50,970 versus 31,878 for dragonfly. The gap is 19,092 stars.
Both were last pushed on 17 November 2026.
Only ClickHouse is marked self-hostable. dragonfly is not.
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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
ClickHouse scores 92.9 and dragonfly scores 80.3. This page calls that a clear lead for ClickHouse.