Skip to content

blog(prisma-vs-vercel): list the four variables the Prisma Postgres integration sets on Vercel #8707

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
gregory-boch-prisma merged 1 commit into from
Nov 2, 2026
Merged

blog(prisma-vs-vercel): list the four variables the Prisma Postgres integration sets on Vercel #8707

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions apps/blog/content/blog/prisma-vs-vercel/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
title: "Prisma vs Vercel: where should you build your next TypeScript app?"
slug: "prisma-vs-vercel"
date: "2026-09-16"
updatedAt: "2026-10-27"
updatedAt: "2026-11-03"
authors:
- "Shane Neubauer"
metaTitle: "Prisma vs Vercel for TypeScript apps: which platform?"
Expand Down Expand Up @@ -137,7 +137,7 @@ A preview uses whatever `DATABASE_URL` it was given, so a preview that inherits

For testing against production-shaped data, this is the more convenient setup, because there is nothing to seed and nothing to point.

The [Prisma Postgres listing](https://vercel.com/marketplace/prisma) sets a single `DATABASE_URL` for the project, and you scope previews away from it with Vercel's per-environment variables.
The [Prisma Postgres integration](https://vercel.com/marketplace/prisma) sets `DATABASE_URL`, `POSTGRES_URL`, `PRISMA_DATABASE_URL`, and `DATABASE_URL_POOLED` for the project, and you scope previews away from them with Vercel's per-environment variables. If a project has no `DATABASE_URL_POOLED`, its database was created before the integration started setting it on 2026-10-29; the [Vercel guide](https://www.prisma.io/docs/guides/postgres/vercel#use-the-pooled-connection-string-for-application-traffic) shows how to add it.

Schema changes travel the same way on both platforms: as migration files in Git that a deploy applies. Prisma ORM 8 helps when two branches change the schema at the same time:

Expand Down Expand Up @@ -214,3 +214,7 @@ Yes. The Prisma Postgres Marketplace integration provisions a database and sets
**Pick Prisma** if your backend is several TypeScript services that share Postgres and you can live with Bun and one region. The compiler then checks the wiring between those services, and the deploy creates it. Start with the [Composer getting-started guide](https://www.prisma.io/docs/composer/getting-started), which runs two services locally without an account.

**Stay on Vercel** if your app leans on Vercel's Next.js features, needs Node.js, WebSockets, or long requests, or if you want previews that arrive with production data. The [Vercel guide](https://www.prisma.io/docs/guides/postgres/vercel) brings Prisma ORM 8 and Prisma Postgres there.

## Update history

- 2026-11-03: "Previews and their databases" now says the Prisma Postgres integration sets `DATABASE_URL`, `POSTGRES_URL`, `PRISMA_DATABASE_URL`, and `DATABASE_URL_POOLED` instead of only `DATABASE_URL`, and that a project with no `DATABASE_URL_POOLED` has a database created before 2026-10-29. No other facts changed.
Loading