Skip to content
DevUtils Online

Databases

chartdb vs Valkey

Valkey leads by 9.3 · clear

A

chartdb

87.2

23,133 stars · AGPL-3.0

B · leads

Valkey

96.5

27,730 stars · BSD-3-Clause

chartdb versus Valkey 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; Valkey is written mainly in C. The composite score is 87.2 for chartdb and 96.5 for Valkey.

Valkey has 27,730 GitHub stars to chartdb's 23,133, a gap of 4,597 (1.20×). Forks are 1,527 for chartdb and 1,540 for Valkey. On the log scale used inside this pair, adoption is 98 versus 100, and the fork community is 100 versus 100.

Push history: chartdb was last pushed on 01 November 2026 (16 days ago), and Valkey was last pushed on 17 November 2026 (0 days ago). Open issues stand at 155 for chartdb (0.007 per star) and 1,045 for Valkey (0.038 per star). Issue-health scores are 84 and 70; 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. Valkey is listed as BSD-3-Clause, 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 Valkey. This is a procurement signal, not legal advice.

In Databases, both chartdb (23,133 stars) and Valkey (27,730 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, Valkey is open source.

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

Valkey finishes ahead at 96.5 against chartdb at 87.2, a 9.3 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 Valkey metrics
Signal chartdb Valkey
GitHub stars 23,133 27,730
Forks 1,527 1,540
Open issues 155 1,045
Adoption 98 100
Activity 78 100
Community 100 100
Issue health 84 70
License 52 96
Self-hosting 100 100
Composite 87.2 96.5

Valkey

Valkey is a Linux Foundation key-value store forked from Redis. It is used as a cache, queue, and ephemeral data store under a permissive license.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, chartdb or Valkey?

Valkey has more GitHub stars: 27,730 versus 23,133 for chartdb. The gap is 4,597 stars.

Which was updated more recently, chartdb or Valkey?

Valkey 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 Valkey?

Yes. This catalog marks both chartdb and Valkey 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 Valkey?

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. Valkey is listed as BSD-3-Clause, 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 Valkey score?

Valkey scores 96.5 and chartdb scores 87.2. This page calls that a clear lead for Valkey.

Related comparisons