A · leads
influxdb
93.7
31,816 stars · Apache-2.0
Databases
influxdb leads by 2.8 · narrow
A · leads
93.7
31,816 stars · Apache-2.0
B
90.9
32,285 stars · GPL-2.0
influxdb versus rocksdb is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. influxdb is written mainly in Rust; rocksdb is written mainly in C++. The composite score is 93.7 for influxdb and 90.9 for rocksdb.
rocksdb has 32,285 GitHub stars to influxdb's 31,816, a gap of 469 (1.01×). Forks are 3,826 for influxdb and 7,033 for rocksdb. On the log scale used inside this pair, adoption is 100 versus 100, and the fork community is 93 versus 100.
Push history: influxdb was last pushed on 17 November 2026 (0 days ago), and rocksdb was last pushed on 17 November 2026 (0 days ago). Open issues stand at 2,175 for influxdb (0.068 per star) and 1,855 for rocksdb (0.057 per star). Issue-health scores are 52 and 52; activity scores are 100 and 100.
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. rocksdb is listed as GPL-2.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. License scores in this pair are 96 for influxdb and 64 for rocksdb. This is a procurement signal, not legal advice.
In Databases, both influxdb (31,816 stars) and rocksdb (32,285 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: influxdb is open source, rocksdb is open source.
The lead is split. influxdb is furthest ahead on license flexibility (96 to 64), while rocksdb is furthest ahead on fork community (100 to 93). Choose the dimension a rollout cannot compromise on.
influxdb finishes ahead at 93.7 against rocksdb at 90.9, a 2.8 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 | influxdb | rocksdb |
|---|---|---|
| GitHub stars | 31,816 | 32,285 |
| Forks | 3,826 | 7,033 |
| Open issues | 2,175 | 1,855 |
| Adoption | 100 | 100 |
| Activity | 100 | 100 |
| Community | 93 | 100 |
| Issue health | 52 | 52 |
| License | 96 | 64 |
| Self-hosting | 100 | 100 |
| Composite | 93.7 | 90.9 |
Scalable datastore for metrics, events, and real-time analytics
A library that provides an embeddable, persistent key-value store for fast storage.
rocksdb has more GitHub stars: 32,285 versus 31,816 for influxdb. The gap is 469 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both influxdb and rocksdb as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. rocksdb is listed as GPL-2.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
influxdb scores 93.7 and rocksdb scores 90.9. This page calls that a narrow lead for influxdb.