A
redis
83.4
77,588 stars · license n/a
Databases
rqlite leads by 6.6 · narrow
A
83.4
77,588 stars · license n/a
B · leads
90.0
17,956 stars · MIT
redis versus rqlite 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; rqlite is written mainly in Go. The composite score is 83.4 for redis and 90.0 for rqlite.
redis has 77,588 GitHub stars to rqlite's 17,956, a gap of 59,632 (4.32×). Forks are 25,072 for redis and 827 for rqlite. On the log scale used inside this pair, adoption is 100 versus 87, and the fork community is 100 versus 66.
Push history: redis was last pushed on 17 November 2026 (0 days ago), and rqlite was last pushed on 17 November 2026 (0 days ago). Open issues stand at 3,122 for redis (0.040 per star) and 69 for rqlite (0.004 per star). Issue-health scores are 70 and 96; 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. rqlite 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 rqlite. This is a procurement signal, not legal advice.
Only rqlite is marked self-hostable here (17,956 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, rqlite is open source.
The lead is split. redis is furthest ahead on fork community (100 to 66), while rqlite is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.
rqlite finishes ahead at 90.0 against redis at 83.4, a 6.6 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 | rqlite |
|---|---|---|
| GitHub stars | 77,588 | 17,956 |
| Forks | 25,072 | 827 |
| Open issues | 3,122 | 69 |
| Adoption | 100 | 87 |
| Activity | 100 | 100 |
| Community | 100 | 66 |
| Issue health | 70 | 96 |
| License | 30 | 96 |
| Self-hosting | 35 | 100 |
| Composite | 83.4 | 90.0 |
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.
The lightweight, fault-tolerant database built on SQLite. Designed to keep your data highly available with minimal effort.
redis has more GitHub stars: 77,588 versus 17,956 for rqlite. The gap is 59,632 stars.
Both were last pushed on 17 November 2026.
Only rqlite 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. rqlite 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.
rqlite scores 90.0 and redis scores 83.4. This page calls that a narrow lead for rqlite.