A · level
TDengine
92.6
25,194 stars · AGPL-3.0
Databases
Too close to call · 92.6 to 92.8
A · level
92.6
25,194 stars · AGPL-3.0
B · level
92.8
25,279 stars · MIT
TDengine versus turso is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. TDengine is written mainly in C; turso is written mainly in Rust. The composite score is 92.6 for TDengine and 92.8 for turso.
turso has 25,279 GitHub stars to TDengine's 25,194, a gap of 85 (1.00×). Forks are 5,011 for TDengine and 1,553 for turso. On the log scale used inside this pair, adoption is 100 versus 100, and the fork community is 100 versus 86.
Push history: TDengine was last pushed on 15 November 2026 (2 days ago), and turso was last pushed on 17 November 2026 (0 days ago). Open issues stand at 454 for TDengine (0.018 per star) and 1,714 for turso (0.068 per star). Issue-health scores are 84 and 52; activity scores are 100 and 100.
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. 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 52 for TDengine and 96 for turso. This is a procurement signal, not legal advice.
In Databases, both TDengine (25,194 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: TDengine is open source, turso is open source.
The lead is split. TDengine is furthest ahead on issue health (84 to 52), while turso is furthest ahead on license flexibility (96 to 52). Choose the dimension a rollout cannot compromise on.
Composite score: TDengine 92.6, turso 92.8. The margin is under one point, so this page calls a tie. Use the dimension breakdown rather than the headline number.
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 | TDengine | turso |
|---|---|---|
| GitHub stars | 25,194 | 25,279 |
| Forks | 5,011 | 1,553 |
| Open issues | 454 | 1,714 |
| Adoption | 100 | 100 |
| Activity | 100 | 100 |
| Community | 100 | 86 |
| Issue health | 84 | 52 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 92.6 | 92.8 |
High-performance, scalable time-series database designed for Industrial IoT (IIoT) scenarios
A SQL database in Rust: SQLite-compatible, now also speaking Postgres (experimental). The LLVM of databases.
turso has more GitHub stars: 25,279 versus 25,194 for TDengine. The gap is 85 stars.
turso was pushed more recently: 17 November 2026 versus 15 November 2026 for TDengine. That is 2 days apart.
Yes. This catalog marks both TDengine and turso as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. 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.
Neither tool clears a one-point margin. TDengine scores 92.6 and turso scores 92.8.