Skip to content
DevUtils Online

Databases

chartdb vs neon

chartdb leads by 1.1 · narrow

A · leads

chartdb

87.8

23,133 stars · AGPL-3.0

B

neon

86.7

23,335 stars · Apache-2.0

chartdb versus neon 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; neon is written mainly in Rust. The composite score is 87.8 for chartdb and 86.7 for neon.

neon has 23,335 GitHub stars to chartdb's 23,133, a gap of 202 (1.01×). Forks are 1,527 for chartdb and 1,139 for neon. On the log scale used inside this pair, adoption is 100 versus 100, and the fork community is 100 versus 96.

Push history: chartdb was last pushed on 01 November 2026 (16 days ago), and neon was last pushed on 31 August 2026 (78 days ago). Open issues stand at 155 for chartdb (0.007 per star) and 589 for neon (0.025 per star). Issue-health scores are 84 and 70; activity scores are 78 and 58.

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. neon 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 neon. This is a procurement signal, not legal advice.

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

The lead is split. chartdb is furthest ahead on recent activity (78 to 58), while neon is furthest ahead on license flexibility (96 to 52). Choose the dimension a rollout cannot compromise on.

chartdb finishes ahead at 87.8 against neon at 86.7, a 1.1 point narrow 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 neon metrics
Signal chartdb neon
GitHub stars 23,133 23,335
Forks 1,527 1,139
Open issues 155 589
Adoption 100 100
Activity 78 58
Community 100 96
Issue health 84 70
License 52 96
Self-hosting 100 100
Composite 87.8 86.7

neon

Neon: Serverless Postgres. We separated storage and compute to offer autoscaling, code-like database branching, and scale to zero.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, chartdb or neon?

neon has more GitHub stars: 23,335 versus 23,133 for chartdb. The gap is 202 stars.

Which was updated more recently, chartdb or neon?

chartdb was pushed more recently: 01 November 2026 versus 31 August 2026 for neon. That is 62 days apart.

Can I self-host both chartdb and neon?

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

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. neon 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 neon score?

chartdb scores 87.8 and neon scores 86.7. This page calls that a narrow lead for chartdb.

Related comparisons