# Next.js (/docs/guides/next/frameworks/nextjs)

> 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.

Set up Prisma Next in a Next.js app with create-prisma, from scaffold to rendered data, and deploy it to Prisma Compute.

Location: Guides > Next > Frameworks > Next.js

## Introduction [#introduction]

This guide shows you how to use Prisma Next in a Next.js app. You scaffold a project where a server component queries your database, initialize the schema, see your data render, and deploy the app to [Prisma Compute](https://www.prisma.io/docs/compute).

Every command below was run end to end against a live [Prisma Postgres](https://www.prisma.io/docs/postgres) database.

## Prerequisites [#prerequisites]

* [Node.js](https://nodejs.org) 24 or later
* A PostgreSQL connection string, or nothing at all: the scaffold can create the database for you

## Use with your agent [#use-with-your-agent]

Prefer to delegate this guide? Copy the prompt and hand it to your coding agent:

```text
Create a new Next.js app with Prisma Next, seed it, and deploy it to Prisma Compute.

1. Scaffold: `npx create-prisma@next create my-app --template next --provider postgres --prisma-postgres --yes` (or pass `--database-url "<url>"` instead of `--prisma-postgres` if I give you a connection string).
2. In `my-app`, run `npm run db:init`, then `npm run db:seed`. If seeding fails with `Cannot read properties of undefined (reading 'where')`, change `db.orm.User` to `db.orm.public.User` in `src/prisma/seed.ts` and `src/prisma/users.ts`, then rerun.
3. Start `npm run dev` in the background, wait until it reports ready, verify http://localhost:3000 renders the seeded users, then stop the dev server.
4. Set `output: "standalone"` in `next.config.ts`; Prisma Compute deploys the standalone server that `next build` emits.
5. Deploy: check `npx @prisma/cli@latest auth whoami`; if I am not signed in, stop and ask me to run `npx @prisma/cli@latest auth login`. Then run `npx @prisma/cli@latest app deploy --create-project my-app --env .env` and verify the live URL renders the seeded users.

Use the installed Prisma Next skills.
```

## 1. Scaffold and enter the project [#1-scaffold-and-enter-the-project]

  

#### bun

```bash
bunx create-prisma@next create my-app --template next --provider postgres
cd my-app
```

#### pnpm

```bash
pnpm dlx create-prisma@next create my-app --template next --provider postgres
cd my-app
```

#### yarn

```bash
yarn dlx create-prisma@next create my-app --template next --provider postgres
cd my-app
```

#### npm

```bash
npx create-prisma@next create my-app --template next --provider postgres
cd my-app
```

Pick Prisma Postgres at the database prompt to have a database created for you, or paste your own `DATABASE_URL`. The scaffold writes your connection string to `.env`, generates the Next.js app with Prisma Next wired in, installs dependencies, and emits the contract your queries are type-checked against.

## 2. Initialize and seed the database [#2-initialize-and-seed-the-database]

  

#### bun

```bash
bun run db:init
bun run db:seed
```

#### pnpm

```bash
pnpm run db:init
pnpm run db:seed
```

#### yarn

```bash
yarn db:init
yarn db:seed
```

#### npm

```bash
npm run db:init
npm run db:seed
```

```text no-copy
"summary": "Applied 5 operation(s) across 1 space(s), database signed"
Seeded 3 users.
```

`db:init` applies your schema (`src/prisma/contract.prisma`) to the database and signs it; the seed gives the first page something to show.

> [!NOTE]
> Seeing `Cannot read properties of undefined (reading 'where')`? The current `next` template still generates the older unqualified query form. Update `db.orm.User` to `db.orm.public.User` in `src/prisma/seed.ts` and `src/prisma/users.ts`, then rerun `db:seed`.

## 3. Run and verify [#3-run-and-verify]

  

#### bun

```bash
bun run dev
```

#### pnpm

```bash
pnpm run dev
```

#### yarn

```bash
yarn dev
```

#### npm

```bash
npm run dev
```

Open [http://localhost:3000](http://localhost:3000) (set `PORT` to change it). The page lists the seeded users, rendered by a server component that calls Prisma Next directly.

## 4. Deploy to Prisma Compute [#4-deploy-to-prisma-compute]

Next.js is supported on [Prisma Compute](https://www.prisma.io/docs/compute). Compute runs the standalone server that `next build` emits, and the template does not enable that output mode yet, so set it in `next.config.ts` first:

```ts title="next.config.ts"
import type { NextConfig } from "next";

const nextConfig: NextConfig = {
  output: "standalone",
};

export default nextConfig;
```

> [!WARNING]
> Without `output: "standalone"` the deploy command still completes, but the uploaded build contains no server to start and the live URL returns a 504. With it, the build drops from roughly 170 MB to 14 MB and boots normally.

Sign in once (it opens a browser):

  

#### bun

```bash
bunx @prisma/cli@latest auth login
```

#### pnpm

```bash
pnpm dlx @prisma/cli@latest auth login
```

#### yarn

```bash
yarn dlx @prisma/cli@latest auth login
```

#### npm

```bash
npx @prisma/cli@latest auth login
```

Then deploy from the project directory. The `--env .env` flag passes your `DATABASE_URL` to the deployment, so the live app talks to the same database:

  

#### bun

```bash
bunx @prisma/cli@latest app deploy --env .env
```

#### pnpm

```bash
pnpm dlx @prisma/cli@latest app deploy --env .env
```

#### yarn

```bash
yarn dlx @prisma/cli@latest app deploy --env .env
```

#### npm

```bash
npx @prisma/cli@latest app deploy --env .env
```

```text no-copy
First deploy of "my-app" -- promoting to production.
Building locally...
  Built      14.4 MB
Uploading...
Deploying...
Live in 15.5s
https://<your-app>.ewr.prisma.build
```

Open the live URL: the page renders the same seeded users as your local dev server. The first deploy asks you to pick or create a project (pass `--create-project my-app` to skip the prompt), pins the directory to it in a gitignored `.prisma/local.json`, and promotes to production. Later production deploys from the same directory need `--prod`; for previews per Git branch and deploy-on-push, see [Deploy your first app](https://www.prisma.io/docs/prisma-compute/deploy).

## Where things live [#where-things-live]

* `src/app/page.tsx`: a server component that queries users and renders them
* `src/prisma/db.ts`: the Prisma Next client your components import
* `src/prisma/contract.prisma`: your schema

Model access is namespace-qualified on PostgreSQL: `db.orm.public.User`. The [Prisma Next overview](https://www.prisma.io/docs/orm/next) covers the contract-first model behind it.

## Next steps [#next-steps]

* Change the schema in `src/prisma/contract.prisma`, then run `npm run contract:emit` and `npm run db:update`.
* [Learn the fundamentals](https://www.prisma.io/docs/orm/next/fundamentals/reading-data): filtering, sorting, pagination, and writes.
* [Read the Prisma Next overview](https://www.prisma.io/docs/orm/next) for the concepts behind contracts and typed queries.

## Related pages

- [`Astro`](https://www.prisma.io/docs/guides/next/frameworks/astro): Set up Prisma Next in an Astro app with create-prisma, from scaffold to rendered data, and deploy it to Prisma Compute.
- [`Elysia`](https://www.prisma.io/docs/guides/next/frameworks/elysia): Build an Elysia API on Prisma Next with the elysia template and deploy it to Prisma Compute.
- [`Hono`](https://www.prisma.io/docs/guides/next/frameworks/hono): Build a Hono API on Prisma Next with the hono template, add your own routes, and deploy it to Prisma Compute.
- [`NestJS`](https://www.prisma.io/docs/guides/next/frameworks/nestjs): Set up Prisma Next in a NestJS app with create-prisma, from scaffold to seeded API to a live deploy on Prisma Compute.
- [`Nuxt`](https://www.prisma.io/docs/guides/next/frameworks/nuxt): Set up Prisma Next in a Nuxt app with create-prisma, from scaffold to rendered data, and deploy it to Prisma Compute.