Generally serverless means that you don't have to worry about the servers, not that it's not running on a server, of course it is. In this case, neon offers pre

Generally serverless means that you don't have to worry about the servers, not that it's not running on a server, of course it is. In this case, neon offers pretty good scalability that goes hand in hand with the usual serverless behaviour of having multiple instances of your code running in parallel, something which postgres alone is not very good at handling because of the "one process per connection" functionality. You'd need pgbouncer or RDS proxy on top of your postgres instance.