A
neon
79.4
23,335 stars · Apache-2.0
Databases
redis leads by 4.0 · narrow
A
79.4
23,335 stars · Apache-2.0
B · leads
83.4
77,588 stars · license n/a
neon versus redis 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; redis is written mainly in C. The composite score is 79.4 for neon and 83.4 for redis.
redis has 77,588 GitHub stars to neon's 23,335, a gap of 54,253 (3.32×). Forks are 1,139 for neon and 25,072 for redis. On the log scale used inside this pair, adoption is 89 versus 100, and the fork community is 70 versus 100.
Push history: neon was last pushed on 31 August 2026 (78 days ago), and redis was last pushed on 17 November 2026 (0 days ago). Open issues stand at 589 for neon (0.025 per star) and 3,122 for redis (0.040 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. redis 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 redis. This is a procurement signal, not legal advice.
Only neon is marked self-hostable here (23,335 stars, deploy score 100). redis is not (77,588 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, redis is unpriced in this catalog.
The lead is split. neon is furthest ahead on license flexibility (96 to 30), while redis is furthest ahead on recent activity (100 to 58). Choose the dimension a rollout cannot compromise on.
redis finishes ahead at 83.4 against neon at 79.4, a 4.0 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 | redis |
|---|---|---|
| GitHub stars | 23,335 | 77,588 |
| Forks | 1,139 | 25,072 |
| Open issues | 589 | 3,122 |
| Adoption | 89 | 100 |
| Activity | 58 | 100 |
| Community | 70 | 100 |
| Issue health | 70 | 70 |
| License | 96 | 30 |
| Self-hosting | 100 | 35 |
| Composite | 79.4 | 83.4 |
Neon: Serverless Postgres. We separated storage and compute to offer autoscaling, code-like database branching, and scale to zero.
For developers, who are building real-time data-driven applications, Redis is the preferred, fastest, and most feature-rich cache, data structure server, and document and vector query engine.
redis has more GitHub stars: 77,588 versus 23,335 for neon. The gap is 54,253 stars.
redis was pushed more recently: 17 November 2026 versus 31 August 2026 for neon. That is 78 days apart.
Only neon is marked self-hostable. redis 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. redis 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.
redis scores 83.4 and neon scores 79.4. This page calls that a narrow lead for redis.