A
neon
83.4
23,335 stars · Apache-2.0
Databases
rocksdb leads by 7.5 · clear
A
83.4
23,335 stars · Apache-2.0
B · leads
90.9
32,285 stars · GPL-2.0
neon versus rocksdb is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. neon is written mainly in Rust; rocksdb is written mainly in C++. The composite score is 83.4 for neon and 90.9 for rocksdb.
rocksdb has 32,285 GitHub stars to neon's 23,335, a gap of 8,950 (1.38×). Forks are 1,139 for neon and 7,033 for rocksdb. On the log scale used inside this pair, adoption is 97 versus 100, and the fork community is 80 versus 100.
Push history: neon was last pushed on 31 August 2026 (78 days ago), and rocksdb was last pushed on 17 November 2026 (0 days ago). Open issues stand at 589 for neon (0.025 per star) and 1,855 for rocksdb (0.057 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. rocksdb is listed as GPL-2.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. License scores in this pair are 96 for neon and 64 for rocksdb. This is a procurement signal, not legal advice.
In Databases, both neon (23,335 stars) and rocksdb (32,285 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, rocksdb is open source.
The lead is split. neon is furthest ahead on license flexibility (96 to 64), while rocksdb is furthest ahead on recent activity (100 to 58). Choose the dimension a rollout cannot compromise on.
rocksdb finishes ahead at 90.9 against neon at 83.4, a 7.5 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 | rocksdb |
|---|---|---|
| GitHub stars | 23,335 | 32,285 |
| Forks | 1,139 | 7,033 |
| Open issues | 589 | 1,855 |
| Adoption | 97 | 100 |
| Activity | 58 | 100 |
| Community | 80 | 100 |
| Issue health | 70 | 52 |
| License | 96 | 64 |
| Self-hosting | 100 | 100 |
| Composite | 83.4 | 90.9 |
Neon: Serverless Postgres. We separated storage and compute to offer autoscaling, code-like database branching, and scale to zero.
A library that provides an embeddable, persistent key-value store for fast storage.
rocksdb has more GitHub stars: 32,285 versus 23,335 for neon. The gap is 8,950 stars.
rocksdb 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 rocksdb 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. rocksdb is listed as GPL-2.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
rocksdb scores 90.9 and neon scores 83.4. This page calls that a clear lead for rocksdb.