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
31,816 stars · Apache-2.0
etcd versus influxdb 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; influxdb is written mainly in Rust. The composite score is 97.9 for etcd and 91.6 for influxdb.
etcd has 52,615 GitHub stars to influxdb's 31,816, a gap of 20,799 (1.65×). Forks are 10,608 for etcd and 3,826 for influxdb. On the log scale used inside this pair, adoption is 100 versus 95, and the fork community is 100 versus 89.
Push history: etcd was last pushed on 17 November 2026 (0 days ago), and influxdb was last pushed on 17 November 2026 (0 days ago). Open issues stand at 478 for etcd (0.009 per star) and 2,175 for influxdb (0.068 per star). Issue-health scores are 84 and 52; activity scores are 100 and 100.
Both etcd and influxdb are listed as Apache-2.0. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In Databases, both etcd (52,615 stars) and influxdb (31,816 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, influxdb 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 issue health at 32 points (84 vs 52), and the tightest is self-hosting at 0 points (100 vs 100).
etcd finishes ahead at 97.9 against influxdb 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 | influxdb |
|---|---|---|
| GitHub stars | 52,615 | 31,816 |
| Forks | 10,608 | 3,826 |
| Open issues | 478 | 2,175 |
| Adoption | 100 | 95 |
| Activity | 100 | 100 |
| Community | 100 | 89 |
| Issue health | 84 | 52 |
| 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
Scalable datastore for metrics, events, and real-time analytics
etcd has more GitHub stars: 52,615 versus 31,816 for influxdb. The gap is 20,799 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both etcd and influxdb 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. influxdb 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 influxdb scores 91.6. This page calls that a narrow lead for etcd.