BigQuery
AvailableDatabases
Google BigQuery data warehouse. dex profiles your tables and authors dbt models directly against your BigQuery project.
Why connect BigQuery?
Connecting BigQuery means your team stops exporting it by hand and starts working with it directly inside Dex.
- Query live data in BigQuery without exporting it or standing up a new pipeline
- Keep dashboards and dbt models in sync with BigQuery instead of a stale nightly copy
- Give teams governed, self-serve access to BigQuery under the same RBAC and audit trail as everything else
Works with Dex
BigQuery connects to the Exmergo products your team already uses.
How it works
Connecting BigQuery to
Exmergo DexCost guard: bytes scannedPoint Dex at BigQuery
Install Dex in Claude Code by running /plugin marketplace add exmergo/exmergo-agent-plugins and /plugin install dex@exmergo, then run /dex:explore against BigQuery. Dex connects with your BigQuery 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 BigQuery 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 BigQuery 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 BigQuery, so exploration never turns into a surprise bill.
Catch drift automatically
/dex:maintain flags it when BigQuery's schema changes and proposes the fix, instead of letting your dbt project silently drift out of sync.
$ /dex:maintain