ClickHouse desktop clientstable
Your ClickHouse. Full steam ahead.
A native ClickHouse desktop client, from the sorting key to the replication queue.
macOS first, with Linux to follow early. Windows is planned.
Tested with a local ClickHouse server over HTTP without a password. TLS, authenticated servers and ClickHouse Cloud remain untested and should be treated as beta.

- Verified endpoint
- Local HTTP without a password
- Default HTTP port
- 8123
- Cloud and TLS
- Configured in the app. Live verification pending.
- Example local connection
- No password
The lay of the land
Everything ClickHouse keeps, where ClickHouse keeps it
DBeard lists each object at the level the engine scopes it, so the sidebar matches what you would see from the engine’s own catalog.
clickhouse://default@localhost:8123/default- ClickHouse HTTP addresses, normally on port 8123. Use the server's HTTP endpoint rather than its native TCP endpoint.
- TLS with clickhouses URLs, secure=true or port 8443 is implemented but untested against a real TLS server.
- Client certificate and key settings are available; real-service verification is pending.
- ClickHouse connection
- Database folderShown when several databases are present. System schemas are omitted.
- Tables, views and dictionariesTables and Views list directly under the connection when only one database is present.
- Columns
Made for ClickHouse
What you get on this engine
Follow the sorting key
Browse pages in sorting-key order. MergeTree tables can report row counts from metadata without scanning the whole table.
See work in progress
Inspect active and inactive parts, running merges, mutations, replication queues and native backup or restore jobs in Administration.
Keep every digit
UInt64 and larger numbers are read as text so digits are not lost. Arrays, maps and tuples display as JSON.

Support
ClickHouse features, one by one
“Coming soon” means it is on the roadmap. “Not planned” means we have decided against it.
| Feature | DBeard |
|---|---|
| MergeTree browsing in sorting-key order | Yes |
| MergeTree metadata row counts | Yes |
| Parts, merges, mutations and replication queue reports | Yes |
| Native backup and restoreRequires a configured server disk. | Yes |
| Insert and import rowsUpdates use ALTER TABLE in a query tab. The sorting key is not a unique row identifier. | Partial |
| Remote TLS accessSettings are implemented. Real-server verification is pending. | Partial |
ClickHouse benchmarks
Benchmark results coming soon.
Ports of call
Hosted ClickHouse it connects to
| Service | Status | Notes |
|---|---|---|
| Self-hosted ClickHouse | Tested | Start with a local server over HTTP without a password, the tested configuration. Remote servers, authentication and TLS need real-service verification before you rely on them. |
| ClickHouse Cloud on AWS | Should work | ClickHouse Cloud offers managed services on AWS. DBeard implements TLS connection settings, but we have not verified a connection to ClickHouse Cloud. Treat cloud connectivity as beta, including authenticated and TLS connections. |
The longer read
A ClickHouse client worth switching to
Browse the objects behind your queries
Explore tables, views, materialized views and dictionaries. The sidebar includes columns, sorting keys and data-skipping indexes. Databases appear as folders; system and INFORMATION_SCHEMA stay out of the sidebar and remain accessible from a query tab.
Sorting keys help ClickHouse read rows efficiently, but they do not identify a unique row. DBeard supports inserting and importing rows. To update existing data, review and run an ALTER TABLE statement in a query tab.
Inspect operations before taking action
Administration reports are bounded snapshots of the connected server, with database and table filters. Inspect parts, merges, mutations and the replication queue to understand what the server is doing.
Native backup and restore statements are prepared for review and use a configured server disk. Restore can leave partial data after failure. DBeard does not perform cluster fan-out, backup retention or server configuration. ClickHouse Cloud managed backups are separate from these native server operations.
Choose the ClickHouse tool that fits your work
For a native desktop workflow alongside your other databases, try DBeard within the tested scope above. If you are evaluating other clients, DataGrip’s official ClickHouse connection guide and DBeaver’s official ClickHouse documentation describe their ClickHouse setup options. Check each vendor’s documentation against the authentication and deployment you need.
Deployment and port references: ClickHouse Cloud regions and the official HTTP interface documentation. Provider availability does not imply that DBeard has tested that service.
Questions
ClickHouse and DBeard, answered
Does DBeard connect to ClickHouse Cloud on AWS?
ClickHouse Cloud is available on AWS. DBeard has TLS connection settings, but ClickHouse Cloud, TLS and authenticated ClickHouse connections remain untested. Treat them as beta; the stable scope is a local HTTP server without a password.
Can I edit a ClickHouse row in the grid?
No. Rows can be inserted and imported, but updates use ALTER TABLE statements in a query tab. A ClickHouse sorting key does not uniquely identify rows.
Are ClickHouse changes transactional?
No. DBeard does not provide ClickHouse transactions; statements are saved as they run. Do not assume the SQL transaction guarantees of other engines apply.
Does this manage ClickHouse Cloud backups?
No. Native BACKUP and RESTORE use a configured server disk. ClickHouse Cloud managed backups are separate, and cloud connectivity remains untested.
- ClickHouse HTTP interface (clickhouse.com), checked 2026-11-20
- ClickHouse Cloud supported regions (clickhouse.com), checked 2026-11-20
- DataGrip ClickHouse connection guide (jetbrains.com), checked 2026-11-20
- DBeaver ClickHouse documentation (dbeaver.com), checked 2026-11-20
Open your ClickHouse database in DBeard.
Free for one connection at a time, with every feature. No account, and your data stays on your machine.