Connection details

Connection details for a deployment can be accessed from the main page from the Connection details accordion:

Connection details

or the SQL workspace from the Connect button:

Connect button

Connection strings

GlareDB uses the Postgres wire protocol, and our connection strings follow the same format. A full connection generated by GlareDB will look like the following:


Breaking this down, we have the following information:

  • user: dEVytoQ7kXWZ (randomly generated by GlareDB)
  • password: glaredb_pw_2QgP0HFpMdteKrHpav7utHPVIsY7 (randomly generated by GlareDB)
  • hostname:
  • port: 6543
  • database: dedicated

The hostname also includes the organization which contains the deployment. In this example, the organization is “glaredbteam”.

Connecting to a specific compute engine

A compute engine may optionally be specified as part of the database name. For example, if you have a running engine named my_engine, then use the following for the database in the connection string:


Using the example of the previous section, the full string would be my_engine.dedicated:


If the compute engine is not reachable or doesn’t exit, the connection will not succeed or fallback.

Generating new passwords

Password are only ever shown once. Store your password somewhere secure, as it can never be retrieved again. In cases where you forget your password, simply generate a new one. There is a limit to how many passwords can be generated for a deployment.

A new username and password combo can be generated by clicking the New password button. A randomly generated username and password will be displayed. The password will only be displayed once.

New password

Also note that when a new password is generated, the connection string will be populated with that password allowing for easy copy and pasting into the client of your choice.

See Managing passwords for more on passwords.