A · level
rocksdb
90.9
32,285 stars · GPL-2.0
Databases
Too close to call · 90.9 to 91.5
A · level
90.9
32,285 stars · GPL-2.0
B · level
91.5
25,279 stars · MIT
rocksdb versus turso is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. rocksdb is written mainly in C++; turso is written mainly in Rust. The composite score is 90.9 for rocksdb and 91.5 for turso.
rocksdb has 32,285 GitHub stars to turso's 25,279, a gap of 7,006 (1.28×). Forks are 7,033 for rocksdb 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 83.
Push history: rocksdb 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 1,855 for rocksdb (0.057 per star) and 1,714 for turso (0.068 per star). Issue-health scores are 52 and 52; activity scores are 100 and 100.
rocksdb is listed as GPL-2.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. 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 64 for rocksdb and 96 for turso. This is a procurement signal, not legal advice.
In Databases, both rocksdb (32,285 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: rocksdb is open source, turso is open source.
The lead is split. rocksdb is furthest ahead on fork community (100 to 83), while turso is furthest ahead on license flexibility (96 to 64). Choose the dimension a rollout cannot compromise on.
Composite score: rocksdb 90.9, turso 91.5. 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 | rocksdb | turso |
|---|---|---|
| GitHub stars | 32,285 | 25,279 |
| Forks | 7,033 | 1,553 |
| Open issues | 1,855 | 1,714 |
| Adoption | 100 | 98 |
| Activity | 100 | 100 |
| Community | 100 | 83 |
| Issue health | 52 | 52 |
| License | 64 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 90.9 | 91.5 |
A library that provides an embeddable, persistent key-value store for fast storage.
A SQL database in Rust: SQLite-compatible, now also speaking Postgres (experimental). The LLVM of databases.
rocksdb has more GitHub stars: 32,285 versus 25,279 for turso. The gap is 7,006 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both rocksdb and turso as self-hostable. Confirm each project's deploy docs before you plan a migration.
rocksdb is listed as GPL-2.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. 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. rocksdb scores 90.9 and turso scores 91.5.