A · leads
ClickHouse
92.9
50,970 stars · Apache-2.0
Databases
ClickHouse leads by 3.1 · narrow
A · leads
92.9
50,970 stars · Apache-2.0
B
89.8
25,279 stars · MIT
ClickHouse versus turso 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++; turso is written mainly in Rust. The composite score is 92.9 for ClickHouse and 89.8 for turso.
ClickHouse has 50,970 GitHub stars to turso's 25,279, a gap of 25,691 (2.02×). Forks are 9,275 for ClickHouse and 1,553 for turso. On the log scale used inside this pair, adoption is 100 versus 94, and the fork community is 100 versus 80.
Push history: ClickHouse was last pushed on 17 November 2026 (0 days ago), and turso was last pushed on 17 November 2026 (0 days ago). Open issues stand at 9,191 for ClickHouse (0.180 per star) and 1,714 for turso (0.068 per star). Issue-health scores are 34 and 52; 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. turso 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 turso. This is a procurement signal, not legal advice.
In Databases, both ClickHouse (50,970 stars) and turso (25,279 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, turso is open source.
The lead is split. ClickHouse is furthest ahead on fork community (100 to 80), while turso is furthest ahead on issue health (52 to 34). Choose the dimension a rollout cannot compromise on.
ClickHouse finishes ahead at 92.9 against turso at 89.8, a 3.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 | turso |
|---|---|---|
| GitHub stars | 50,970 | 25,279 |
| Forks | 9,275 | 1,553 |
| Open issues | 9,191 | 1,714 |
| Adoption | 100 | 94 |
| Activity | 100 | 100 |
| Community | 100 | 80 |
| Issue health | 34 | 52 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 92.9 | 89.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.
A SQL database in Rust: SQLite-compatible, now also speaking Postgres (experimental). The LLVM of databases.
ClickHouse has more GitHub stars: 50,970 versus 25,279 for turso. The gap is 25,691 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both ClickHouse and turso 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. turso 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.
ClickHouse scores 92.9 and turso scores 89.8. This page calls that a narrow lead for ClickHouse.