About
下一代 Node.js / TypeScript ORM
Discord | X | Blog Post | Architecture
Looking for Prisma ORM 7? It lives on the
v7branch of this repository, and theprismaand@prisma/*packages on npm continue to be published from there.
Prisma Next is currently in Early Access and we're building it in the open with the community. APIs will still evolve as your feedback shapes them, so we don't recommend it for production workloads yet. Come along for the ride: star the repo, follow @prisma on X, or read along on the Prisma blog.
Prisma Next is a TypeScript rewrite of Prisma ORM, designed to be extensible, composable, and AI-agent friendly by default. Read the full announcement: The Next Evolution of Prisma ORM.
Prerequisites
- Node.js 24 or newer
- A package manager (
npm,pnpm, oryarn)
Getting started
1. Scaffold a new project
The interactive scaffolder picks a JavaScript framework (Next.js, Vite, Hono, and others) and wires Prisma Next in with your chosen database (PostgreSQL or MongoDB):
npm create prisma@nextYou finish with a runnable app, a starter contract, and the agent skills already registered.
2. Or, add Prisma Next to an existing project
Run this from your repo root:
npx @prisma/cli@next orm initprisma orm init writes prisma.config.ts, scaffolds a starter contract and db.ts under src/prisma/, installs the runtime, emits the contract, and registers the agent skills. It does not touch your framework or build setup.
3. Use your AI agent for everything Prisma Next
Both installers leave a top-level prisma-next.md primer at your project root for any agent to read first. init additionally materialises one SKILL.md per workflow in two places, so different agent runtimes can find them at their expected paths:
.claude/skills/<skill-name>/SKILL.md— picked up by Claude Code.agents/skills/<skill-name>/SKILL.md— universal location for Cursor, Copilot Agent, and other runtimes
A skills-lock.json at the project root tracks which skill versions are installed. Your editor's AI assistant auto-loads the right skill when your prompt matches.
Just describe what you want. For example:
"Add a
postsmodel with a relation tousers, then write a query that loads each user's three most recent posts."
The agent loads the prisma-8 skill, opens its contract and queries references, then drives the change end-to-end.
For the full catalogue and what each skill covers, see skills/README.md.
Found a bug, missing a feature, or have a question for the team?
Ask your agent. The prisma-8 skill's feedback flow drafts a structured GitHub issue or hands you a Prisma Discord link for live Q&A. You can review and confirm before anything is submitted.
For extension authors
Prisma Next has a minimal core. Everything around it, including Postgres support itself, is built on the same public SPI that's available to any author. If you've wanted to integrate your tool, your database, or your library with Prisma, this is the way in.
A few extensions already shipping:
@internal/extension-pgvector: vector columns and similarity operators for semantic search.@internal/extension-paradedb: typed BM25 indexes with multiple tokenizers for full-text search.@internal/extension-postgis: geospatial types and queries.@cipherstash/prisma-next: searchable encryption and data-level access control.
Want to ship your own? The Authoring Prisma Next Extensions blog walks through the SPI, the layers your extension can hook into, and how the team features new extensions in the Prisma Next directory.
Supported databases
Prisma 8 carries PostgreSQL to general availability — and that is all at this stage:
- PostgreSQL — the primary target; general availability at Prisma 8
- MongoDB — early access; proves the framework works beyond SQL
- SQLite — a proof of concept today
MySQL follows later. See the roadmap for what must happen before the 8.0.0-rc.1 release.
Contributing
See CONTRIBUTING.md for setup, commands, DCO signoff, and PR expectations. For substantive changes, please open an issue first so we can give direction-fit feedback before you invest implementation time.
Security issues: follow the Private Vulnerability Reporting flow in SECURITY.md. Please do not file them as public issues.
Community
Built something with Prisma Next? Tag @prisma on X. The best community builds get a shout-out and a link here.
- Discord: Talk to us in Discord in the
prisma-nextchannel - X: @prisma
- Blog: prisma.io/blog
License
Apache 2.0. See LICENSE.
Issues· 2707 open
- #30492
SQL builder: a `where` comparison on an enum column accepts any string
kind/bugUpdated Sep 29, 2026 - #30491
SQL builder: an outer query's column used inside a subquery renders without its table and binds to the inner table
kind/bugUpdated Sep 29, 2026 - #30490
A uuid(7) default in a migration's dataTransform is generated at emit time, so every self-emit changes the migration's hash
kind/bugUpdated Sep 29, 2026 - #30489
SQL builder: an update cannot set a column from a subquery or a joined table, so filling a foreign key in a data migration must be raw SQL
kind/bugUpdated Sep 29, 2026 - #30488
SQL builder: no insert whose rows come from a select, so a data migration that derives rows must be raw SQL
kind/bugUpdated Sep 29, 2026 - #30487
Memory grows without limit when $transaction([...]) batches vary in shape
bug/1-unconfirmedkind/bugUpdated Sep 29, 2026 - #11778
Migration failed with error table doesn't exist but table exists
bug/1-unconfirmedkind/bugtopic: migratetech/enginestopic: prisma migrate devUpdated Sep 29, 2026 - #11245
Migration failed to apply cleanly to the shadow database after fixing a duplicated enum `@map`'d value - Error: P3006
bug/2-confirmedkind/bugtech/enginestopic: enumUpdated Sep 29, 2026 - #25325
Migration Failure when Deleting a Column with a Default Value in Microsoft SQL Server
bug/1-unconfirmedkind/bugtopic: sql servertopic: prisma migrate devUpdated Sep 29, 2026 - #7251
Prisma Migrate - Can't add value to enum in Postgres Database
bug/2-confirmedkind/bugtech/enginestopic: enumtopic: postgresqlUpdated Sep 29, 2026