Skip to content
DevUtils Online

Databases

chartdb vs influxdb

influxdb leads by 9.5 · clear

A

chartdb

85.2

23,133 stars · AGPL-3.0

B · leads

influxdb

94.7

31,816 stars · Apache-2.0

chartdb versus influxdb is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. chartdb is written mainly in TypeScript; influxdb is written mainly in Rust. The composite score is 85.2 for chartdb and 94.7 for influxdb.

influxdb has 31,816 GitHub stars to chartdb's 23,133, a gap of 8,683 (1.38×). Forks are 1,527 for chartdb and 3,826 for influxdb. On the log scale used inside this pair, adoption is 97 versus 100, and the fork community is 89 versus 100.

Push history: chartdb was last pushed on 01 November 2026 (16 days ago), and influxdb was last pushed on 17 November 2026 (0 days ago). Open issues stand at 155 for chartdb (0.007 per star) and 2,175 for influxdb (0.068 per star). Issue-health scores are 84 and 52; activity scores are 78 and 100.

chartdb is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. 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 52 for chartdb and 96 for influxdb. This is a procurement signal, not legal advice.

In Databases, both chartdb (23,133 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: chartdb is open source, influxdb is open source.

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

influxdb finishes ahead at 94.7 against chartdb at 85.2, a 9.5 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.

chartdb versus influxdb metrics
Signal chartdb influxdb
GitHub stars 23,133 31,816
Forks 1,527 3,826
Open issues 155 2,175
Adoption 97 100
Activity 78 100
Community 89 100
Issue health 84 52
License 52 96
Self-hosting 100 100
Composite 85.2 94.7

Questions this page answers

Which has more GitHub stars, chartdb or influxdb?

influxdb has more GitHub stars: 31,816 versus 23,133 for chartdb. The gap is 8,683 stars.

Which was updated more recently, chartdb or influxdb?

influxdb was pushed more recently: 17 November 2026 versus 01 November 2026 for chartdb. That is 16 days apart.

Can I self-host both chartdb and influxdb?

Yes. This catalog marks both chartdb and influxdb as self-hostable. Confirm each project's deploy docs before you plan a migration.

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

chartdb is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. 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 chartdb vs influxdb score?

influxdb scores 94.7 and chartdb scores 85.2. This page calls that a clear lead for influxdb.

Related comparisons