Prisma Next Roadmap

On March 4th we introduced Prisma Next, the future of Prisma ORM. We made the repo public so you can follow progress. We shared some of what we've built so far and what's in the works, including:

• a brand new query API with custom collection methods for your models
• streaming query results
• a low-level, type-safe SQL query builder (an escape hatch for complex or custom SQL queries)
• extensions that let you install new behaviors and data types (including the first extension example: pgvector)
• support for TypeScript Prisma schemas as an alternative to the traditional schema.prisma, so you can pick which you prefer
• middleware, validations, query linting, and lots more

There's a lot still to do, so to make sure we can get Prisma Next into developers' hands as soon as possible, we're delivering the remaining work in phases.

April: Enable external contributions

We want external contributors to be able to add new Prisma Next features, like:

• SQL database targets
• Postgres extensions
• middleware for telemetry, error reporting, and query checks
• new query builders
• validator integrations (like Zod and Arktype)
• integrations with services like Sentry and Datadog
• integrations with popular frameworks like Next.js and Vue.js

These are just some of our ideas and we want to open Prisma Next to hear your ideas.

We're currently focused on developing stable APIs for extension points, establishing reliable interfaces for extension authors, and validating core framework concepts.

In April, we'll put out a public call inviting collaborators to join us to extend Prisma Next. We will work with you during April to implement your extensions and polish the small things we inevitably got wrong.

We're already working with the MongoDB and ParadeDB teams on POCs to validate that the architecture genuinely supports non-SQL targets and extension-provided database primitives.

If you want to get in early and help shape the final version of Prisma Next, April is the time to get involved.

May: Early access

Next, we want to get Prisma Next into users' hands. We need to see how it holds up in real-world applications, so we'll follow our normal EA process: an initial release, a period of feedback and refinement, then General Availability.

As soon as it's ready, we'll put out a public announcement alongside getting started material and guides explaining the key differences between Prisma 7 and Prisma Next.

By this point we expect the user-facing APIs to be stable for Postgres and one additional SQL database (SQLite is our top pick).

If you want to adopt Prisma Next early, May is the time to get started.

June - July: Postgres General Availability

Between the EA release in May and July, we want to bring Prisma Next Postgres support to GA, giving it our stamp of approval as a production-ready product. Prisma 7 will continue to receive long-term support for teams that want a fully battle-tested foundation.

For teams looking to upgrade, you'll be able to run Prisma Next and Prisma 7 in parallel and gradually shift traffic from one to the other. We'll also provide a compatibility layer so you don't need to immediately rewrite all your queries.

Follow along

For the most up-to-date view, follow the roadmap in the Prisma Next repo as it develops in real time. We'll post announcements like this one as we learn more.

For the broader picture, check out the Prisma Next repo and star it to subscribe to updates.