Connecting

Create, save, and manage connections. Credentials stay in the macOS Keychain.

A connection points Tablify at one database. You can save connections, pin the ones you use most, and reopen recent ones from search.

Creating a connection

Connection forms are built from the driver, so each engine asks for exactly the fields it needs.

  • PostgreSQL and MySQL use a host, password, and TLS mode. Verified TLS can also use a CA, client certificate, and private key.
  • SQLite opens a local file. You can mark it read-only, and Tablify handles files that are missing, locked, read-only, moved, or corrupt.
  • Redis connects to a standalone server over a URL or host, with an optional username and password, a logical database, and TLS.

Where credentials live

Secrets are stored in the macOS Keychain under the service com.tablify.app. They are never written to the local state file, logs, diagnostics, or crash reports. If the Keychain is unavailable, Tablify offers a session-only credential instead of a plaintext fallback.

When a connection fails

Connection errors are split into network, TLS, authentication, missing database, permission, and unknown. Tablify points to the field that needs attention and lets you copy the error details.

Managing connections

Create, edit, duplicate, remove, connect, reconnect, disconnect, and test connections from the same list. Each window runs one active connection at a time, with as many data and query tabs inside it as you need.