A
dragonfly
80.1
31,878 stars · license n/a
Databases
etcd leads by 17.8 · decisive
A
80.1
31,878 stars · license n/a
B · leads
97.9
52,615 stars · Apache-2.0
dragonfly versus etcd is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. dragonfly is written mainly in C++; etcd is written mainly in Go. The composite score is 80.1 for dragonfly and 97.9 for etcd.
etcd has 52,615 GitHub stars to dragonfly's 31,878, a gap of 20,737 (1.65×). Forks are 1,294 for dragonfly and 10,608 for etcd. On the log scale used inside this pair, adoption is 95 versus 100, and the fork community is 77 versus 100.
Push history: dragonfly was last pushed on 17 November 2026 (0 days ago), and etcd was last pushed on 17 November 2026 (0 days ago). Open issues stand at 209 for dragonfly (0.007 per star) and 478 for etcd (0.009 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.
dragonfly 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. 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. License scores in this pair are 30 for dragonfly and 96 for etcd. This is a procurement signal, not legal advice.
Only etcd is marked self-hostable here (52,615 stars, deploy score 100). dragonfly is not (31,878 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: dragonfly is unpriced in this catalog, etcd is open source.
etcd is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health. The widest gap is license flexibility at 66 points (30 vs 96), and the tightest is issue health at 0 points (84 vs 84).
etcd finishes ahead at 97.9 against dragonfly at 80.1, a 17.8 point decisive 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 | dragonfly | etcd |
|---|---|---|
| GitHub stars | 31,878 | 52,615 |
| Forks | 1,294 | 10,608 |
| Open issues | 209 | 478 |
| Adoption | 95 | 100 |
| Activity | 100 | 100 |
| Community | 77 | 100 |
| Issue health | 84 | 84 |
| License | 30 | 96 |
| Self-hosting | 35 | 100 |
| Composite | 80.1 | 97.9 |
A modern replacement for Redis and Memcached
Distributed reliable key-value store for the most critical data of a distributed system
etcd has more GitHub stars: 52,615 versus 31,878 for dragonfly. The gap is 20,737 stars.
Both were last pushed on 17 November 2026.
Only etcd is marked self-hostable. dragonfly is not.
dragonfly 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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
etcd scores 97.9 and dragonfly scores 80.1. This page calls that a decisive lead for etcd.