feat(docs): add Next.js on Vercel guide for Prisma Postgres

[aidankmcalister]

Linear: DR-8359

Summary by CodeRabbit

• Documentation
  • Updated Postgres on Vercel guide with clearer Marketplace integration and automatic DATABASE_URL/connection pooling behavior.
  • Rewrote serverless-scaling section to explain avoiding separate connection pooling and local/preview/production behavior.
  • Replaced generic "Usage" with a "Using with Next.js" walkthrough, including guidance to read DATABASE_URL and run Prisma Client generation during deploy.
  • Moved and refreshed Prisma billing/pricing details.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
blog	Ready	Preview, Comment	May 8, 2026 3:14pm
docs	Ready	Preview, Comment	May 8, 2026 3:14pm
eclipse	Ready	Preview, Comment	May 8, 2026 3:14pm
site	Ready	Preview, Comment	May 8, 2026 3:14pm

[github-actions]

🍈 Lychee Link Check Report

13 links: ✅ 6 OK | 🚫 0 errors | 🔀 3 redirects | 👻 4 excluded

✅ All links are working!

---

Full Statistics Table

Status	Count
✅ Successful	6
🔀 Redirected	3
👻 Excluded	4
🚫 Errors	0
⛔ Unsupported	0
⏳ Timeouts	0
❓ Unknown	0

[argos-ci]

The latest updates on your projects. Learn more about Argos notifications ↗︎

Build	Status	Details	Updated (UTC)
default (Inspect)	✅ No changes detected	-	May 8, 2026, 3:22 PM

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 6083b8fc-792e-44c2-b1c2-3bd8e0074b15

📥 Commits

Reviewing files that changed from the base of the PR and between 625b2d5 and cdafc74.

📒 Files selected for processing (1)

• apps/docs/content/docs/guides/postgres/vercel.mdx

✅ Files skipped from review due to trivial changes (1)

• apps/docs/content/docs/guides/postgres/vercel.mdx

---

Walkthrough

The Vercel Postgres guide is reframed around Marketplace integration with emphasis on automatic DATABASE_URL provisioning and built-in connection pooling. Setup instructions shift from generic patterns to actionable step-by-step guidance for database creation, project connection, and local development. Prisma Client generation is clarified as a per-deploy requirement with updated configuration examples.

Changes

Vercel Postgres Guide Refresh

Layer / File(s)	Summary
Documentation Metadata apps/docs/content/docs/guides/postgres/vercel.mdx	Frontmatter updated (description, metaTitle, metaDescription) to emphasize Marketplace integration and connection pooling focus.
Introduction & Value Proposition apps/docs/content/docs/guides/postgres/vercel.mdx	Opening section rewritten to explain automatic DATABASE_URL from Marketplace, clarify compatibility with any ORM/library, and expand "Why Prisma Postgres works well on Vercel" section covering serverless scaling and default pooling.
Setup Flow apps/docs/content/docs/guides/postgres/vercel.mdx	Usage section replaced with step-by-step instructions: install dependencies, create database via Marketplace, connect to Vercel project, run Prisma Studio locally.
Next.js Configuration apps/docs/content/docs/guides/postgres/vercel.mdx	Framework guidance updated to reference the Next.js framework guide and emphasize configuring prisma.config.ts to read from DATABASE_URL.
Deployment & Client Generation apps/docs/content/docs/guides/postgres/vercel.mdx	Prisma Client guidance changed to "Generate Prisma Client on every deploy" with updated vercel.json postinstall snippet format.
Supporting Content apps/docs/content/docs/guides/postgres/vercel.mdx	Templates section lead-in updated for Marketplace phrasing; Billing and pricing section repositioned and refined with minor wording updates.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'feat(docs): add Next.js on Vercel guide for Prisma Postgres' accurately reflects the core change—updating documentation to emphasize Vercel Marketplace integration and adding Next.js-specific setup guidance for Prisma Postgres.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

Warning

Review ran into problems

🔥 Problems

Git: Failed to clone repository. Please run the @coderabbitai full review command to re-trigger a full review. If the issue persists, set path_filters to include or exclude specific files.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

apps/docs/content/docs/guides/postgres/vercel.mdx (1)

17-59: ⚠️ Potential issue | 🟠 Major | ⚡ Quick win

Add explicit step to pull environment variables before running Prisma Studio locally

The documentation implies DATABASE_URL is available locally but doesn't explain how users get it there. Vercel Marketplace integrations automatically set env vars in the project, but they don't automatically populate local environments—users must explicitly run vercel env pull to sync them into .env.local before commands like prisma studio can access DATABASE_URL. Without this step, first-time users will encounter failures when trying to run local tooling.

Suggested documentation update

 ### View and edit data in Prisma Studio

-To view and edit data in your Prisma Postgres instance, run Prisma Studio locally where your `DATABASE_URL` is set:
+To view and edit data in your Prisma Postgres instance, first pull your environment variables locally, then run Prisma Studio:
+
+```npm
+vercel env pull .env.local
+```
 
 ```npm
 npx prisma studio

</details>

<details>
<summary>🤖 Prompt for AI Agents</summary>

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @apps/docs/content/docs/guides/postgres/vercel.mdx around lines 17 - 59, The
docs mention running Prisma Studio but don't tell users how to get DATABASE_URL
locally; add an explicit step instructing users to run the Vercel CLI
environment pull (e.g., "vercel env pull .env.local") to sync environment
variables into their local file (such as .env.local) before running "npx prisma
studio" so Prisma Studio can read DATABASE_URL; reference DATABASE_URL and the
Prisma Studio step in the "View and edit data in Prisma Studio" section and
include the exact vercel env pull command and target file.

</details>

</blockquote></details>

</blockquote></details>

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Outside diff comments:
In `@apps/docs/content/docs/guides/postgres/vercel.mdx`:
- Around line 17-59: The docs mention running Prisma Studio but don't tell users
how to get DATABASE_URL locally; add an explicit step instructing users to run
the Vercel CLI environment pull (e.g., "vercel env pull .env.local") to sync
environment variables into their local file (such as .env.local) before running
"npx prisma studio" so Prisma Studio can read DATABASE_URL; reference
DATABASE_URL and the Prisma Studio step in the "View and edit data in Prisma
Studio" section and include the exact vercel env pull command and target file.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: eab908c3-c912-45d8-bbec-0c3bcf626844

📥 Commits

Reviewing files that changed from the base of the PR and between 9234919 and 625b2d5.

📒 Files selected for processing (1)

• apps/docs/content/docs/guides/postgres/vercel.mdx