A
neon
83.6
23,335 stars · Apache-2.0
Databases
quivr leads by 15.5 · decisive
A
83.6
23,335 stars · Apache-2.0
B · leads
99.1
39,655 stars · MIT
neon versus quivr 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; quivr is written mainly in Go. The composite score is 83.6 for neon and 99.1 for quivr.
quivr has 39,655 GitHub stars to neon's 23,335, a gap of 16,320 (1.70×). Forks are 1,139 for neon and 3,730 for quivr. On the log scale used inside this pair, adoption is 95 versus 100, and the fork community is 86 versus 100.
Push history: neon was last pushed on 31 August 2026 (78 days ago), and quivr was last pushed on 16 November 2026 (1 day ago). Open issues stand at 589 for neon (0.025 per star) and 16 for quivr (0.000 per star). Issue-health scores are 70 and 96; 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. quivr 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 quivr. This is a procurement signal, not legal advice.
In Databases, both neon (23,335 stars) and quivr (39,655 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, quivr is open source.
quivr is ahead on every scored dimension that is not level. Level dimensions: license flexibility, self-hosting. The widest gap is recent activity at 42 points (58 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
quivr finishes ahead at 99.1 against neon at 83.6, a 15.5 point decisive 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 | quivr |
|---|---|---|
| GitHub stars | 23,335 | 39,655 |
| Forks | 1,139 | 3,730 |
| Open issues | 589 | 16 |
| Adoption | 95 | 100 |
| Activity | 58 | 100 |
| Community | 86 | 100 |
| Issue health | 70 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 83.6 | 99.1 |
Neon: Serverless Postgres. We separated storage and compute to offer autoscaling, code-like database branching, and scale to zero.
An open-source engine that turns continuous content streams into search and monitoring. Durable ingestion, hybrid search, alerts, and plugins for formats, models and business rules.
quivr has more GitHub stars: 39,655 versus 23,335 for neon. The gap is 16,320 stars.
quivr was pushed more recently: 16 November 2026 versus 31 August 2026 for neon. That is 77 days apart.
Yes. This catalog marks both neon and quivr 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. quivr 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.
quivr scores 99.1 and neon scores 83.6. This page calls that a decisive lead for quivr.