A · leads
QuestDB
86.5
17,538 stars · Apache-2.0
Databases
QuestDB leads by 3.1 · narrow
A · leads
86.5
17,538 stars · Apache-2.0
B
83.4
77,588 stars · license n/a
QuestDB versus redis is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. QuestDB is written mainly in Java; redis is written mainly in C. The composite score is 86.5 for QuestDB and 83.4 for redis.
redis has 77,588 GitHub stars to QuestDB's 17,538, a gap of 60,050 (4.42×). Forks are 1,701 for QuestDB and 25,072 for redis. On the log scale used inside this pair, adoption is 87 versus 100, and the fork community is 73 versus 100.
Push history: QuestDB was last pushed on 17 November 2026 (0 days ago), and redis was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1,515 for QuestDB (0.086 per star) and 3,122 for redis (0.040 per star). Issue-health scores are 52 and 70; activity scores are 100 and 100.
QuestDB is listed as Apache-2.0, 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. 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. License scores in this pair are 96 for QuestDB and 30 for redis. This is a procurement signal, not legal advice.
Only QuestDB is marked self-hostable here (17,538 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: QuestDB is open source, redis is unpriced in this catalog.
The lead is split. QuestDB is furthest ahead on license flexibility (96 to 30), while redis is furthest ahead on fork community (100 to 73). Choose the dimension a rollout cannot compromise on.
QuestDB finishes ahead at 86.5 against redis at 83.4, a 3.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 | QuestDB | redis |
|---|---|---|
| GitHub stars | 17,538 | 77,588 |
| Forks | 1,701 | 25,072 |
| Open issues | 1,515 | 3,122 |
| Adoption | 87 | 100 |
| Activity | 100 | 100 |
| Community | 73 | 100 |
| Issue health | 52 | 70 |
| License | 96 | 30 |
| Self-hosting | 100 | 35 |
| Composite | 86.5 | 83.4 |
QuestDB is a time-series database with SQL and a focus on ingestion speed. It is used for metrics, market data, and other timestamp-heavy workloads.
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.
redis has more GitHub stars: 77,588 versus 17,538 for QuestDB. The gap is 60,050 stars.
Both were last pushed on 17 November 2026.
Only QuestDB is marked self-hostable. redis is not.
QuestDB is listed as Apache-2.0, 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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
QuestDB scores 86.5 and redis scores 83.4. This page calls that a narrow lead for QuestDB.