A · leads
ClickHouse
92.9
50,970 stars · Apache-2.0
Databases
ClickHouse leads by 3.4 · narrow
A · leads
92.9
50,970 stars · Apache-2.0
B
89.5
25,194 stars · AGPL-3.0
ClickHouse versus TDengine 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++; TDengine is written mainly in C. The composite score is 92.9 for ClickHouse and 89.5 for TDengine.
ClickHouse has 50,970 GitHub stars to TDengine's 25,194, a gap of 25,776 (2.02×). Forks are 9,275 for ClickHouse and 5,011 for TDengine. On the log scale used inside this pair, adoption is 100 versus 94, and the fork community is 100 versus 93.
Push history: ClickHouse was last pushed on 17 November 2026 (0 days ago), and TDengine was last pushed on 15 November 2026 (2 days ago). Open issues stand at 9,191 for ClickHouse (0.180 per star) and 454 for TDengine (0.018 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. TDengine is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. License scores in this pair are 96 for ClickHouse and 52 for TDengine. This is a procurement signal, not legal advice.
In Databases, both ClickHouse (50,970 stars) and TDengine (25,194 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, TDengine is open source.
The lead is split. ClickHouse is furthest ahead on license flexibility (96 to 52), while TDengine is furthest ahead on issue health (84 to 34). Choose the dimension a rollout cannot compromise on.
ClickHouse finishes ahead at 92.9 against TDengine at 89.5, a 3.4 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 | TDengine |
|---|---|---|
| GitHub stars | 50,970 | 25,194 |
| Forks | 9,275 | 5,011 |
| Open issues | 9,191 | 454 |
| Adoption | 100 | 94 |
| Activity | 100 | 100 |
| Community | 100 | 93 |
| Issue health | 34 | 84 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 92.9 | 89.5 |
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.
High-performance, scalable time-series database designed for Industrial IoT (IIoT) scenarios
ClickHouse has more GitHub stars: 50,970 versus 25,194 for TDengine. The gap is 25,776 stars.
ClickHouse was pushed more recently: 17 November 2026 versus 15 November 2026 for TDengine. That is 2 days apart.
Yes. This catalog marks both ClickHouse and TDengine 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. TDengine is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
ClickHouse scores 92.9 and TDengine scores 89.5. This page calls that a narrow lead for ClickHouse.