Skip to content
DevUtils Online

Databases

dragonfly vs influxdb

influxdb leads by 11.7 · clear

A

dragonfly

83.0

31,878 stars · license n/a

B · leads

influxdb

94.7

31,816 stars · Apache-2.0

dragonfly versus influxdb 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++; influxdb is written mainly in Rust. The composite score is 83.0 for dragonfly and 94.7 for influxdb.

dragonfly has 31,878 GitHub stars to influxdb's 31,816, a gap of 62 (1.00×). Forks are 1,294 for dragonfly and 3,826 for influxdb. On the log scale used inside this pair, adoption is 100 versus 100, and the fork community is 87 versus 100.

Push history: dragonfly 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 209 for dragonfly (0.007 per star) and 2,175 for influxdb (0.068 per star). Issue-health scores are 84 and 52; 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. 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. License scores in this pair are 30 for dragonfly and 96 for influxdb. This is a procurement signal, not legal advice.

Only influxdb is marked self-hostable here (31,816 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, influxdb is open source.

The lead is split. dragonfly is furthest ahead on issue health (84 to 52), while influxdb is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.

influxdb finishes ahead at 94.7 against dragonfly at 83.0, a 11.7 point clear margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

dragonfly versus influxdb metrics
Signal dragonfly influxdb
GitHub stars 31,878 31,816
Forks 1,294 3,826
Open issues 209 2,175
Adoption 100 100
Activity 100 100
Community 87 100
Issue health 84 52
License 30 96
Self-hosting 35 100
Composite 83.0 94.7

Questions this page answers

Which has more GitHub stars, dragonfly or influxdb?

dragonfly has more GitHub stars: 31,878 versus 31,816 for influxdb. The gap is 62 stars.

Which was updated more recently, dragonfly or influxdb?

Both were last pushed on 17 November 2026.

Can I self-host both dragonfly and influxdb?

Only influxdb is marked self-hostable. dragonfly is not.

Which license is easier to embed in a commercial product, dragonfly or influxdb?

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. 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.

Who wins the dragonfly vs influxdb score?

influxdb scores 94.7 and dragonfly scores 83.0. This page calls that a clear lead for influxdb.

Related comparisons