A · level
neon
85.7
23,335 stars · Apache-2.0
Databases
Too close to call · 85.7 to 84.8
A · level
85.7
23,335 stars · Apache-2.0
B · level
84.8
33,315 stars · license n/a
neon versus surrealdb is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in Rust. The composite score is 85.7 for neon and 84.8 for surrealdb.
surrealdb has 33,315 GitHub stars to neon's 23,335, a gap of 9,980 (1.43×). Forks are 1,139 for neon and 1,408 for surrealdb. On the log scale used inside this pair, adoption is 97 versus 100, and the fork community is 97 versus 100.
Push history: neon was last pushed on 31 August 2026 (78 days ago), and surrealdb was last pushed on 17 November 2026 (0 days ago). Open issues stand at 589 for neon (0.025 per star) and 443 for surrealdb (0.013 per star). Issue-health scores are 70 and 84; activity scores are 58 and 100.
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. surrealdb 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. License scores in this pair are 96 for neon and 30 for surrealdb. This is a procurement signal, not legal advice.
Only neon is marked self-hostable here (23,335 stars, deploy score 100). surrealdb is not (33,315 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: neon is open source, surrealdb is unpriced in this catalog.
The lead is split. neon is furthest ahead on license flexibility (96 to 30), while surrealdb is furthest ahead on recent activity (100 to 58). Choose the dimension a rollout cannot compromise on.
Composite score: neon 85.7, surrealdb 84.8. The margin is under one point, so this page calls a tie. Use the dimension breakdown rather than the headline number.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | neon | surrealdb |
|---|---|---|
| GitHub stars | 23,335 | 33,315 |
| Forks | 1,139 | 1,408 |
| Open issues | 589 | 443 |
| Adoption | 97 | 100 |
| Activity | 58 | 100 |
| Community | 97 | 100 |
| Issue health | 70 | 84 |
| License | 96 | 30 |
| Self-hosting | 100 | 35 |
| Composite | 85.7 | 84.8 |
Neon: Serverless Postgres. We separated storage and compute to offer autoscaling, code-like database branching, and scale to zero.
A scalable, distributed, collaborative, document-graph database, for the realtime web
surrealdb has more GitHub stars: 33,315 versus 23,335 for neon. The gap is 9,980 stars.
surrealdb was pushed more recently: 17 November 2026 versus 31 August 2026 for neon. That is 78 days apart.
Only neon is marked self-hostable. surrealdb is not.
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. surrealdb 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Neither tool clears a one-point margin. neon scores 85.7 and surrealdb scores 84.8.