Skip to content
DevUtils Online

Databases

cockroach vs neon

neon leads by 6.0 · narrow

A

cockroach

78.0

32,622 stars · license n/a

B · leads

neon

84.0

23,335 stars · Apache-2.0

cockroach versus neon is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. cockroach is written mainly in Go; neon is written mainly in Rust. The composite score is 78.0 for cockroach and 84.0 for neon.

cockroach has 32,622 GitHub stars to neon's 23,335, a gap of 9,287 (1.40×). Forks are 4,236 for cockroach 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 84.

Push history: cockroach was last pushed on 11 November 2026 (6 days ago), and neon was last pushed on 31 August 2026 (78 days ago). Open issues stand at 8,042 for cockroach (0.247 per star) and 589 for neon (0.025 per star). Issue-health scores are 34 and 70; activity scores are 92 and 58.

cockroach 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 cockroach 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). cockroach is not (32,622 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: cockroach is unpriced in this catalog, neon is open source.

The lead is split. cockroach is furthest ahead on recent activity (92 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 84.0 against cockroach at 78.0, a 6.0 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.

cockroach versus neon metrics
Signal cockroach neon
GitHub stars 32,622 23,335
Forks 4,236 1,139
Open issues 8,042 589
Adoption 100 97
Activity 92 58
Community 100 84
Issue health 34 70
License 30 96
Self-hosting 35 100
Composite 78.0 84.0

cockroach

CockroachDB — the cloud native, distributed SQL database designed for high availability, effortless scale, and control over data placement.

Project site · GitHub · Full profile

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

cockroach has more GitHub stars: 32,622 versus 23,335 for neon. The gap is 9,287 stars.

Which was updated more recently, cockroach or neon?

cockroach was pushed more recently: 11 November 2026 versus 31 August 2026 for neon. That is 72 days apart.

Can I self-host both cockroach and neon?

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

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

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

neon scores 84.0 and cockroach scores 78.0. This page calls that a narrow lead for neon.

Related comparisons