Over time we kept running into the same problem with Prisma ORM.

The architecture that got us here started slowing us down. Fixes took longer. Adding new capabilities got harder.

So we asked: what would Prisma look like if we rebuilt it today? pic.twitter.com/Fcl9GUwvyj

— Prisma Postgres (@prisma) March 10, 2026

That question led to Prisma Next.

A new foundation for Prisma ORM written fully in TypeScript.

The goal is not to change the developer experience people like.

The goal is to remove the constraints in the current codebase so Prisma can evolve faster.

— Prisma Postgres (@prisma) March 10, 2026

The guiding idea behind Prisma Next is simple.

Keep the core experience developers rely on:
- declarative schema
- model-first queries
- strong type safety

But make the system composable and extensible by default.

— Prisma Postgres (@prisma) March 10, 2026

Prisma Next also introduces a built-in type-safe SQL query builder.

When you need more control, you can drop down to SQL while still keeping full type safety from your schema. pic.twitter.com/4pBruqVLJs

— Prisma Postgres (@prisma) March 10, 2026

It also changes how Prisma ORM can evolve.

Instead of one fixed bundle, Prisma Next is modular. Database features and extensions can plug directly into the system.

That means Prisma ORM can grow alongside modern databases and new capabilities. pic.twitter.com/LMWWVqcXj0

— Prisma Postgres (@prisma) March 10, 2026

A lot of thoughtful work is going into Prisma Next.

Huge appreciation to the our engineers putting in the time & care to push it forward. Special shoutout to @william_ma14406 for the effort & leadership behind the scenes.

Read the full blog to learn about our vision 👇…

— Prisma Postgres (@prisma) March 10, 2026