A · level
tidb
92.9
40,739 stars · Apache-2.0
Databases
Too close to call · 92.9 to 93.0
A · level
92.9
40,739 stars · Apache-2.0
B · level
93.0
27,730 stars · BSD-3-Clause
tidb versus Valkey is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. tidb is written mainly in Go; Valkey is written mainly in C. The composite score is 92.9 for tidb and 93.0 for Valkey.
tidb has 40,739 GitHub stars to Valkey's 27,730, a gap of 13,009 (1.47×). Forks are 6,297 for tidb and 1,540 for Valkey. On the log scale used inside this pair, adoption is 100 versus 96, and the fork community is 100 versus 84.
Push history: tidb 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 7,730 for tidb (0.190 per star) and 1,045 for Valkey (0.038 per star). Issue-health scores are 34 and 70; activity scores are 100 and 100.
tidb 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 tidb and 96 for Valkey. This is a procurement signal, not legal advice.
In Databases, both tidb (40,739 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: tidb is open source, Valkey is open source.
The lead is split. tidb is furthest ahead on fork community (100 to 84), while Valkey is furthest ahead on issue health (70 to 34). Choose the dimension a rollout cannot compromise on.
Composite score: tidb 92.9, Valkey 93.0. The margin is under one point, so this page calls a tie. Use the dimension breakdown rather than the headline number.
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 | tidb | Valkey |
|---|---|---|
| GitHub stars | 40,739 | 27,730 |
| Forks | 6,297 | 1,540 |
| Open issues | 7,730 | 1,045 |
| Adoption | 100 | 96 |
| Activity | 100 | 100 |
| Community | 100 | 84 |
| Issue health | 34 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 92.9 | 93.0 |
TiDB is built for agentic workloads that grow unpredictably, with ACID guarantees and native support for transactions, analytics, and vector search. No data silos. No noisy neighbors. No infrastructure ceiling.
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.
tidb has more GitHub stars: 40,739 versus 27,730 for Valkey. The gap is 13,009 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both tidb and Valkey as self-hostable. Confirm each project's deploy docs before you plan a migration.
tidb 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.
Neither tool clears a one-point margin. tidb scores 92.9 and Valkey scores 93.0.