Ctrl+Shift+N) starts another with the connection list. Open Database… on a connection’s sidebar row opens another database as a session in the same window.


A PostgreSQL connection through an SSH tunnel
Engines
Every driver is compiled into the app. Pick the one in Driver:
The server releases each engine is tested against, and the ones it does not support, are in the app’s supported servers table.
Redshift, CockroachDB, TiDB, OceanBase and Databend are untested on Linux. Support through the PostgreSQL or MySQL drivers on Mac does not establish Linux compatibility.
Limits
- Binary, array, spatial, composite and variant cells are read-only. Inspect or copy them in the grid; use a query to change them.
- Enter time and timestamp values as text, such as
13:45:00or2026-11-05 13:45:00. Include an offset for types that store one. Invalid values stay in the editor with an error; correct them before saving. - Redis Cluster and Sentinel are unsupported. Connect to a standalone Redis server instead.
Add a connection
1
Open the connect dialog
Click Add Connection in an empty connection list, or choose New Connection… from the main menu.
2
Name the server
Pick the Driver, then fill Host and Database. Port starts on the engine’s default.
3
Sign in
Fill Username and Password. With Remember Password on, the password goes to secret storage; with it off, every connect asks for it.
4
Test, then connect
Test connects once to check the settings, then disconnects. Connect saves the connection and adds its session to the window.
mongodb+srv:// address, turn on DNS Seed List. Authentication Database (optional) names the database that holds the user.
Options
Safe Mode is also in the main menu while connected, and a change there is saved to the connection.
Pick Read-Only for a production server you only read. Moving to or from it reconnects that connection’s sessions.
TLS
Encryption under Security picks the mode:
Keep Verify full unless the server has no certificate this computer can check. For a server signed by your own certificate authority, choose its PEM file in CA certificate rather than dropping to Require.
- Client certificate and Client key log in with a certificate, on every network engine but SQL Server.
- TLS server name checks the certificate against another name than the host. MySQL and MongoDB take it only through an SSH tunnel.
- A failed handshake says what went wrong. An unknown issuer takes you to CA certificate, a name mismatch to TLS server name.
SSH tunnels
Turn on Use SSH Tunnel and fill Host or alias. Native packages run the systemssh client, so empty rows come from ~/.ssh/config, and known_hosts and your SSH agent apply as they do in a terminal. For the bundle, check Flatpak connections.
Use SSH agent by default. Choose Private key for a specific key file, or Password or Keyboard-interactive when the server requires it.
Jump hosts takes what
ssh -J takes: user@host:port, several separated by commas.
An unknown or changed host key shows its SHA256 fingerprint before anything connects, even where ssh_config says StrictHostKeyChecking accept-new or no. Troubleshooting covers a changed or revoked key.
SQLite and DuckDB files
With SQLite or DuckDB picked, Database file replaces the server rows. Choose… opens an existing file, and New Database… creates the file when you connect. A file also opens straight from Files, through Open With on a SQLite database, or from a terminal:SQL Server with Kerberos
Set Method to Windows (Kerberos). There is no username or password: the driver uses the ticketklist shows, so get one first.
MSSQLSvc/<host>:<port> from the host and port you typed. Native packages use the default realm of the host’s /etc/krb5.conf. Type the host name the SPN is registered for, not an IP address or a CNAME. A server in another realm works only when your KDC answers with a referral, as Active Directory does inside a forest.
Flatpak connections
The bundle runs inside a sandbox. Check these differences before copying a native connection setup:- Secrets use the Secret portal and an encrypted file inside the sandbox. Follow keyring recovery if a password, MCP token or AI key cannot be stored.
- Kerberos uses the host’s KCM ticket cache. The sandbox selects
/app/etc/krb5.conf, with DNS realm and KDC lookup, instead of the host’s/etc/krb5.conf. Obtain a ticket in KCM on the host; a file-backed ticket cache is not enough. - SSH reads
~/.ssh/config, keys andknown_hosts, but not the host’s/etc/sshconfiguration.ProxyCommandandMatch execcannot run host-only helpers. Use a setup supported inside the sandbox or install a native package. - File-backed FIDO keys cannot sign inside the sandbox. Load the key into the host SSH agent and choose SSH agent.
- A CA installed only on the host is absent from the runtime’s trust store. Select its PEM file in CA certificate and keep Verify full.

