Neon

Pro

Neon is serverless PostgreSQL. DevDb finds the Neon connection string of your project and connects.

Automatic detection

DevDb looks for a Neon connection string (a host that ends with .neon.tech) in this order:

1. .env, then .env.local, in these keys: DATABASE_URL, POSTGRES_URL, DATABASE_URL_UNPOOLED, POSTGRES_URL_NON_POOLING.
2. Any Neon connection string in .devdbrc.

Example .env:

DATABASE_URL=postgresql://app_owner:[email protected]/app?sslmode=require

When DevDb finds a string, Neon - PostgreSQL shows under Local Databases. Click it to connect.

Add a connection manually

Use a direct connection:

1. Under Remote Connections, click Add, then select Direct Connection.
2. Paste the connection string from the Neon console. DevDb fills in the fields and turns on TLS.
3. Click Test, then click Connect.

TLS

Neon accepts only TLS connections. DevDb always uses TLS for Neon and verifies the certificate of the server.

Suspended compute (cold start)

Neon suspends a compute that is not in use. The first query then waits while the compute starts. DevDb tries the first connection up to 3 times, with a longer wait each time. If the connection still fails, click Reconnect in the DevDb panel.

Pooled and direct hosts

DevDb uses the host in your connection string. A -pooler host stays pooled. A direct host stays direct.

pgvector

DevDb shows vector columns in Neon databases. See pgvector.