A · leads
ClickHouse
92.9
50,970 stars · Apache-2.0
Databases
ClickHouse leads by 4.1 · narrow
A · leads
92.9
50,970 stars · Apache-2.0
B
88.8
17,538 stars · Apache-2.0
ClickHouse versus QuestDB is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. ClickHouse is written mainly in C++; QuestDB is written mainly in Java. The composite score is 92.9 for ClickHouse and 88.8 for QuestDB.
ClickHouse has 50,970 GitHub stars to QuestDB's 17,538, a gap of 33,432 (2.91×). Forks are 9,275 for ClickHouse and 1,701 for QuestDB. On the log scale used inside this pair, adoption is 100 versus 90, and the fork community is 100 versus 81.
Push history: ClickHouse was last pushed on 17 November 2026 (0 days ago), and QuestDB was last pushed on 17 November 2026 (0 days ago). Open issues stand at 9,191 for ClickHouse (0.180 per star) and 1,515 for QuestDB (0.086 per star). Issue-health scores are 34 and 52; activity scores are 100 and 100.
Both ClickHouse and QuestDB are listed as Apache-2.0. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In Databases, both ClickHouse (50,970 stars) and QuestDB (17,538 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, QuestDB is open source.
The lead is split. ClickHouse is furthest ahead on fork community (100 to 81), while QuestDB is furthest ahead on issue health (52 to 34). Choose the dimension a rollout cannot compromise on.
ClickHouse finishes ahead at 92.9 against QuestDB at 88.8, a 4.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 | ClickHouse | QuestDB |
|---|---|---|
| GitHub stars | 50,970 | 17,538 |
| Forks | 9,275 | 1,701 |
| Open issues | 9,191 | 1,515 |
| Adoption | 100 | 90 |
| Activity | 100 | 100 |
| Community | 100 | 81 |
| Issue health | 34 | 52 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 92.9 | 88.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.
QuestDB is a time-series database with SQL and a focus on ingestion speed. It is used for metrics, market data, and other timestamp-heavy workloads.
ClickHouse has more GitHub stars: 50,970 versus 17,538 for QuestDB. The gap is 33,432 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both ClickHouse and QuestDB 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. QuestDB 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
ClickHouse scores 92.9 and QuestDB scores 88.8. This page calls that a narrow lead for ClickHouse.