feat(docs): add Prisma Postgres vs Neon comparison and migration guide#7879
feat(docs): add Prisma Postgres vs Neon comparison and migration guide#7879aidankmcalister wants to merge 1 commit intomainfrom
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
WalkthroughDocumentation guide for migrating from Neon to Prisma Postgres restructured into a clearly numbered four-step process with explicit commands for exporting, importing, and updating applications. Page metadata updated for clarity. ChangesMigration Guide Restructuring
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~5 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Comment |
🍈 Lychee Link Check Report7 links: ✅ All links are working!Full Statistics Table
|
|
The latest updates on your projects. Learn more about Argos notifications ↗︎
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
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/switch-to-prisma-postgres/from-neon.mdx (1)
223-225:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winMake the
DATABASE_URLexample unambiguously non-literal.Line 224 reads like a complete value and is easy to paste unchanged. Prefer an explicit placeholder that tells readers to reuse the exact connection string from Step 1.
Suggested doc tweak
-DATABASE_URL="postgres://USER:PASSWORD@db.prisma.io:5432/?sslmode=require" +DATABASE_URL="<DIRECT_CONNECTION_STRING_FROM_STEP_1>"🤖 Prompt for 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. In `@apps/docs/content/docs/guides/switch-to-prisma-postgres/from-neon.mdx` around lines 223 - 225, Update the .env example so the DATABASE_URL value is clearly a non-literal placeholder rather than a ready-to-paste connection string: replace the current example value in the `.env` code block (the DATABASE_URL line) with an explicit placeholder form (e.g. using <USER>, <PASSWORD>, <HOST>, <DBNAME> or a note to reuse the exact connection string from Step 1) and add a short clarifying comment in the same snippet telling readers to substitute their real credentials or reuse the connection string obtained in Step 1.
🤖 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.
Inline comments:
In `@apps/docs/content/docs/guides/switch-to-prisma-postgres/from-neon.mdx`:
- Around line 23-25: Update the two table cells that list Neon details: change
the "Postgres version" cell (the table row with "**Postgres version**") from
"16, 17" to "14, 15, 16, 17, 18 (preview)" and change the "Available regions"
cell (the row with "**Available regions**") from "11 regions (8 AWS, 3 Azure)"
to "8 AWS regions" and list the regions: "us-east-1, us-east-2, us-west-2,
eu-central-1, eu-west-2, ap-southeast-1, ap-southeast-2, sa-east-1". Ensure you
only modify those two cells and leave other content (including lines 84–90)
unchanged.
---
Outside diff comments:
In `@apps/docs/content/docs/guides/switch-to-prisma-postgres/from-neon.mdx`:
- Around line 223-225: Update the .env example so the DATABASE_URL value is
clearly a non-literal placeholder rather than a ready-to-paste connection
string: replace the current example value in the `.env` code block (the
DATABASE_URL line) with an explicit placeholder form (e.g. using <USER>,
<PASSWORD>, <HOST>, <DBNAME> or a note to reuse the exact connection string from
Step 1) and add a short clarifying comment in the same snippet telling readers
to substitute their real credentials or reuse the connection string obtained in
Step 1.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 904f0828-4ad2-47fa-b3fe-597a15681e2c
📒 Files selected for processing (1)
apps/docs/content/docs/guides/switch-to-prisma-postgres/from-neon.mdx
| | **Postgres version** | 17 | 16, 17 | | ||
| | **Available regions** | 6 regions | 11 regions (8 AWS, 3 Azure) | | ||
|
|
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
`Please verify current official values for Prisma Postgres vs Neon on:
- supported Postgres versions,
- available regions,
- pooled/direct connection limits by plan,
- free-tier quotas,
- autosuspend defaults and disablement by plan.
Use only official Prisma and Neon docs/pricing pages.`
💡 Result:
Prisma Postgres vs Neon: Current official values (as of 2026-05-07). 1) Supported Postgres versions: Prisma Postgres: PostgreSQL v17.[1] Neon: Postgres 14, 15, 16, 17, 18 (preview).[2][3] 2) Available regions: Prisma Postgres: us-west-1 (San Francisco), us-east-1 (North Virginia), eu-west-3 (Paris), eu-central-1 (Frankfurt), ap-northeast-1 (Tokyo), ap-southeast-1 (Singapore).[4] Neon: AWS regions: us-east-1 (N. Virginia), us-east-2 (Ohio), us-west-2 (Oregon), eu-central-1 (Frankfurt), eu-west-2 (London), ap-southeast-1 (Singapore), ap-southeast-2 (Sydney), sa-east-1 (São Paulo). Azure regions deprecated as of Apr 2026.[5] 3) Pooled/direct connection limits by plan: Prisma Postgres (concurrent limits; idle pooled closed after 60min; 5 direct reserved for platform): Free/Starter: Pooled 50, Direct 10[6] Pro: Pooled 250, Direct 50[6] Business: Pooled 500, Direct 100[6] (Note: Some pages show lower pooled for Free like 10, but detailed docs confirm 50.[6][7]) Neon: PgBouncer pooled: max_client_conn 10,000; default_pool_size 90% of max_connections (varies by compute size, e.g. 0.25GB:5, 1GB:104, 2GB:20? snippet partial); max_connections varies by compute size (1000 for pooled?). No per-plan limits specified; applies to all plans.[8] 4) Free-tier quotas: Prisma Postgres (Free plan): First 60,000 operations free, then $0.0080 per 1,000 ops. No storage mentioned as free limit (usage-based).[7] Neon (Free plan, per project): 100 CU-hours compute, 0.5 GB storage, 5 GB egress, 100 projects, 10 branches/project. Compute suspends on limits.[9][10] 5) Autosuspend defaults and disablement by plan: Prisma Postgres: No autosuspend/scale-to-zero mentioned in docs.[1] Neon (scale-to-zero after inactivity): Free: After 5 min (not configurable, always on).[9] Launch: After 5 min, can be disabled.[9] Scale: Configurable (1 min to always on).[9]
Citations:
- 1: https://www.prisma.io/docs/postgres
- 2: https://www.neon.tech/docs/postgresql/postgres-version-policy
- 3: https://neon.tech/docs/reference/compatibility/
- 4: https://prisma.io/docs/postgres/more/faq
- 5: https://neon.tech/docs/introduction/regions/
- 6: https://www.prisma.io/docs/postgres/database/connection-pooling
- 7: https://www.prisma.io/pricing
- 8: https://www.neon.tech/docs/connect/connection-pooling
- 9: https://neon.com/2024-plan-updates
- 10: http://neon.tech/pricing
🏁 Script executed:
head -90 apps/docs/content/docs/guides/switch-to-prisma-postgres/from-neon.mdx | tail -70 | cat -nRepository: prisma/web
Length of output: 5721
🏁 Script executed:
sed -n '80,95p' apps/docs/content/docs/guides/switch-to-prisma-postgres/from-neon.mdx | cat -nRepository: prisma/web
Length of output: 1841
Update Neon version and region claims to reflect current facts.
Lines 23 and 25 contain outdated information:
- Line 23 (Postgres versions): Neon supports PostgreSQL 14, 15, 16, 17, and 18 (preview), not just "16, 17". Update the table to reflect this fuller support.
- Line 25 (Available regions): Neon's Azure regions were deprecated as of April 2026. Update from "11 regions (8 AWS, 3 Azure)" to "8 AWS regions" (us-east-1, us-east-2, us-west-2, eu-central-1, eu-west-2, ap-southeast-1, ap-southeast-2, sa-east-1).
Lines 84–90 are accurate and require no changes.
🤖 Prompt for 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.
In `@apps/docs/content/docs/guides/switch-to-prisma-postgres/from-neon.mdx` around
lines 23 - 25, Update the two table cells that list Neon details: change the
"Postgres version" cell (the table row with "**Postgres version**") from "16,
17" to "14, 15, 16, 17, 18 (preview)" and change the "Available regions" cell
(the row with "**Available regions**") from "11 regions (8 AWS, 3 Azure)" to "8
AWS regions" and list the regions: "us-east-1, us-east-2, us-west-2,
eu-central-1, eu-west-2, ap-southeast-1, ap-southeast-2, sa-east-1". Ensure you
only modify those two cells and leave other content (including lines 84–90)
unchanged.
1 participant
Linear: DR-8353
Summary by CodeRabbit
pg_dump, and data import with explicit commands and connection string formats.