PostgreSQL, Neon, CockroachDB & YugabyteDB

All four engines use the same connection form — pick the engine that matches your host so rdSQL applies the right dialect and defaults.

Connect#

1. Click New Connection.
2. In the Connection tab, set a Connection Name and choose PostgreSQL, Neon, CockroachDB or YugabyteDB as the Database Engine.
3. Fill in Host, Port, Database, Username, Password — or paste a connection URL and let rdSQL fill the fields for you. A *.neon.tech URL selects the Neon engine and turns SSL on by itself.
4. If your provider requires TLS, set SSL Mode accordingly (disable, prefer, or require). Most managed providers — Neon, Amazon RDS, Supabase, CockroachDB Cloud — require it.
5. If the database is only reachable through a bastion host, open the Security & SSH tab and fill in the SSH Host, SSH User, and a private key path or password.
6. Click Test, then Save.

What you get#

The connection appears in the sidebar with its schemas and tables. From there you can browse and edit data, run SQL, back up and restore, compare schemas, and draw ER diagrams.

PostgreSQL and Neon also back up into each other: a PostgreSQL connection can be the target of a Neon backup and the other way round — they count as the same engine for Backup & Restore.

Troubleshooting#

• Connection timed out — check firewall rules and the host/port; if the database sits on a private network, use the SSH tunnel fields in Security & SSH.
• SSL required / connection refused — managed Postgres providers almost always need SSL Mode set to require.
• Auth failed — verify the username and password, and that the user has CONNECT privilege on the target database.