Serverless Postgres: a connection string, not a server

What this is about

The database is reachable over HTTP from a runtime that cannot hold a socket open. What you are given is a connection string, not a machine you provision, log into, or keep alive.

The short version

Here’s something every vibe coder should know. Your database does not have to be a machine you look after. With Neon, what you are given is a connection string.

That string is the whole address. It carries the user, the password, the host and the database name, and nothing in it names a computer you rent.

Neon calls this serverless Postgres. Their own documentation describes it as Postgres with autoscaling, scale to zero, and instant restore.

Here is the part that matters for your code. Neon publishes a driver that lets you query from environments that have no long lived socket, over plain HTTP.

Their documentation says querying over an HTTP fetch request is faster for single transactions, the kind they call one shot queries.

Here is the check. Ask your AI whether this project talks to the database over HTTP or over a socket. Then ask which one the code you are deploying can actually keep open.

And the honest limit is on the same page. If you need a session, or an interactive transaction, HTTP is not enough and the driver gives you web sockets instead.

So the thing you were handed is an address, not a box. The database answers over the web, and what is left to you is how you talk to it.