Use Prisma Next with Supabase and pin Prisma Compute preview branches

Prisma Next now runs a stock Supabase project end to end through @prisma-next/extension-supabase, and adds Row-Level Security policy authoring in the schema and in TypeScript, plus managed native PostgreSQL enum migrations.

Prisma Compute reclaims preview environments that have been idle for 48 hours and lets you pin the ones you want to keep. Projects now set their region once at creation, and databases and apps inherit it.

Prisma Postgres warns you before you hit your database limit, with a dashboard banner and emails at 75% and at the limit. Prisma Studio adds a Migrations view that renders Prisma Next migration history as visual contract diffs. Prisma ORM extends its AI safety checkpoint to prisma db push --accept-data-loss.

Highlights

NewPrisma Next runs Supabase projects end to end

Using Prisma Next against Supabase used to fail on first contact: generated Row-Level Security migrations could not be imported, migrate rejected its own remediation, and JWKS and grants needed manual repair. The @prisma-next/extension-supabase package now takes a stock Supabase project from plan to migrate to verify without intervention, declares Supabase roles in the schema, and ships with a complete Supabase contract introspected from a reference instance.

Note: Prisma Next is in Early Access. Scope and behavior may still change.

$ npx prisma-next migration plan --name init
$ npx prisma-next migrate --yes
$ npx prisma-next db verify

Shipped in prisma/prisma-next#960, prisma/prisma-next#987, and prisma/prisma-next#997.

NewPrisma Compute reclaims idle preview environments, and pinning keeps them

Stale preview environments used to accumulate until you deleted them by hand, holding database quota the whole time. Prisma Compute now reclaims a preview environment, both the app and its database, after 48 hours without a push, and the Prisma Console branches view gains a Pin control that exempts a branch from cleanup. Production branches are never reclaimed.

Note: Prisma Compute is in Public Beta.

Read the branching docs for how production and preview branches differ.

NewPrisma Studio shows Prisma Next migration history as visual diffs

Inspecting an applied Prisma Next migration meant reading its ledger rows by hand. Prisma Studio now shows a Migrations view whenever the connected database carries a prisma_contract ledger: a newest-first timeline of every applied migration with its name, apply time, operation count, and destructive-change marker, plus a visual diff of what each migration did to models, fields, enums, and indexes, the SQL that ran, and a schema diff. Prisma Studio reads the history from the database itself, so it works for any Prisma Next PostgreSQL database you can connect to.

Read the launch post for a tour of the timeline, SQL, and schema panels, and the Studio with Prisma Next docs for setup. Shipped in prisma/studio#1533.

Prisma Next

Prisma Next adds Row-Level Security policy authoring in the schema and in TypeScript, and manages the full lifecycle of native PostgreSQL enums in migrations.

namespace public {
  model Profile { id String @id; userId String; @@rls }

  // anyone may read the public directory; owners may always read their own row
  policy_select profile_public_read { target = Profile; roles = [anon];          using = "true" }
  policy_select profile_owner_read  { target = Profile; roles = [authenticated]; using = "userId::uuid = auth.uid()" }
}

Prisma Compute

Prisma Compute sets a project's region once at creation, inherits it across databases and apps, and reworks custom-domain setup around the CNAME record.

Prisma Postgres

Prisma Postgres now warns you before database creation hits your plan's limit.

Prisma Console

The Prisma Console adds a workspace support portal.

Prisma ORM

Prisma ORM closes a gap in its AI agent safety checkpoint.

Prisma Studio

Prisma Studio 0.33.0 is now bundled in the Prisma CLI.

Fixes and improvements

Prisma Next

Prisma ORM

Prisma Studio

Prisma Compute

Guides and articles

• Your AI Agent Needs a Database. Give It One in Five Seconds: how coding agents can provision a temporary Prisma Postgres database with npx create-db, no sign-up, with --json output agents can parse.
• Serverless Postgres: the definitive guide: a category guide comparing serverless PostgreSQL providers and their pricing models, with an interactive decision tree and a worked cost-crossover example.
• TypeScript 7 native compiler: faster type checking: migrating a large TypeScript monorepo to the native Go compiler cut whole-repo type checking to roughly a third of the time.
• You Don't Need a Vector Database, Postgres Already Has pgvector: builds working semantic search on a temporary Prisma Postgres database with pgvector, with type-safe queries through Prisma Next.
• You Don't Need a Job Queue, Postgres Already Has SKIP LOCKED: builds a reliable background job queue with retries on Prisma Postgres using FOR UPDATE SKIP LOCKED, no separate broker required.
• What to Put in Your AGENTS.md So Your Agent Handles the Database Right: a copy-pasteable AGENTS.md section for database work: ephemeral PostgreSQL via npx create-db, safe migrations, and JSON output for coding agents.

Need help applying these changes in production? Prisma Enterprise Support can help with schema design, performance, security, and compliance.