Prisma Next: April milestone complete, the extension API is open

In March we published the Prisma Next roadmap. April was the month we'd open Prisma Next up to external contributors. May was the month we'd put it into users' hands.

The April milestone is complete. The extension API is open to outside authors.

Four extensions now ship on it: pgvector, arktype-json, ParadeDB, and CipherStash. One planned piece did not land: streaming subscriptions in the runtime. May shifts to Early Access for users.

If you want to build a Prisma Next extension, the call for extension authors is the front door. The API will keep evolving, but it's stable enough to build something real against — and we want to hear what's missing.

What you can build with the extension API

An extension can contribute new data types, new query operations, and new migration logic. The first four cover that range:

pgvector adds vector types and similarity queries to your Postgres schema.
arktype-json lets you store and query typed JSON columns with ArkType validation.
ParadeDB adds full-text and analytical search backed by ParadeDB's Postgres extensions.
CipherStash adds searchable encryption at rest — encrypted column types with query operations on encrypted values, built by the CipherStash team.

These are built on the same extension API the Prisma Next team uses for built-in features. If you want to see what an extension looks like end to end, the upcoming build-your-own-extension tutorial walks through a small one from scratch.

What else landed in April

Extensions are the headline, but the rest of the stack moved too. Here's what you can do now that you couldn't a month ago.

Migrations

You can author migrations in TypeScript. Scaffold a migration file, write the change in code, and the compiler emits a structured description the runner picks up and applies. TypeScript migrations in Prisma Next walks through the authoring surface.

Data migrations are partly there. You can run a data transformation — say, splitting name into firstName and lastName — and the system records what changed and what guarantees the migration leaves behind ("every row now has a non-null email"). What still needs to land: the runtime using those guarantees, so queries can take advantage of them automatically. That part carries into May. Data migrations in Prisma Next covers this in detail.

Contract authoring

You can define your data contract in contract.prisma or in TypeScript. Both surfaces produce the same compiled contract, regardless of which you choose. Next up: the everyday helpers, IDE autocomplete, and the patterns a first-time user expects to work without thinking.

Transactions and React Server Components

Transactions work on Postgres. The ORM can open a transaction, and the SQL query builder can run inside it, sharing one database connection — so the SQL escape hatch actually works mid-transaction.

The runtime runs safely under React Server Components: parallel Server Components, shared runtime state, connection pooling, and query-result caching all behave correctly under concurrency.

Middleware hooks are in place — a middleware function can see a query, return a cached result, or rewrite the response.

MongoDB

MongoDB is a first-class database family in Prisma Next. You get type-safe queries, real database migrations (indexes, JSON Schema validators, collection options), polymorphic collections with discriminated unions, embedded documents, and a typed aggregation pipeline builder. MongoDB Without Compromise covers the full story.

SQLite

We built a SQLite proof of concept that shows how straightforward it is to add more database targets to Prisma Next. More targets will roll out in the coming months, but right now our focus is Postgres and MongoDB.

What did not land

Streaming subscriptions didn't make it in April, but they will in May.

For our upcoming Supabase support, we're adding realtime query subscriptions — an adapter that receives a stream of changes from the database, a subscribe() call in the runtime, cancellation and cleanup, and change events flowing through middleware.

May: making it easy to get started

May's focus is the developer experience. We want your first hour with Prisma Next to feel smooth — from scaffolding a project to running your first query. When it's ready, we'll launch Prisma Next as Early Access for Postgres and MongoDB.

Three things to watch this month:

Getting started gets smoother. Project scaffolding, db init, db update, CLI consistency, error messages that tell you what to do next. Contract authoring picks up the patterns you'd reach for on day one — scalar arrays, composite keys, @updatedAt, native type annotations — and the language server stops showing false errors on valid Prisma Next schemas.
The query and migration surfaces keep maturing. Transactions extend to SQLite and MongoDB. The SQL query builder covers more real-world escape-hatch patterns. The migration workflow gets clearer output, smoother manual migration UX, and preflight verification.
New platform support. First-class Supabase support, including realtime query subscriptions. Cloudflare Workers ships as a first-party Postgres module.

Try it out

You can start building with Prisma Next today. Run npx prisma-next init, open the contract, add a model, run prisma-next migration plan — it takes about as long as reading this paragraph.

The API is still settling, so expect breaking changes often. If you find rough edges or something you were hoping for that's missing, drop into #prisma-next on Discord and tell us. Feedback right now is the most valuable thing we can get.

Star or watch prisma/prisma-next on GitHub to follow updates as they land, and subscribe to the Prisma blog for the monthly milestone update.

Prisma Next is not yet production-ready. Prisma 7 remains the right choice for production today, and when Prisma Next is ready for general use, it becomes Prisma 8.

Prisma Next: April Milestone Complete, the Extension API Is Open