A · leads
ClickHouse
90.3
50,970 stars · Apache-2.0
Databases
ClickHouse leads by 6.9 · narrow
A · leads
90.3
50,970 stars · Apache-2.0
B
83.4
77,588 stars · license n/a
ClickHouse versus redis 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++; redis is written mainly in C. The composite score is 90.3 for ClickHouse and 83.4 for redis.
redis has 77,588 GitHub stars to ClickHouse's 50,970, a gap of 26,618 (1.52×). Forks are 9,275 for ClickHouse and 25,072 for redis. On the log scale used inside this pair, adoption is 96 versus 100, and the fork community is 90 versus 100.
Push history: ClickHouse was last pushed on 17 November 2026 (0 days ago), and redis was last pushed on 17 November 2026 (0 days ago). Open issues stand at 9,191 for ClickHouse (0.180 per star) and 3,122 for redis (0.040 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. redis 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 redis. This is a procurement signal, not legal advice.
Only ClickHouse is marked self-hostable here (50,970 stars, deploy score 100). redis is not (77,588 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, redis is unpriced in this catalog.
The lead is split. ClickHouse is furthest ahead on license flexibility (96 to 30), while redis is furthest ahead on issue health (70 to 34). Choose the dimension a rollout cannot compromise on.
ClickHouse finishes ahead at 90.3 against redis at 83.4, a 6.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 | redis |
|---|---|---|
| GitHub stars | 50,970 | 77,588 |
| Forks | 9,275 | 25,072 |
| Open issues | 9,191 | 3,122 |
| Adoption | 96 | 100 |
| Activity | 100 | 100 |
| Community | 90 | 100 |
| Issue health | 34 | 70 |
| License | 96 | 30 |
| Self-hosting | 100 | 35 |
| Composite | 90.3 | 83.4 |
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.
For developers, who are building real-time data-driven applications, Redis is the preferred, fastest, and most feature-rich cache, data structure server, and document and vector query engine.
redis has more GitHub stars: 77,588 versus 50,970 for ClickHouse. The gap is 26,618 stars.
Both were last pushed on 17 November 2026.
Only ClickHouse is marked self-hostable. redis 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. redis 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 90.3 and redis scores 83.4. This page calls that a narrow lead for ClickHouse.