A · leads
DuckDB
96.5
43,126 stars · MIT
Databases
DuckDB leads by 13.4 · clear
A · leads
96.5
43,126 stars · MIT
B
83.1
23,335 stars · Apache-2.0
DuckDB versus neon is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. DuckDB is written mainly in C++; neon is written mainly in Rust. The composite score is 96.5 for DuckDB and 83.1 for neon.
DuckDB has 43,126 GitHub stars to neon's 23,335, a gap of 19,791 (1.85×). Forks are 4,214 for DuckDB and 1,139 for neon. On the log scale used inside this pair, adoption is 100 versus 94, and the fork community is 100 versus 84.
Push history: DuckDB 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 1,261 for DuckDB (0.029 per star) and 589 for neon (0.025 per star). Issue-health scores are 70 and 70; activity scores are 100 and 58.
DuckDB 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. 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 96 for DuckDB and 96 for neon. This is a procurement signal, not legal advice.
In Databases, both DuckDB (43,126 stars) and neon (23,335 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: DuckDB is open source, neon is open source.
DuckDB is ahead on every scored dimension that is not level. Level dimensions: issue health, license flexibility, self-hosting. The widest gap is recent activity at 42 points (100 vs 58), and the tightest is self-hosting at 0 points (100 vs 100).
DuckDB finishes ahead at 96.5 against neon at 83.1, a 13.4 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 | DuckDB | neon |
|---|---|---|
| GitHub stars | 43,126 | 23,335 |
| Forks | 4,214 | 1,139 |
| Open issues | 1,261 | 589 |
| Adoption | 100 | 94 |
| Activity | 100 | 58 |
| Community | 100 | 84 |
| Issue health | 70 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 96.5 | 83.1 |
DuckDB is an in-process analytical database, often described as SQLite for OLAP. It runs inside the application process and queries local files such as Parquet.
Neon: Serverless Postgres. We separated storage and compute to offer autoscaling, code-like database branching, and scale to zero.
DuckDB has more GitHub stars: 43,126 versus 23,335 for neon. The gap is 19,791 stars.
DuckDB was pushed more recently: 17 November 2026 versus 31 August 2026 for neon. That is 78 days apart.
Yes. This catalog marks both DuckDB and neon as self-hostable. Confirm each project's deploy docs before you plan a migration.
DuckDB 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. 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.
DuckDB scores 96.5 and neon scores 83.1. This page calls that a clear lead for DuckDB.