Vercel Postgres is gone. Here is what replaced it and what to do with your code.

What actually happened

Vercel Postgres launched in 2023 as part of Vercel Storage. Vercel's docs now say, verbatim: "Vercel Postgres is no longer available. If you had an existing Vercel Postgres database, we automatically moved it to Neon in December 2024. For new projects, install a Postgres integration from the Marketplace."

Nothing about the underlying engine changed in that move — Vercel Postgres already ran on Neon's infrastructure before the cutover. What changed is account ownership and the product surface: there is no "Vercel Postgres" to provision anymore, only Marketplace integrations (Neon, Supabase and others) billed through Vercel.

Sources: Vercel: Postgres on Vercel

What this means for @vercel/postgres in your code

The @vercel/postgres npm package still runs, but it is no longer actively developed and is marked deprecated. It points at the same Neon connection string your database already uses, so nothing breaks today — but new code should not start from it.

Neon publishes @neondatabase/vercel-postgres-compat as a drop-in replacement with the same sql template-tag API, or @neondatabase/serverless directly for new code that does not need the Vercel-specific wrapper.

Sources: @vercel/postgres on npm, @neondatabase/vercel-postgres-compat on npm

Your real options from here

• Do nothing: your database is already on Neon, your connection string already works, and the deprecated package still runs. This is fine short-term, but you inherit whatever Neon plan Vercel put you on and you are swapping packages eventually anyway.
• Swap the package, keep Neon: replace @vercel/postgres with @neondatabase/vercel-postgres-compat (same API) or @neondatabase/serverless, and manage the Neon project directly instead of through Vercel Storage.
• Move to a backend that bundles more than bare Postgres: if the reason you wanted Vercel Postgres was "one less thing to run myself," bare Neon still leaves auth, storage and realtime as separate problems. That is the gap Scribase is built for.

Sources: Vercel: Postgres on Vercel

Moving off it to Scribase

Your data is Postgres today regardless of which product name is on the bill, so the move is a plain dump and restore: pg_dump the schema and data from your Neon connection string, apply them to a Scribase project with scribase migrate, and point your driver at the new endpoint. Scribase's own branching, scale to zero and time travel work the same way Neon's do, because the database layer is the same idea — the difference is that auth, storage and realtime are already on the same Postgres instead of separate services you wire up yourself.

A project is $25 a month, flat, with no separate database/auth/storage bill to reconcile the way a Vercel + Neon + a third auth provider setup can end up being.

Sources: Scribase pricing