A
neon
86.4
23,335 stars · Apache-2.0
Databases
turso leads by 8.3 · clear
A
86.4
23,335 stars · Apache-2.0
B · leads
94.7
25,279 stars · MIT
neon versus turso 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 86.4 for neon and 94.7 for turso.
turso has 25,279 GitHub stars to neon's 23,335, a gap of 1,944 (1.08×). Forks are 1,139 for neon and 1,553 for turso. On the log scale used inside this pair, adoption is 99 versus 100, and the fork community is 96 versus 100.
Push history: neon was last pushed on 31 August 2026 (78 days ago), and turso was last pushed on 17 November 2026 (0 days ago). Open issues stand at 589 for neon (0.025 per star) and 1,714 for turso (0.068 per star). Issue-health scores are 70 and 52; 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. turso is listed as MIT, 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 96 for neon and 96 for turso. This is a procurement signal, not legal advice.
In Databases, both neon (23,335 stars) and turso (25,279 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: neon is open source, turso is open source.
The lead is split. neon is furthest ahead on issue health (70 to 52), while turso is furthest ahead on recent activity (100 to 58). Choose the dimension a rollout cannot compromise on.
turso finishes ahead at 94.7 against neon at 86.4, a 8.3 point clear 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 | turso |
|---|---|---|
| GitHub stars | 23,335 | 25,279 |
| Forks | 1,139 | 1,553 |
| Open issues | 589 | 1,714 |
| Adoption | 99 | 100 |
| Activity | 58 | 100 |
| Community | 96 | 100 |
| Issue health | 70 | 52 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 86.4 | 94.7 |
Neon: Serverless Postgres. We separated storage and compute to offer autoscaling, code-like database branching, and scale to zero.
A SQL database in Rust: SQLite-compatible, now also speaking Postgres (experimental). The LLVM of databases.
turso has more GitHub stars: 25,279 versus 23,335 for neon. The gap is 1,944 stars.
turso was pushed more recently: 17 November 2026 versus 31 August 2026 for neon. That is 78 days apart.
Yes. This catalog marks both neon and turso as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. turso is listed as MIT, 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.
turso scores 94.7 and neon scores 86.4. This page calls that a clear lead for turso.