ClickHouse
AvailableDatabases
ClickHouse Cloud and self-hosted ClickHouse. dex profiles your tables and authors dbt models, with every scan capped by max_execution_time and max_bytes_to_read.
Why connect ClickHouse?
Connecting ClickHouse means your team stops exporting it by hand and starts working with it directly inside Dex.
- Query live data in ClickHouse without exporting it or standing up a new pipeline
- Keep dashboards and dbt models in sync with ClickHouse instead of a stale nightly copy
- Give teams governed, self-serve access to ClickHouse under the same RBAC and audit trail as everything else
Works with Dex
ClickHouse connects to the Exmergo products your team already uses.
How it works
Connecting ClickHouse to
Exmergo DexCost guard: compute secondsPoint Dex at ClickHouse
Install Dex in Claude Code by running /plugin marketplace add exmergo/exmergo-agent-plugins and /plugin install dex@exmergo, then run /dex:explore against ClickHouse. Dex connects with your ClickHouse credentials directly, so they, and your raw data, never enter the model's context.
$ /plugin marketplace add exmergo/exmergo-agent-plugins
$ /plugin install dex@exmergo
$ /dex:explore
Explore before touching anything
/dex:explore profiles the schema it finds in ClickHouse and proposes what to model before writing a single line of dbt.
$ /dex:explore
Author governed dbt models
/dex:transform writes and maintains the dbt models and tests that turn raw ClickHouse data into trusted, reusable tables in your project.
$ /dex:transform
Stay inside a cost guard
Dex enforces a cost guard on every query it runs against ClickHouse, so exploration never turns into a surprise bill.
Catch drift automatically
/dex:maintain flags it when ClickHouse's schema changes and proposes the fix, instead of letting your dbt project silently drift out of sync.
$ /dex:maintain