A · leads
chroma
96.5
29,704 stars · Apache-2.0
Databases
chroma leads by 11.5 · clear
A · leads
96.5
29,704 stars · Apache-2.0
B
85.0
23,335 stars · Apache-2.0
chroma versus neon 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 96.5 for chroma and 85.0 for neon.
chroma has 29,704 GitHub stars to neon's 23,335, a gap of 6,369 (1.27×). Forks are 2,609 for chroma and 1,139 for neon. On the log scale used inside this pair, adoption is 100 versus 98, and the fork community is 100 versus 90.
Push history: chroma was last pushed on 13 November 2026 (3 days ago), and neon was last pushed on 31 August 2026 (78 days ago). Open issues stand at 979 for chroma (0.033 per star) and 589 for neon (0.025 per star). Issue-health scores are 70 and 70; activity scores are 100 and 58.
Both chroma and neon are listed as Apache-2.0. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In Databases, both chroma (29,704 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: chroma is open source, neon is open source.
chroma 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).
chroma finishes ahead at 96.5 against neon at 85.0, a 11.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 | chroma | neon |
|---|---|---|
| GitHub stars | 29,704 | 23,335 |
| Forks | 2,609 | 1,139 |
| Open issues | 979 | 589 |
| Adoption | 100 | 98 |
| Activity | 100 | 58 |
| Community | 100 | 90 |
| Issue health | 70 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 96.5 | 85.0 |
Search infrastructure for AI
Neon: Serverless Postgres. We separated storage and compute to offer autoscaling, code-like database branching, and scale to zero.
chroma has more GitHub stars: 29,704 versus 23,335 for neon. The gap is 6,369 stars.
chroma was pushed more recently: 13 November 2026 versus 31 August 2026 for neon. That is 75 days apart.
Yes. This catalog marks both chroma and neon as self-hostable. Confirm each project's deploy docs before you plan a migration.
chroma 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. 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.
chroma scores 96.5 and neon scores 85.0. This page calls that a clear lead for chroma.