Features
Everything the app does, by the work.
Nine chapters — connect, security, query, terminals, edit, design, understand, assistant, move — each shown with the app's own pictures and clips, and each naming its guide in the docs.
Twelve engines. One app.
Every feature is built against one driver contract, so the grid, the designers and the assistant work the same whether the server speaks Postgres, Oracle or Redis.
Hosted services get a tile of their own with the port and SSL mode they expect:
Supabase
Neon
CockroachDB
TimescaleDB
YugabyteDB
Valkey
ClickHouse Cloud
Paste a string, or pick a tile.
Paste a connection string, an ssh command or a file path into the box at the top of the picker, and the form opens filled in. Or pick a tile: the databases, the hosted services and the hosts each have a card of their own, and the port and SSL mode follow. Test the connection before you save it; a new one is tried before it is filed.
- Save Password starts off: the app asks when you connect, and forgets when it quits
- A colour and a Production switch for the servers that matter
- Folders in the sidebar, and a filter that never dials a server
And around a connection.
When a connection drops
DBClient tries a query again only when the server confirms it is safe. If a change may have already gone through, DBClient asks you to check.
Guide: dropped connectionsMove your set-up
Export connections, folders and saved queries as one readable file; import it on another Mac. Passwords come along only behind Touch ID.
Guide: moving connectionsFiles open as connections
Drop a SQLite or DuckDB file or a .sql script on the window or the Dock; DBClient reads the bytes, not the extension, and opens the right thing. Drop a CSV, Excel or JSON file on a table to import it, or on a database to make a new table from it.
Guide: opening filesWhat each engine gets.
Every engine has the sidebar, the grid, the assistant and a door to its own console client. The kinds of object that exist on an engine are the kinds it shows.
| Engine | Editable grid | Designers | Users & Roles | Diagram |
|---|---|---|---|---|
| PostgreSQL and Supabase, Neon, CockroachDB, TimescaleDB, YugabyteDB | ✓ | ✓all kinds | ✓ | ✓ |
| MySQL and MariaDB | ✓ | ✓tables, triggers, events, sequences on MariaDB | ✓ | ✓ |
| SQLite | ✓with table rebuilds | ✓tables, indexes, triggers | — | ✓ |
| SQL Server | ✓ | ✓plus synonyms, partition functions and schemes | ✓ | ✓ |
| Oracle | ✓ | ✓tables, sequences, types, synonyms, triggers, tablespaces | ✓ | ✓ |
| IBM Db2 | ✓tables with an enforced key | ✓tables, indexes, triggers, sequences | ✓ | ✓ |
| DuckDB and CSV files | ✓ | ✓tables, sequences | — | ✓ |
| ClickHouse and ClickHouse Cloud | ✓ | ✓tables | ✓ | ✓ |
| Databricks SQL warehouses | ✓managed tables | ✓Delta tables, views, routines | ✓ | ✓ |
| MongoDB | ✓documents | —console | ✓ | — |
| Redis and Valkey | ✓keys | —console | ✓ACL users | — |
Oracle and IBM Db2 need their makers' client libraries, which the app does not ship. The first Oracle or Db2 connection offers to download the client from Oracle or IBM, checks every file against the digests the app was built with, and keeps it in your Library folder, where the same sheet updates or removes it.
Databricks needs no client library. Connect to a SQL warehouse over HTTPS with an access token, then browse its catalogs in the sidebar. On PostgreSQL and SQL Server, the sidebar lists the databases on that connection. ClickHouse Cloud supports browser sign-in.
Safe by default.
Passwords in your Keychain behind Touch ID, servers checked before they are trusted, production marked so every write waits, and an assistant that reads but never writes. Nothing leaves your Mac that you did not send.
Saved passwords stay behind Touch ID.
By default, DBClient asks for Touch ID or your Mac password when you open a database, file or SSH connection, even if you have no saved password. If the connection drops, DBClient can reconnect without asking again.
- Turning this off in Settings also asks for Touch ID or your Mac password
- Saved passwords stay in your Keychain. Showing one on screen asks you to unlock it
- With Save Password off, DBClient asks when you connect and forgets the password when you quit
Production mode: every write waits.
Mark a connection as production and give it a colour. The whole workspace wears the colour while that server is in front, every session on it starts with auto-commit off, and a change runs only when you commit it, with its SQL shown first.
- Seven colours, so staging never looks like production
- Auto-commit can be switched on for a session; the next connect starts it off again
- Engines without transactions say so under the switch
Guarded at every step.
Keychain and Touch ID
Passwords are Keychain items, never a file, and every connection can ask for Touch ID or your login password before it connects. Or save none: leave Save Password off and the app asks when you connect, then forgets the answer when it quits. Showing a saved password on screen always asks for Touch ID.
Guide: passwordsSSH, SSL, proxies
SSH tunnels (password, RSA, Ed25519 or ECDSA key) that read your ~/.ssh/config the way ssh does, Host entries, jump hosts and keys included; SSL up to full certificate verification; SOCKS5 and HTTP CONNECT proxies, chained with SSH when you need both. AWS IAM sign-in for RDS and Aurora PostgreSQL, the token signed at every connect.
Guide: tunnels and proxiesHost keys that must match
An SSH server's key is checked against ~/.ssh/known_hosts, as ssh checks it. A new server asks once, with its fingerprint on the sheet; a changed or revoked key is refused with the file and the line named, and there is no setting that turns the check off.
Guide: host keysThe assistant reads, never writes
A query the assistant runs must start with a reading word, be one statement and hold no word that writes; then the engine enforces it again, in its own read-only mode. Your key stays in the Keychain and goes only to the provider you chose.
Guide: the AI assistantNo account, no telemetry
Nothing to sign up for, no crash reporter, no analytics. The whole list of what the app connects to, and when, is in the docs; your own servers are always on it, and nothing else is until you ask for it.
Guide: what the app connects toSigned and verified updates
Every build is signed and notarized. An update installs only once its disk image's checksum matches the published cask and the app inside passes a strict code-signing check carrying the same Developer ID.
Guide: updatesAn editor that knows your schema.
A hand-rolled SQL lexer and an outline of the statement drive the highlighting and the completion, so both stay exact and fast.
Write, run, repeat.
Tables, columns, keywords and functions complete as you type, scoped to the tab's database and in the engine's own dialect; a join is written from the foreign keys, and a CTE's or a subquery's columns complete like a table's. ⌘↩ runs the statement under the cursor, ⇧⌘↩ runs everything, and a selection runs alone with either. Results land per statement, each with its own grid, log and pager.
- Syntax highlighting, problem marks as you type, and a formatter (⇧⌘F) that never touches your types
- Explain before you run; Watch to re-run on an interval
- Comment a block with ⌘/, duplicate or delete a line, find and replace
- Tabs remember their editor, results and page — ⇧⌘T reopens the one you closed
⌘K to anywhere.
The command palette searches tables and views, their DDL, the schema diagram, the app's actions and your other connections as you type. Arrows and ↩ run the choice.
- Open a table, show its CREATE statement, start a designer
- Switch connection without reaching for the sidebar
- Works from any tab, on any engine
Every tab, one grid.
The strip's grid button shows every open tab across every connection as a card with its first lines. Click one, or walk them with the arrow keys and press Return; Escape closes the overview.
- One strip across connections, grouped in the sidebar's order
- Cards preview the query, the browse, the designer
- ⌘W closes, ⇧⌘T brings the last closed tab back
And around the editor.
A sidebar that scales
Folders of connections, one flat tree that stays quick with 900 tables open, a filter that never dials a server, and about how many rows each table holds beside its name.
Guide: the sidebarWatch and Explain
Re-run a statement on an interval and see the rows change; read the plan before you run it.
Guide: Explain and WatchSaved queries and tabs
Queries saved per connection and database, every statement you ran remembered and one ⌘K away, tabs that remember their editor, results and page, ⇧⌘T to bring one back.
Guide: saved queriesA real terminal, wherever the work is.
The engine's own client in a console tab, a shell on any server you reach over SSH, with its files beside it, and a shell on this Mac, one click away.
The engine's own client, in a tab.
A console tab is a real terminal running the client you already know — psql, mysql or mariadb, sqlite3, sqlcmd, clickhouse-client, mongosh, redis-cli, SQL*Plus or SQLcl, db2cli, dbsqlcli — signed in with the connection's own host, port, user and password, through its SSH or proxy tunnel too. Its prompt, history, pager and colours are the client's, not an imitation.
- The door is always there; without the client, the tab names the Homebrew line that installs it, with a copy button and Check Again
- The password never goes on the command line: the client reads it from its environment or its own prompt
- MongoDB and Redis also get a command console as their first-class query surface
- DuckDB is the one engine without a console: a file allows one process, and the app is it
- Ask AI Assist to explain console output or suggest SQL. Click Insert, then press Return to run it
A terminal on any server, or on this Mac.
An SSH host is a connection too: the SSH Tunnel page's rows, your ~/.ssh/config read as in Terminal, a terminal on the server the moment it connects, and a Files tab for its folders. This Mac is the second kind of host, and its terminals run your own login shell. Every terminal tab is named by the folder its shell is in.
- One authenticated connection per host; every terminal, listing and copy joins it, and nothing is typed twice
- The host's Connection String is its ssh command: paste one to fill the rows, or copy it out for Terminal
- The terminal button, ⌘T and the row's New Terminal open more; exit closes the tab
- A Files tab lists the host's folders; drag files in from the Finder or rows out to it, and rsync copies them in the tab's log with a progress line, asking before it writes over anything; drag rows onto a folder to move them on the host, or Copy, Cut and Paste within it and with the Finder; Delete… removes what you chose
- A terminal on this Mac in one click, from the toolbar's Terminal button or ⌃⌘T; the button at the foot of the sidebar opens the selected connection's terminal or console
- AI Assist reads recent terminal output and suggests commands for your Mac or SSH server. Click Insert, then press Return to run a command
- The server's key is checked against ~/.ssh/known_hosts, as ssh checks it
- Everything a connection has: folders, a colour, Production, Export and Import
A grid built for editing.
Drawn by AppKit, so 60 columns scroll as fast as 6, and every cell is a real control when you edit it.
Edit in place, review as SQL, commit once.
A single-table SELECT that covers the primary key is editable — typed editors per column kind, rows added and deleted from the row gutter, joins edited cell by cell against each owning table. ⌘S shows the statements; Commit runs them in one transaction.
- Excel-style selection: rows, columns, cells, ranges
- Sort with a double-click on a header or from its menu, several columns with ranks
- Long text and JSON open in their own editor, reformatted on demand
- Set NULL, revert a cell, discard everything
A picker for every foreign key.
A cell that holds a foreign key opens a picker on the table it points at: the first 500 rows as a small table, each key beside the name or title it stands for, the table's name beside the filter box. Type a few letters, click the row, and the key is written for you. Any other value can still be typed.
- The row the cell points at is marked and in view as the picker opens
- The filter searches every column shown
- A long key such as a UUID shows whole; the picker opens wider for it
Designers for every kind of object.
Tables, indexes, foreign keys, triggers, events, sequences, types, synonyms, aggregates, operators, extensions, casts, tablespaces, partition functions and schemes, users and roles — each one a tab, each one previewing its SQL. Kinds of object
Alter a table without writing the ALTER.
Columns load as drafts. Rename, retype, reorder, change a default, toggle NOT NULL, add and drop keys and indexes — the diff becomes ordered statements you can read before you apply them. On SQLite, the full rebuild recipe runs in one transaction.
- Postgres emits USING casts for type changes
- MySQL restates the full column, and says so
- Collations picked from the server's own list, and kept when a column is restated
- Column and table comments, written the way each engine keeps them
- What an engine cannot do is a note, not a silent failure
- Compare two databases and read the script that makes one like the other
Two schemas, and the script between them.
Compare two connected databases that use the same engine. See which tables, columns, indexes and keys differ, then review a SQL script to update the target. Changes run in the order the tables need. On PostgreSQL, SQL Server, SQLite and DuckDB, a failed update is fully undone.
- Staging against production, or one branch's database against another's
- What only the target has is kept unless you ask to drop it
- Open it in a query tab on the target and run it there, or copy it
Each database at a glance.
Click a database and see every kind of object it holds with a count, the server's version, and a door to create what is missing. Cards open the same listings the sidebar does.
- Server-level kinds — extensions, casts, tablespaces, accounts — beside the schema's
- New Schema, New Table, New Role from one place
- The diagram and the console, one click away
Accounts, memberships and grants.
On every engine that has accounts, the sidebar files them under Users & Roles: superusers, connection limits, expiry, role membership and grants at every scope. The role editor writes the GRANTs and REVOKEs for you.
- Postgres, MySQL, MariaDB, SQL Server, Oracle, IBM Db2, Databricks, MongoDB, Redis ACLs, ClickHouse
- SQL Server's three-state DENY handled as its own thing
- Every change previewed as SQL
Pictures of your data.
The schema as a diagram.
Drawn from real foreign keys, laid out by relationship, edges routed around boxes. Drag tables; the layout keeps your placements and arranges the rest around them.
- Self-references and multiple keys between two tables drawn distinctly
- Filter to a name and the picture narrows
- Double-click a table to open it
A chart of any result.
Bar, line, area, pie and scatter over the result you already have. Choose the X column, the measures, a series column and the aggregate; the chart follows re-runs.
- A pie folds its long tail into Other
- Eight-colour palette validated for both appearances
- Toggle back to the grid at any time
Ask your data a question.
An assistant that sees your schema and answers with read-only queries, through your own key or a model on your Mac.
An assistant that reads, never writes.
Ask in plain words. The assistant sees your schema, runs read-only queries to check its answer, and replies with tables and SQL. A statement that would change data is handed back to you as text — the guard is code, not a prompt.
- Claude, OpenAI, Gemini, xAI, DeepSeek, Mistral — your key, your choice; or a model on your own Mac through Ollama or LM Studio, with nothing leaving it
- View a saved API key in Settings with Touch ID or your Mac password
- Read replies as they arrive, then insert SQL into the editor or commands into a terminal
- Ask about console or terminal output, including lines that scrolled off screen. You choose which commands to insert and run
- Inline suggestions in the editor, which you can switch off
In, out, and across engines.
A table is not stuck where it was made. Drag it to another server, or take its rows away as a file and bring others in.
Drag a table to another engine.
Drop a table from one connection onto another's database and a sheet shows what will run: the CREATE in the target's dialect, the rows to copy, structure or data or both. Tables move between any two of the ten SQL engines, columns and types translated; views and routines move where the dialect matches.
- PostgreSQL to SQLite, MySQL to DuckDB, Oracle to Db2, and every other pair
- Replace or keep what is already there
- One transaction where the target has them
Export, read the DDL, import.
Export the rows in front of you, or a whole table, as CSV, TSV, JSON, JSON Lines, SQL inserts, Excel, Markdown, HTML or XML, copied or saved. Read any object's CREATE statement. Import any of those back into a table, with column mapping and NULL handling, in one transaction, or drop the file on the table — or on a database, to make a new table from it.
- All rows or the selection
- DDL for tables, views, routines, types and the rest
- The import opens the table it filled
A whole database out, and back in.
Dump Database… runs the engine's own tool — pg_dump, mysqldump, sqlite3 or mongodump — with the file, the scope and the connection's settings filled in, in a console tab that shows the tool's own output and, at its foot, how far the job has got. Every dump that finishes is listed under Backups, a double-click from Restore, and the file stays where you chose to write it: no hidden folder, no schedules. Restore Database… reads any file back the same way with psql, mysql, sqlite3 or mongorestore.
- Structure, data, or both
- Backups per connection: each file with its size and date, Restore a double-click away, and the Trash for the ones you are done with
- The console's password and tunnel handling, so nothing is typed twice
- A missing tool is named, with its Homebrew line
Try it on your own database.
Free for a month, then one price, and never asking you to sign in.
$brew install --cask az-code-lab/taps/dbclient