A · leads
tidb
92.9
40,739 stars · Apache-2.0
Databases
tidb leads by 1.9 · narrow
A · leads
92.9
40,739 stars · Apache-2.0
B
91.0
25,279 stars · MIT
tidb versus turso is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. tidb is written mainly in Go; turso is written mainly in Rust. The composite score is 92.9 for tidb and 91.0 for turso.
tidb has 40,739 GitHub stars to turso's 25,279, a gap of 15,460 (1.61×). Forks are 6,297 for tidb and 1,553 for turso. On the log scale used inside this pair, adoption is 100 versus 96, and the fork community is 100 versus 84.
Push history: tidb 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 7,730 for tidb (0.190 per star) and 1,714 for turso (0.068 per star). Issue-health scores are 34 and 52; activity scores are 100 and 100.
tidb 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 tidb and 96 for turso. This is a procurement signal, not legal advice.
In Databases, both tidb (40,739 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: tidb is open source, turso is open source.
The lead is split. tidb is furthest ahead on fork community (100 to 84), while turso is furthest ahead on issue health (52 to 34). Choose the dimension a rollout cannot compromise on.
tidb finishes ahead at 92.9 against turso at 91.0, a 1.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 | tidb | turso |
|---|---|---|
| GitHub stars | 40,739 | 25,279 |
| Forks | 6,297 | 1,553 |
| Open issues | 7,730 | 1,714 |
| Adoption | 100 | 96 |
| Activity | 100 | 100 |
| Community | 100 | 84 |
| Issue health | 34 | 52 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 92.9 | 91.0 |
TiDB is built for agentic workloads that grow unpredictably, with ACID guarantees and native support for transactions, analytics, and vector search. No data silos. No noisy neighbors. No infrastructure ceiling.
A SQL database in Rust: SQLite-compatible, now also speaking Postgres (experimental). The LLVM of databases.
tidb has more GitHub stars: 40,739 versus 25,279 for turso. The gap is 15,460 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both tidb and turso as self-hostable. Confirm each project's deploy docs before you plan a migration.
tidb 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.
tidb scores 92.9 and turso scores 91.0. This page calls that a narrow lead for tidb.