Connections, SSH & TLS

Save a connection profile

Choose an engine and enter the host, port, user and database. The connection dialog also supports parsing a connection URL. Review the resulting fields before testing and saving.

Saved profiles let you return to a database from the sidebar. Use clear names so you can distinguish local, staging and production connections.

Connect through SSH

Enable SSH in the connection settings and enter the SSH host, port and user.
Choose password, private key or SSH agent authentication. Supply the private-key passphrase when needed.
Check the host fingerprint before trusting a new SSH host. Test SSH, then test the database connection.

Choose TLS settings deliberately

PostgreSQL supports disable, prefer, require, verify_ca and verify_full. verify_ca checks the certificate chain; verify_full also checks the hostname. Supply your CA certificate when the server uses a private CA.

Client certificate and key fields support mutual TLS where available. Exact TLS capabilities vary by driver: do not assume every engine provides PostgreSQL-equivalent verification.

Credential storage

The desktop app stores credentials in the operating system’s credential store. Core database workflows do not require a Meja account. Exported connection profiles can contain sensitive details; check export options before sharing them.