# Release status (/docs/prisma-orm/release-status)

> For the complete Prisma documentation index, see [llms.txt](https://www.prisma.io/docs/llms.txt). A markdown version of any docs page is available by appending `.md` to its URL.

Where Prisma ORM 8 stands today, what you get when you install it, and how to stay on Prisma ORM 7.

Location: Prisma ORM > Release status

Prisma ORM 8 is a **release candidate**. You can install it and build with it today. Until the final release, some details of the API may still change, so code you write now may need small edits later. Each release candidate fixes bugs found in the previous one. What Prisma ORM 8 changes, and why, is on the [Prisma ORM overview](https://www.prisma.io/docs/orm).

It needs Node.js 22.18 or newer (on the 24 line, 24.11 or newer; 24.0 to 24.10 do not work) and TypeScript 5.9 or newer.

Before you decide, read [what is not available yet](https://www.prisma.io/docs/orm/coming-from-prisma-orm-7#not-available-yet). Today that includes `$extends`, filtering inside JSON columns, atomic `increment`, most nested writes, transaction isolation levels, and the `P2002`-style error codes.

## When the final release is expected [#when-the-final-release-is-expected]

General availability is expected in October 2026.

## Prisma ORM 7 is supported for 18 months after the final release [#prisma-orm-7-is-supported-for-18-months-after-the-final-release]

Prisma ORM 7 keeps receiving bug fixes and security updates for 18 months from the day Prisma ORM 8 reaches general availability. Its documentation stays at [/orm/v7](https://www.prisma.io/docs/orm/v7).

## Prisma ORM 6 receives security patches until 19 November 2026 [#prisma-orm-6-receives-security-patches-until-19-november-2026]

Prisma ORM 6 receives security patches, but no other updates, for 12 months after the release of Prisma ORM 7. That period ends on 19 November 2026. Its documentation stays at [/orm/v6](https://www.prisma.io/docs/orm/v6).

## What you get when you install today [#what-you-get-when-you-install-today]

Prisma ORM 8 is two packages: the command-line tool, and a library your app imports. There is one library per database; for PostgreSQL it is `@prisma/orm-postgres`.

  

#### bun

```bash
bun add --dev prisma
bun add @prisma/orm-postgres
```

#### pnpm

```bash
pnpm add --save-dev prisma
pnpm add @prisma/orm-postgres
```

#### yarn

```bash
yarn add --dev prisma
yarn add @prisma/orm-postgres
```

#### npm

```bash
npm install --save-dev prisma
npm install @prisma/orm-postgres
```

For MongoDB the library is `@prisma/orm-mongo`, and for SQLite it is `@prisma/orm-sqlite`. MySQL is not supported yet.

The two packages have different version numbers, and that is normal: they are released separately, and the command-line tool gets more frequent releases. Install both at `latest`; any two `latest` versions work together, and you do not pair the numbers yourself.

| Package                              | Version today |
| ------------------------------------ | ------------- |
| `prisma` (the command-line tool)     | `8.0.0-rc.13` |
| `@prisma/orm-postgres` (the library) | `8.0.0-rc.9`  |

Versions were checked on 11 September 2026; run `npm view prisma dist-tags` for today's.

`@prisma/client`, the library that Prisma ORM 7 apps import, stays at `7.10.0`. It belongs to Prisma ORM 7 and is not part of Prisma ORM 8.

> [!WARNING]
> If you have a Prisma ORM 7 project
> 
> `npm install prisma` and `npx prisma` now give you the Prisma ORM 8 command-line tool. It does not read `schema.prisma` and has no `generate`, `migrate dev`, or `db push` commands. If your project is on Prisma ORM 7, run `npm install --save-dev prisma@7` now, and lock the version in `package.json` as shown below. If version 8 is already installed, that same command downgrades it. To see what you have now, run `npm ls prisma @prisma/client`.

## How to stay on Prisma ORM 7 [#how-to-stay-on-prisma-orm-7]

Lock both packages to version 7 in `package.json`:

```json title="package.json"
{
  "devDependencies": {
    "prisma": "^7"
  },
  "dependencies": {
    "@prisma/client": "^7"
  }
}
```

Anywhere you run the tool without a locked version, for example in CI or in a one-off command, write `npx prisma@7` instead of `npx prisma`.

The Prisma ORM 7 documentation is at [/orm/v7](https://www.prisma.io/docs/orm/v7), its setup guides at [/v7/getting-started](https://www.prisma.io/docs/v7/getting-started), and its command reference at [/cli/v7](https://www.prisma.io/docs/cli/v7).

## Next steps [#next-steps]

* To move an existing Prisma ORM 7 app, follow [Migrate from Prisma ORM 7 to 8](https://www.prisma.io/docs/guides/upgrade-prisma-orm/postgresql). It runs both versions side by side and moves one part of the app at a time.
* To see what each Prisma ORM 7 command and query is called now, and what is not available yet, see [Coming from Prisma ORM 7](https://www.prisma.io/docs/orm/coming-from-prisma-orm-7).

## Related pages

- [`create-prisma`](https://www.prisma.io/docs/prisma-orm/create-prisma): Scaffold a new Prisma ORM app with create-prisma, with Prisma Composer, Prisma Postgres, and a deploy path built in.