Connect a GUI application
Learn how to connect a GUI application to Neon
This topic describes how to connect to a Neon database from a GUI application or IDE. Most GUI applications and IDEs that support connecting to a Postgres database also support connecting to Neon.
Gather your connection details
The following details are typically required when configuring a connection:
- database name
- role (user)
You can gather these details from the Connection Details widget on the Neon Dashboard. Select a branch, a role, and the database you want to connect to. A connection string is constructed for you.
Neon supports pooled and direct connections to the database. Use a pooled connection string if your application uses a high number of concurrent connections. For more information, see Connection pooling.
The connection string includes the role, password, hostname, and database name.
- database name:
Neon uses the default Postgres port,
Connect to the database
In the GUI application or IDE, enter the connection details into the appropriate fields and connect. Some applications permit specifying a connection string while others require entering connection details into separate fields. In the pgAdmin example below, connection details are entered into separate fields, and clicking Save establishes the database connection.
Some Java-based tools that use the pgJDBC driver for connecting to Postgres, such as DBeaver, DataGrip, and CLion, do not support including a role name and password in a database connection string or URL field. When you find that a connection string is not accepted, try entering the database name, role, and password values in the appropriate fields in the tool's connection UI when configuring a connection to Neon. For example, the DBeaver client has a URL field, but connecting to Neon requires specifying the connection details as shown:
Tested GUI applications and IDEs
Connections from the GUI applications and IDEs in the table below have been tested with Neon.
Some applications require an Server Name Indication (SNI) workaround. Neon uses compute endpoint domain names to route incoming connections. However, the Postgres wire protocol does not transfer the server domain name, so Neon relies on the Server Name Indication (SNI) extension of the TLS protocol to do this. Not all application clients support SNI. In these cases, a workaround is required. For more information, see Connection errors.
|Application or IDE||Notes|
|AWS Database Migration Service (DMS)||Use SNI workaround D. Use a |
|Azure Data Studio||Requires the PostgreSQL extension and SNI workaround D|
|Beekeeper Studio||Requires the Enable SSL option|
|Datagran||Requires SNI workaround D connection workaround|
|DronaHQ hosted cloud version||Requires selecting Connect using SSL when creating a connector|
|Forest Admin||The database requires at least one table|
|Google Looker Studio||Requires Enable SSL and uploading the ISRG Root X1 self-signed |
|Luna Modeler||Requires enabling the SSL/TLS option|
|PopSQL||No SNI support. Use SNI workaround D.|
|Postico||SNI support since v1.5.21. For older versions, use SNI workaround B.|
|PostgreSQL VS Code Extension by Chris Kolkman|
|TablePlus||SNI support on macOS since build 436, and on Windows since build 202. No SNI support on Linux currently. For older versions, use SNI workaround B.|
|Segment||Requires SNI workaround D|
Applications that use older client libraries or drivers that do not support Server Name Indication (SNI) may not permit connecting to Neon. If you encounter the following error, refer to Connection errors for possible workarounds.