{"id":48236762,"title":"Show HN: Prisma Next – data contracts, migration graphs, agent DX","points":13,"user":"wmadden","time":1779461612,"time_ago":"6 hours ago","type":"link","content":"

Hey I'm Will from the Prisma team, engineering manager and also the lead developer on Prisma Next.

I'd like to introduce you all to the next version of Prisma: a full rewrite in TypeScript that builds on the established patterns in Prisma and comes with a family of skills that integrate it into whatever AI tooling you're using in 2026.

(Read the announcement on our blog here: https://pris.ly/pn-ea)

The three topics in the title are brand new concepts in Prisma Next so let me give you a quick rundown.

1. Data contracts

If you've used Prisma before you've seen the `schema.prisma` file. That's a contract between your application and your database: it spells out exactly what your app relies on and what your database promises to persist.

Your contract drives everything in Prisma Next, like queries, migrations, error checking and correctness guarantees. It's hashed to give it an identity similar to a git commit and we use that hash to sign your DB: if the DB is signed with your contract's hash, your app knows it's compatible.

2. Migration graphs, guardrails and verifications

A migration transforms your database from one contract's structure to another. That makes migrations the edges in a graph of data contracts.

In Prisma Next we don't store migrations as a sequence of alphabetically ordered SQL files that break the second you merge two branches together. Instead, we store them as a graph, similar to how git stores your filesystem changes as a graph of commits.

And we don't store migrations as black box SQL files. Each migration's on-disk structure is an `ops.json` file with a reviewable TypeScript file alongside it. Each operation has a precheck (verifies preconditions before executing) and a postcheck (verifies successful execution and provides idempotency). The migration promises to move you from contract A to contract B, and the resulting schema is verified against the destination contract before the migration is committed.

They're the safest migrations you'll ever write and they're generated for you when you change your contract.

3. Agent DX

Data contracts and verified, hashed, deterministic migrations are strong enough primitives to safely delegate this work to an agent.

Prisma Next helps pry the footgun out of our collective fingers and gives you a set of reliable, predictable tools and also a family of curated skills with guardrails on every operation. This helps you focus on building your app instead of double-checking everything your agent does.

Today we're releasing it in Early Access. It's early, there are gaps, but it's a different shape of ORM than you're used to and we want to get feedback to help us shape its future direction.

The blog post goes into more detail than I have here but the best way to get a feel for it is to run `npm create prisma@next` or just clone the repo and check it out.","url":"https://github.com/prisma/prisma-next","domain":"github.com","comments":[{"id":48236812,"level":0,"user":"sorenbs","time":1779461805,"time_ago":"6 hours ago","content":"

There's a lot of new stuff here. The complete rewrite in TypeScript alone is a huge improvement. But the new migration system is probably the most ambitious part. Very curious for feedback on that!","comments":[]},{"id":48238104,"level":0,"user":"alexbevi","time":1779467271,"time_ago":"4 hours ago","content":"

Love the MongoDB support!","comments":[]}],"comments_count":2}