Skip to content
DevUtils Online

Databases

neon vs orm

orm leads by 11.1 · clear

A

neon

83.6

23,335 stars · Apache-2.0

B · leads

orm

94.7

47,675 stars · Apache-2.0

neon versus orm 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; orm is written mainly in TypeScript. The composite score is 83.6 for neon and 94.7 for orm.

orm has 47,675 GitHub stars to neon's 23,335, a gap of 24,340 (2.04×). Forks are 1,139 for neon and 2,635 for orm. On the log scale used inside this pair, adoption is 93 versus 100, and the fork community is 89 versus 100.

Push history: neon was last pushed on 31 August 2026 (78 days ago), and orm was last pushed on 17 November 2026 (0 days ago). Open issues stand at 589 for neon (0.025 per star) and 2,817 for orm (0.059 per star). Issue-health scores are 70 and 52; activity scores are 58 and 100.

Both neon and orm 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 neon (23,335 stars) and orm (47,675 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, orm is open source.

The lead is split. neon is furthest ahead on issue health (70 to 52), while orm is furthest ahead on recent activity (100 to 58). Choose the dimension a rollout cannot compromise on.

orm finishes ahead at 94.7 against neon at 83.6, a 11.1 point clear margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

neon versus orm metrics
Signal neon orm
GitHub stars 23,335 47,675
Forks 1,139 2,635
Open issues 589 2,817
Adoption 93 100
Activity 58 100
Community 89 100
Issue health 70 52
License 96 96
Self-hosting 100 100
Composite 83.6 94.7

neon

Neon: Serverless Postgres. We separated storage and compute to offer autoscaling, code-like database branching, and scale to zero.

Project site · GitHub · Full profile

orm

The Prisma ORM: write your application in TypeScript with human-readable queries instead of SQL. Host your database on Prisma Postgres and your app on Prisma Compute.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, neon or orm?

orm has more GitHub stars: 47,675 versus 23,335 for neon. The gap is 24,340 stars.

Which was updated more recently, neon or orm?

orm was pushed more recently: 17 November 2026 versus 31 August 2026 for neon. That is 78 days apart.

Can I self-host both neon and orm?

Yes. This catalog marks both neon and orm as self-hostable. Confirm each project's deploy docs before you plan a migration.

Which license is easier to embed in a commercial product, neon or orm?

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. orm 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.

Who wins the neon vs orm score?

orm scores 94.7 and neon scores 83.6. This page calls that a clear lead for orm.

Related comparisons