A · leads
neon
87.0
23,335 stars · Apache-2.0
Databases
neon leads by 3.6 · narrow
A · leads
87.0
23,335 stars · Apache-2.0
B
83.4
25,561 stars · license n/a
neon versus SpacetimeDB 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 87.0 for neon and 83.4 for SpacetimeDB.
SpacetimeDB has 25,561 GitHub stars to neon's 23,335, a gap of 2,226 (1.10×). Forks are 1,139 for neon and 1,121 for SpacetimeDB. On the log scale used inside this pair, adoption is 99 versus 100, and the fork community is 100 versus 100.
Push history: neon was last pushed on 31 August 2026 (78 days ago), and SpacetimeDB was last pushed on 17 November 2026 (0 days ago). Open issues stand at 589 for neon (0.025 per star) and 984 for SpacetimeDB (0.038 per star). Issue-health scores are 70 and 70; 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. SpacetimeDB 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 SpacetimeDB. This is a procurement signal, not legal advice.
Only neon is marked self-hostable here (23,335 stars, deploy score 100). SpacetimeDB is not (25,561 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, SpacetimeDB is unpriced in this catalog.
The lead is split. neon is furthest ahead on license flexibility (96 to 30), while SpacetimeDB is furthest ahead on recent activity (100 to 58). Choose the dimension a rollout cannot compromise on.
neon finishes ahead at 87.0 against SpacetimeDB at 83.4, a 3.6 point narrow margin under the published weights.
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 | SpacetimeDB |
|---|---|---|
| GitHub stars | 23,335 | 25,561 |
| Forks | 1,139 | 1,121 |
| Open issues | 589 | 984 |
| Adoption | 99 | 100 |
| Activity | 58 | 100 |
| Community | 100 | 100 |
| Issue health | 70 | 70 |
| License | 96 | 30 |
| Self-hosting | 100 | 35 |
| Composite | 87.0 | 83.4 |
Neon: Serverless Postgres. We separated storage and compute to offer autoscaling, code-like database branching, and scale to zero.
Development at the speed of light
SpacetimeDB has more GitHub stars: 25,561 versus 23,335 for neon. The gap is 2,226 stars.
SpacetimeDB was pushed more recently: 17 November 2026 versus 31 August 2026 for neon. That is 78 days apart.
Only neon is marked self-hostable. SpacetimeDB 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. SpacetimeDB 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.
neon scores 87.0 and SpacetimeDB scores 83.4. This page calls that a narrow lead for neon.