A
QuestDB
93.2
17,538 stars · Apache-2.0
Databases
Valkey leads by 3.1 · narrow
A
93.2
17,538 stars · Apache-2.0
B · leads
96.3
27,730 stars · BSD-3-Clause
QuestDB versus Valkey 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; Valkey is written mainly in C. The composite score is 93.2 for QuestDB and 96.3 for Valkey.
Valkey has 27,730 GitHub stars to QuestDB's 17,538, a gap of 10,192 (1.58×). Forks are 1,701 for QuestDB and 1,540 for Valkey. On the log scale used inside this pair, adoption is 96 versus 100, and the fork community is 100 versus 99.
Push history: QuestDB 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,515 for QuestDB (0.086 per star) and 1,045 for Valkey (0.038 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. 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 QuestDB and 96 for Valkey. This is a procurement signal, not legal advice.
In Databases, both QuestDB (17,538 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: QuestDB is open source, Valkey is open source.
The lead is split. QuestDB is furthest ahead on fork community (100 to 99), while Valkey is furthest ahead on issue health (70 to 52). Choose the dimension a rollout cannot compromise on.
Valkey finishes ahead at 96.3 against QuestDB at 93.2, 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 | Valkey |
|---|---|---|
| GitHub stars | 17,538 | 27,730 |
| Forks | 1,701 | 1,540 |
| Open issues | 1,515 | 1,045 |
| Adoption | 96 | 100 |
| Activity | 100 | 100 |
| Community | 100 | 99 |
| Issue health | 52 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 93.2 | 96.3 |
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.
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 17,538 for QuestDB. The gap is 10,192 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both QuestDB and Valkey as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. 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.3 and QuestDB scores 93.2. This page calls that a narrow lead for Valkey.