
Trino
AvailableDatabases
Self-hosted Trino, Starburst Enterprise, and Trino on Amazon EMR. Dex explores your catalogs, authors dbt models, and detects drift with cluster-load guards.
Why connect Trino?
Dex works with self-hosted Trino, Starburst Enterprise, and Trino on Amazon EMR to explore your catalogs, author dbt models, and detect drift across the data sources Trino already connects.
- Explore tables across your Trino catalogs without exporting data or building another pipeline
- Author dbt models and tests against fully qualified catalog.schema.table relations
- Protect shared cluster capacity with load budgets measured in cluster-seconds and server-enforced query caps
Works with Dex
Trino connects to the Exmergo products your team already uses.
How it works
Connecting Trino to
Point Dex at Trino
Install Dex in Claude Code by running /plugin marketplace add exmergo/exmergo-agent-plugins and /plugin install dex@exmergo. Set connector: trino in .dex/config.yml. Dex discovers your connection through TRINO_URL, the TRINO_* environment, configured connection coordinates, or an existing dbt profile; credentials stay outside the model context.
$ /plugin marketplace add exmergo/exmergo-agent-plugins
$ /plugin install dex@exmergo
Explore your catalogs
/dex:explore inventories and profiles the tables in your allowed catalogs and schemas, infers relationships, and proposes what to model.
$ /dex:explore
Author governed dbt models
/dex:transform authors dbt models and tests through dbt-trino, with builds targeting your configured development catalog and schema.
$ /dex:transform
Stay inside a cluster-load guard
Dex estimates scan load before execution and asks for confirmation before running metered work. Budgets are measured in cluster-seconds, with server-enforced runtime and physical scan caps to protect shared capacity.
Catch drift automatically
/dex:maintain detects schema, volume, and grain drift in your Trino sources and proposes reviewable changes to keep your project in sync.
$ /dex:maintain
