A · leads
etcd
97.9
52,615 stars · Apache-2.0
Databases
etcd leads by 6.3 · narrow
A · leads
97.9
52,615 stars · Apache-2.0
B
91.6
27,730 stars · BSD-3-Clause
etcd versus Valkey is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. etcd is written mainly in Go; Valkey is written mainly in C. The composite score is 97.9 for etcd and 91.6 for Valkey.
etcd has 52,615 GitHub stars to Valkey's 27,730, a gap of 24,885 (1.90×). Forks are 10,608 for etcd and 1,540 for Valkey. On the log scale used inside this pair, adoption is 100 versus 94, and the fork community is 100 versus 79.
Push history: etcd 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 478 for etcd (0.009 per star) and 1,045 for Valkey (0.038 per star). Issue-health scores are 84 and 70; activity scores are 100 and 100.
etcd 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 etcd and 96 for Valkey. This is a procurement signal, not legal advice.
In Databases, both etcd (52,615 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: etcd is open source, Valkey is open source.
etcd is ahead on every scored dimension that is not level. Level dimensions: recent activity, license flexibility, self-hosting. The widest gap is fork community at 21 points (100 vs 79), and the tightest is self-hosting at 0 points (100 vs 100).
etcd finishes ahead at 97.9 against Valkey at 91.6, a 6.3 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 | etcd | Valkey |
|---|---|---|
| GitHub stars | 52,615 | 27,730 |
| Forks | 10,608 | 1,540 |
| Open issues | 478 | 1,045 |
| Adoption | 100 | 94 |
| Activity | 100 | 100 |
| Community | 100 | 79 |
| Issue health | 84 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 91.6 |
Distributed reliable key-value store for the most critical data of a distributed system
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.
etcd has more GitHub stars: 52,615 versus 27,730 for Valkey. The gap is 24,885 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both etcd and Valkey as self-hostable. Confirm each project's deploy docs before you plan a migration.
etcd 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.
etcd scores 97.9 and Valkey scores 91.6. This page calls that a narrow lead for etcd.