A
cockroach
78.0
32,622 stars · license n/a
Databases
turso leads by 14.2 · clear
A
78.0
32,622 stars · license n/a
B · leads
92.2
25,279 stars · MIT
cockroach versus turso is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. cockroach is written mainly in Go; turso is written mainly in Rust. The composite score is 78.0 for cockroach and 92.2 for turso.
cockroach has 32,622 GitHub stars to turso's 25,279, a gap of 7,343 (1.29×). Forks are 4,236 for cockroach and 1,553 for turso. On the log scale used inside this pair, adoption is 100 versus 98, and the fork community is 100 versus 88.
Push history: cockroach was last pushed on 11 November 2026 (6 days ago), and turso was last pushed on 17 November 2026 (0 days ago). Open issues stand at 8,042 for cockroach (0.247 per star) and 1,714 for turso (0.068 per star). Issue-health scores are 34 and 52; activity scores are 92 and 100.
cockroach 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. 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 30 for cockroach and 96 for turso. This is a procurement signal, not legal advice.
Only turso is marked self-hostable here (25,279 stars, deploy score 100). cockroach is not (32,622 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: cockroach is unpriced in this catalog, turso is open source.
The lead is split. cockroach is furthest ahead on fork community (100 to 88), while turso is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.
turso finishes ahead at 92.2 against cockroach at 78.0, a 14.2 point clear 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 | cockroach | turso |
|---|---|---|
| GitHub stars | 32,622 | 25,279 |
| Forks | 4,236 | 1,553 |
| Open issues | 8,042 | 1,714 |
| Adoption | 100 | 98 |
| Activity | 92 | 100 |
| Community | 100 | 88 |
| Issue health | 34 | 52 |
| License | 30 | 96 |
| Self-hosting | 35 | 100 |
| Composite | 78.0 | 92.2 |
CockroachDB — the cloud native, distributed SQL database designed for high availability, effortless scale, and control over data placement.
A SQL database in Rust: SQLite-compatible, now also speaking Postgres (experimental). The LLVM of databases.
cockroach has more GitHub stars: 32,622 versus 25,279 for turso. The gap is 7,343 stars.
turso was pushed more recently: 17 November 2026 versus 11 November 2026 for cockroach. That is 6 days apart.
Only turso is marked self-hostable. cockroach is not.
cockroach 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. 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.
turso scores 92.2 and cockroach scores 78.0. This page calls that a clear lead for turso.