A
redis
83.4
77,588 stars · license n/a
Databases
turso leads by 4.1 · narrow
A
83.4
77,588 stars · license n/a
B · leads
87.5
25,279 stars · MIT
redis versus turso is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. redis is written mainly in C; turso is written mainly in Rust. The composite score is 83.4 for redis and 87.5 for turso.
redis has 77,588 GitHub stars to turso's 25,279, a gap of 52,309 (3.07×). Forks are 25,072 for redis and 1,553 for turso. On the log scale used inside this pair, adoption is 100 versus 90, and the fork community is 100 versus 72.
Push history: redis 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 3,122 for redis (0.040 per star) and 1,714 for turso (0.068 per star). Issue-health scores are 70 and 52; activity scores are 100 and 100.
redis 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 redis 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). redis is not (77,588 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: redis is unpriced in this catalog, turso is open source.
The lead is split. redis is furthest ahead on fork community (100 to 72), while turso is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.
turso finishes ahead at 87.5 against redis at 83.4, a 4.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 | redis | turso |
|---|---|---|
| GitHub stars | 77,588 | 25,279 |
| Forks | 25,072 | 1,553 |
| Open issues | 3,122 | 1,714 |
| Adoption | 100 | 90 |
| Activity | 100 | 100 |
| Community | 100 | 72 |
| Issue health | 70 | 52 |
| License | 30 | 96 |
| Self-hosting | 35 | 100 |
| Composite | 83.4 | 87.5 |
For developers, who are building real-time data-driven applications, Redis is the preferred, fastest, and most feature-rich cache, data structure server, and document and vector query engine.
A SQL database in Rust: SQLite-compatible, now also speaking Postgres (experimental). The LLVM of databases.
redis has more GitHub stars: 77,588 versus 25,279 for turso. The gap is 52,309 stars.
Both were last pushed on 17 November 2026.
Only turso is marked self-hostable. redis is not.
redis 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 87.5 and redis scores 83.4. This page calls that a narrow lead for turso.