Skip to content

Latest commit

 

History

8,215 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Prisma 8

Docs | Discord | X | Blog Post | Architecture

License: Apache-2.0 npm CI


Using Prisma 7? It remains fully supported. Its source lives on the v7 branch of this repository and its docs at prisma.io/docs/orm/v7.

Prisma 8 is a release candidate. 8.0.0 final is expected in the next four to eight weeks. Until then a release candidate may include breaking changes, and every release ships with an upgrade recipe that the prisma-8 skill applies for you. The candidate is a complete implementation we stand behind: we treat bugs in it as urgent, and the risk you take on is a feature that is not built yet rather than churn. The feature scoreboard names every gap. New projects should start here. Existing Prisma 7 applications can migrate incrementally, and Prisma 7 stays on the v7 branch with bug fixes for twelve months after 8.0.0 final. Star the repo, follow @prisma on X, or read along on the Prisma blog.

Prisma 8 is a TypeScript rewrite of Prisma ORM, designed to be extensible, composable, and AI-agent friendly by default. Read the announcement or start with the docs.

Prerequisites

  • Node.js 24 or newer
  • A package manager (npm, pnpm, or yarn)

Getting started

1. Scaffold a new project

The interactive scaffolder picks an app template (Next.js, Hono, Nuxt, Astro, NestJS, SvelteKit, TanStack Start, or Elysia) and wires Prisma 8 in with your chosen database (PostgreSQL or MongoDB):

npm create prisma

You finish with a runnable app, a starter contract, and the agent skills already installed. See the create-prisma reference for every template and flag, or follow the PostgreSQL and MongoDB quickstarts.

2. Or, add Prisma 8 to an existing project

Run this from your repo root:

npx prisma orm init

orm init writes prisma.config.ts, scaffolds a starter contract and db.ts under src/prisma/, installs the runtime, and emits the contract. It does not touch your framework or build setup. Then install the agent skills:

npx prisma skills sync

See the orm init and skills CLI references, or the guides for adding Prisma 8 to an existing PostgreSQL or MongoDB app.

3. Use your AI agent for everything Prisma 8

Both installers leave a top-level prisma-next.md primer at your project root for any agent to read first, and install one SKILL.md per workflow into the directories agent runtimes read:

  • .claude/skills/<skill-name>/SKILL.md — Claude Code
  • .cursor/skills/<skill-name>/SKILL.md — Cursor
  • .agents/skills/<skill-name>/SKILL.md — universal location for Copilot Agent and other runtimes
  • .devin/skills/<skill-name>/SKILL.md — Devin

Skills ship inside the Prisma packages your project installs, so they always describe the version in use. Your editor's AI assistant auto-loads the right skill when your prompt matches.

Just describe what you want. For example:

"Add a posts model with a relation to users, 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 8 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.

Extensions already shipping:

See Using extensions for how to install and register one. Want to ship your own? The call for extension authors walks through the SPI, the layers your extension can hook into, and how the team features new extensions.

Supported databases

  • PostgreSQL — the primary target, first-class support
  • MongoDB — first-class support
  • SQLite — planned next, a proof of concept today

MySQL follows after SQLite. See the feature scoreboard for what each database supports today.

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 8? Tag @prisma on X. The best community builds get a shout-out and a link here.

License

Apache 2.0. See LICENSE.

About

Next-generation ORM for Node.js & TypeScript | PostgreSQL, MySQL, MariaDB, SQL Server, SQLite, MongoDB and CockroachDB

Topics

Resources

Code of conduct

Contributing

Security policy

Stars

47.6k stars

Watchers

329 watching

Forks

Releases

Used by

Contributors

Languages