Get your Neon connection details
- Open the Neon console and select your project.
- On the Dashboard, click Connect.
- Copy the connection string. It looks like:
- Pooled (
-poolerin the host) — use this for QueryBear. It handles many short-lived connections well. - Direct — for migrations and long sessions; not needed here.
Create a read-only role
Run the standard Postgres read-only role SQL from the PostgreSQL guide using Neon’s SQL Editor orpsql. Neon supports roles and ALTER DEFAULT PRIVILEGES like any Postgres.
Add the connection to QueryBear
In the QueryBear dashboard → Connections → New connection → PostgreSQL. Paste the Neon connection string, or fill in host/port/database/user/password. SSL mode must berequire — Neon rejects unencrypted connections.
Neon-specific notes
- Branching: Neon lets you create database branches. Point QueryBear at a branch’s connection string to query that branch in isolation — handy for testing against a copy of production.
- Autosuspend: Neon scales compute to zero when idle. The first query after a suspend may take a second to wake the compute. QueryBear’s query timeout accommodates this.
- Pooled endpoint: Always prefer the
-poolerhost for QueryBear.