A
SpacetimeDB
82.8
25,561 stars · license n/a
Databases
turso leads by 11.9 · clear
A
82.8
25,561 stars · license n/a
B · leads
94.7
25,279 stars · MIT
SpacetimeDB versus turso is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in Rust. The composite score is 82.8 for SpacetimeDB and 94.7 for turso.
SpacetimeDB has 25,561 GitHub stars to turso's 25,279, a gap of 282 (1.01×). Forks are 1,121 for SpacetimeDB and 1,553 for turso. On the log scale used inside this pair, adoption is 100 versus 100, and the fork community is 96 versus 100.
Push history: SpacetimeDB 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 984 for SpacetimeDB (0.038 per star) and 1,714 for turso (0.068 per star). Issue-health scores are 70 and 52; activity scores are 100 and 100.
SpacetimeDB 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 SpacetimeDB 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). SpacetimeDB is not (25,561 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: SpacetimeDB is unpriced in this catalog, turso is open source.
The lead is split. SpacetimeDB is furthest ahead on issue health (70 to 52), while turso is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.
turso finishes ahead at 94.7 against SpacetimeDB at 82.8, a 11.9 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 | SpacetimeDB | turso |
|---|---|---|
| GitHub stars | 25,561 | 25,279 |
| Forks | 1,121 | 1,553 |
| Open issues | 984 | 1,714 |
| Adoption | 100 | 100 |
| Activity | 100 | 100 |
| Community | 96 | 100 |
| Issue health | 70 | 52 |
| License | 30 | 96 |
| Self-hosting | 35 | 100 |
| Composite | 82.8 | 94.7 |
Development at the speed of light
A SQL database in Rust: SQLite-compatible, now also speaking Postgres (experimental). The LLVM of databases.
SpacetimeDB has more GitHub stars: 25,561 versus 25,279 for turso. The gap is 282 stars.
Both were last pushed on 17 November 2026.
Only turso is marked self-hostable. SpacetimeDB is not.
SpacetimeDB 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 94.7 and SpacetimeDB scores 82.8. This page calls that a clear lead for turso.