PatchVault › Errors › @vercel/kv & @vercel/postgres → Upstash + Neon

Vercel Postgres is no longer available. If you had an existing Vercel Postgres database, we automatically moved it to Neon in December 2024.

You need a maintained replacement for @vercel/postgres. Neon's transition guide says the SDK still works but is no longer actively maintained by Vercel, and recommends @neondatabase/serverless (or @neondatabase/vercel-postgres-compat as a drop-in).

Check your code free (runs in your browser)

The box is pre-filled with a sample that triggers this error. Paste your own file to check it. Nothing leaves this page.

Or scan your whole repo locally (free, stdlib Python, read-only):

python3 <(curl -fsSL https://patchvault-81y.pages.dev/starters/vercel-kv-scan.py) .
Get the @vercel/kv & @vercel/postgres → Upstash + Neon auto-fixer: $9 one-time

Why it happens

Vercel transitioned all Vercel Postgres stores to Neon's native integration (Q4 2024 to Q1 2025). New Postgres databases come from Marketplace providers such as Neon, Prisma Postgres, Supabase and AWS Aurora Postgres.

Manual fix

npm uninstall @vercel/postgres
npm install @neondatabase/serverless

// before
import { sql } from '@vercel/postgres'
const { rows } = await sql`SELECT * FROM users WHERE id = ${id}`
// after
import { neon } from '@neondatabase/serverless'
const sql = neon(process.env.DATABASE_URL!)
const rows = await sql`SELECT * FROM users WHERE id = ${id}`

Verify

Re-run your install/build and re-scan the file above. The finding should be gone. The paid fixer applies the same change across a repo: --dry-run shows the diff, --apply keeps a .bak of each file, and --rollback restores them.

Sources

Related errors

Full guide and free terminal scanner: @vercel/kv & @vercel/postgres → Upstash + Neon. Last checked 2026-10-31.