Skip to content
DevUtils Online

Databases

dragonfly vs neon

neon leads by 1.2 · narrow

A

dragonfly

84.8

31,878 stars · license n/a

B · leads

neon

86.0

23,335 stars · Apache-2.0

dragonfly versus neon 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++; neon is written mainly in Rust. The composite score is 84.8 for dragonfly and 86.0 for neon.

dragonfly has 31,878 GitHub stars to neon's 23,335, a gap of 8,543 (1.37×). Forks are 1,294 for dragonfly and 1,139 for neon. On the log scale used inside this pair, adoption is 100 versus 97, and the fork community is 100 versus 98.

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

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. 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 30 for dragonfly and 96 for neon. This is a procurement signal, not legal advice.

Only neon is marked self-hostable here (23,335 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, neon is open source.

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

neon finishes ahead at 86.0 against dragonfly at 84.8, a 1.2 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.

dragonfly versus neon metrics
Signal dragonfly neon
GitHub stars 31,878 23,335
Forks 1,294 1,139
Open issues 209 589
Adoption 100 97
Activity 100 58
Community 100 98
Issue health 84 70
License 30 96
Self-hosting 35 100
Composite 84.8 86.0

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, dragonfly or neon?

dragonfly has more GitHub stars: 31,878 versus 23,335 for neon. The gap is 8,543 stars.

Which was updated more recently, dragonfly or neon?

dragonfly was pushed more recently: 17 November 2026 versus 31 August 2026 for neon. That is 78 days apart.

Can I self-host both dragonfly and neon?

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

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

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

neon scores 86.0 and dragonfly scores 84.8. This page calls that a narrow lead for neon.

Related comparisons