Neon
Performance
Stability
Cost
Direct endpoint instead of -pooler in serverless
Part of the Connection pooling check · fix arrives as a guide
What it is
A serverless function connects to the direct Neon endpoint rather than the -pooler hostname.
Why it matters
The direct endpoint gives each function instance its own Postgres connection. Serverless scales by adding instances, so connection count grows with concurrency until the database refuses new ones.
How to fix it
Switch the hostname to the pooled endpoint — the one containing -pooler — so PgBouncer multiplexes connections. Keep the direct endpoint for migrations, which need session-level features the pooler does not offer.
Run them all on your app
Connect your repo and your live services with read-only scopes. The first scan is free, and nothing changes without your approval.