Vercel Postgres
Postgres bundled into Vercel, now powered by Neon under the hood.
VISIT VERCEL POSTGRESKey takeaway: Technically there is nothing here that Neon does not give you, because it is Neon underneath. What you are buying is one dashboard, one invoice, and environment variables wired across preview and production without thinking about it. Worth it if your team already pays the Vercel premium for the same reasons; not worth it once the database line item gets scrutinised.
Quick facts
- CategoryPostgres
- EnginePostgres
- PricingFreemium
- LicenseProprietary
- Created2023
- GitHub starsclosed
- PostgresCompatible
- Edge-readyYes
What it is
Vercel Postgres is Vercel's storage product, since 2024 powered by Neon under the hood. Tight integration with Vercel projects, automatic env var wiring, edge-friendly access via the @vercel/postgres SDK. Pricing is meaningfully more expensive than Neon direct.
Best for
- Vercel projects that want storage in the same dashboard
- Teams that prioritise zero-config integration over price
When not to pick it
Skip Vercel Postgres if cost matters, going direct to Neon is meaningfully cheaper for the same underlying database.
My take
Convenient but expensive. For teams that already pay the Vercel premium and want one bill, fine. For cost-sensitive projects, use Neon directly.
What the integration actually buys you
The honest case for Vercel Postgres is operational, not technical. Connection strings land in your project as environment variables across every environment automatically, preview deployments get the right credentials without a secrets-management step, and the SDK works inside Vercel's runtimes without you thinking about drivers. There is one vendor to call, one bill to approve, and no second account for someone to forget to offboard when they leave. On a small team shipping quickly, those are real hours. The engineering underneath is Neon, so the branching, the scale-to-zero behaviour, and the Postgres compatibility are the same product you would get direct. Nobody should choose this for a capability reason, because there is not one. Choose it when your team's binding constraint is attention rather than budget, which for a lot of early-stage teams is the accurate description.
The wrapper premium, and an unusually easy exit
The pricing sits meaningfully above going direct to Neon for the same underlying database, and that gap is the entire decision. On a small project it is a rounding error against your Vercel bill. On anything carrying real traffic it becomes a line item someone eventually asks about, and the answer "we pay extra for convenience" gets less comfortable each quarter. The good news is that this is the least painful migration in the category: same engine, same wire protocol, same Postgres. Moving to Neon direct is largely provisioning there and changing a connection string, with your queries, ORM, and migrations untouched. So the sensible posture is to start here if it saves setup time, keep the data-access code free of anything Vercel-specific, and move the day the number stops looking like a rounding error.
Frequently asked questions
Is Vercel Postgres the same as Neon?
It is Neon underneath. The branching, the compute and storage separation, and the Postgres compatibility are the same engine. What differs is packaging: Vercel handles provisioning, environment variables, and billing inside your existing project, and charges meaningfully more than buying the same database from Neon directly.
Is Vercel Postgres worth the extra cost?
Early on, for a small team that values one dashboard and zero-config environment wiring, yes. Once the database carries real traffic, the gap against Neon direct is hard to justify. Because it is the same engine, switching later is mostly a connection-string change, so starting here costs you very little optionality.
Does Vercel Postgres work at the edge?
Yes. The SDK talks over HTTP rather than raw TCP, so it works inside edge runtimes where conventional Postgres drivers cannot open a socket. That is the same capability Neon's serverless driver provides, which is unsurprising given what is running underneath it.
Links
Compare Vercel Postgres side-by-side
Similar tools you should also consider
If Vercel Postgres is your pick, the next conversation is short
The 30-min call is where your database choice becomes a real architecture, a migration plan if you are switching, and a price range you can take to your stakeholders. Describe your stack, your scale, your data shape. I tell you whether Vercel Postgres is genuinely your fit.