Connecting
Create, save, and manage connections. Credentials are stored in the macOS Keychain.
A connection points Tablify at one database. A window holds one active connection, with as many table, key, and query tabs inside it as you need.
Creating a connection
Start from the welcome window by choosing an engine or pasting a connection string. A pasted string is parsed locally and never sent anywhere to be interpreted. It fills an ordinary form you can correct before anything is saved or connected.
Each form is built from the driver, so an engine asks only for the fields it uses.
| Engine | Fields |
|---|---|
| PostgreSQL, MySQL | Host, credentials, and a TLS mode. Verified TLS also accepts a CA, client certificate, and private key |
| SQLite | A local file, optionally opened read-only |
| Redis | A URL or host, an optional username and password, a logical database, and TLS |
Credentials
Secrets are stored in the macOS Keychain under the service com.tablify.app, keyed by the saved connection and the field they belong to. The saved record holds public parameters and references to those entries, never the secrets themselves. Nothing secret reaches the local state file, logs, diagnostics, or crash reports.
If the Keychain is unavailable, Tablify offers a session-only credential instead of falling back to plaintext.
Connection records cannot be exported or imported. A record names the Keychain accounts its passwords live under, so a file listing them would be a credential index.
When a connection fails
Network, TLS, authentication, missing database, permission, and resource failures are reported separately. Tablify points at the field that needs attention, and the details can be copied.
A failed attempt keeps the form and its safe input, and clears the secret fields.
Managing connections
The connection list is where records are created, edited, duplicated, removed, and tested, and where a session is connected, reconnected, and disconnected. Pin the connections you use most. Recent ones reopen from quick open.
Reconnecting creates a new session and rebuilds the open tabs against it. Tablify stores up to 200 saved connections and refuses new ones past that limit rather than dropping an existing record.