Skip to main content
dex lets a coding agent work on your warehouse and your dbt project without the risks that usually come with it. It explores an unfamiliar warehouse, authors dbt models and semantic layers as reviewable diffs, and keeps the project correct as the data underneath it changes. Every rule that makes this safe lives in the engine, not in a prompt. dex never writes to your data, never pulls personal data into the agent’s context, never spends on a metered warehouse before quoting the cost, never changes your project except as a diff you review, and never builds anywhere but a dev target. The cost controls and the PII policy describe two of those rules in full.

​
Explore, Transform, Maintain

  • Explore ranks what matters in a warehouse, profiles it from aggregates, flags personal data, and infers how tables join. See the exploration methodology.
  • Transform writes and refactors dbt models, tests, and semantic layers as plans you review before anything is applied. See what dex reads and writes in a dbt project.
  • Maintain compares the warehouse and the project against a known-good snapshot and proposes the edits that reconcile any drift.

​
Where to go next

  • The CLI reference lists every command and flag.
  • The connector pages, starting with DuckDB, cover credentials, cost, and read-only enforcement for each warehouse.
  • The Apache Ossie tutorial walks a native semantic layer through every command on a local warehouse.