I Just Found Out Vercel Has Postgres

Note: this is from 2023. My database setup has changed since then, but this was a fun moment, so I'm keeping the writeup for the archive.

Hey everyone, Romel here. I was today years old when I found out that Vercel has Postgres. I already deploy basically everything to Vercel, so the idea of having the database living in the same place I push my code to is very tempting, and I wanted to see how it plays with Prisma.

The appeal is mostly about removing moving parts. Right now my apps are deployed on Vercel, but the database is somewhere else entirely, which means another dashboard, another set of credentials, another thing to think about. If the database can sit right next to the app, that's one less context switch when I'm trying to ship something in a single evening.

Wiring it up to Prisma was about as easy as I hoped. Point the connection string at the Vercel database, run the migration, and the same schema-first workflow I already use just works. No new ORM to learn, no rewriting my data layer. That's exactly the kind of low-friction swap I look for on a side project.

The one thing I'm keeping an eye on is the serverless side of it. Serverless Postgres and traditional connection-based ORMs don't always get along, since every function spinning up wants its own connection. Vercel's setup is built with that in mind, but it's the part I want to actually test under a bit of load before I move anything important over.

So that's the plan: take one of my smaller projects and migrate it over as a trial run. Worst case I learn where the rough edges are. Best case I get to delete a whole separate database service from my mental overhead.

If you've run Vercel Postgres in anything real, I'd love to hear how it held up. Drop it in the comments or find me on Discord.