A
turso
94.4
25,279 stars · MIT
Databases
Valkey leads by 2.1 · narrow
A
94.4
25,279 stars · MIT
B · leads
96.5
27,730 stars · BSD-3-Clause
turso versus Valkey is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. turso is written mainly in Rust; Valkey is written mainly in C. The composite score is 94.4 for turso and 96.5 for Valkey.
Valkey has 27,730 GitHub stars to turso's 25,279, a gap of 2,451 (1.10×). Forks are 1,553 for turso and 1,540 for Valkey. On the log scale used inside this pair, adoption is 99 versus 100, and the fork community is 100 versus 100.
Push history: turso was last pushed on 17 November 2026 (0 days ago), and Valkey was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1,714 for turso (0.068 per star) and 1,045 for Valkey (0.038 per star). Issue-health scores are 52 and 70; activity scores are 100 and 100.
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. Valkey is listed as BSD-3-Clause, 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 turso and 96 for Valkey. This is a procurement signal, not legal advice.
In Databases, both turso (25,279 stars) and Valkey (27,730 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: turso is open source, Valkey is open source.
The lead is split. turso is furthest ahead on fork community (100 to 100), while Valkey is furthest ahead on issue health (70 to 52). Choose the dimension a rollout cannot compromise on.
Valkey finishes ahead at 96.5 against turso at 94.4, a 2.1 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 | turso | Valkey |
|---|---|---|
| GitHub stars | 25,279 | 27,730 |
| Forks | 1,553 | 1,540 |
| Open issues | 1,714 | 1,045 |
| Adoption | 99 | 100 |
| Activity | 100 | 100 |
| Community | 100 | 100 |
| Issue health | 52 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 94.4 | 96.5 |
A SQL database in Rust: SQLite-compatible, now also speaking Postgres (experimental). The LLVM of databases.
Valkey is a Linux Foundation key-value store forked from Redis. It is used as a cache, queue, and ephemeral data store under a permissive license.
Valkey has more GitHub stars: 27,730 versus 25,279 for turso. The gap is 2,451 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both turso and Valkey as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. Valkey is listed as BSD-3-Clause, 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.
Valkey scores 96.5 and turso scores 94.4. This page calls that a narrow lead for Valkey.