# Exmergo

> Documentation for Exmergo, the AI stack for your data stack, and for its products, starting with Dex, the agent-native analytics engineering toolkit.

- [Exmergo](https://docs.exmergo.com/index.md): Exmergo is the company focused on building the AI stack for your data stack. Find the documentation for each Exmergo product here, starting with Dex.
- [Introduction](https://docs.exmergo.com/dex/index.md): dex is the agent-native analytics engineering toolkit. Explore a warehouse, transform it with reviewable dbt edits, and maintain it as schemas and data drift.
- [Cost controls](https://docs.exmergo.com/dex/guardrails/cost-controls.md): How dex prices warehouse work before it runs: the confirm and budget handshake, per-command and daily ceilings, the spend ledger, and auto-profile pricing.
- [The PII policy](https://docs.exmergo.com/dex/guardrails/pii-policy.md): How dex flags personal data without surfacing it: what a PII flag means, the blocking threshold, the query firewall rule, and how a human clears a flag.
- [The source of truth and the .dex/ cache](https://docs.exmergo.com/dex/concepts/source-of-truth.md): Why the repository is the source of truth for dex: dbt models and the semantic layer stay canonical, and the .dex/ directory is only a disposable cache.
- [Exploration methodology](https://docs.exmergo.com/dex/concepts/methodology.md): How dex makes sense of a warehouse without enumerating it: one-pass inventory, ranking, aggregate-only profiling, join inference, and the persisted draft map.
- [dbt projects: what dex reads and writes](https://docs.exmergo.com/dex/concepts/dbt-project.md): What dex reads from a dbt project, how it writes changes back as reviewable diffs, and how it runs dbt build, deps, and parse against a dev target only.
- [DuckDB connector](https://docs.exmergo.com/dex/connectors/duckdb.md): Run dex on DuckDB with no credentials: the zero-setup on-ramp, the demo warehouse, the dev and CI engine, and the read-only, resource-bounded defaults.
- [BigQuery connector](https://docs.exmergo.com/dex/connectors/bigquery.md): Connect dex to BigQuery with Application Default Credentials. Every scan is priced by a free dry run, capped with maximum_bytes_billed, and read-only.
- [Snowflake connector](https://docs.exmergo.com/dex/connectors/snowflake.md): Connect dex to Snowflake through connections.toml, environment variables, or a dbt profile. Warehouse-seconds pricing, credits shown, read-only by design.
- [Databricks connector](https://docs.exmergo.com/dex/connectors/databricks.md): Connect dex to Databricks SQL warehouses over Unity Catalog: unified SDK auth, warehouse-seconds pricing with DBUs alongside, and read-only enforcement.
- [Amazon Redshift connector](https://docs.exmergo.com/dex/connectors/redshift.md): Connect dex to Amazon Redshift Serverless or provisioned clusters: IAM temporary credentials, compute-seconds priced as RPU-hours, read-only access.
- [PostgreSQL connector](https://docs.exmergo.com/dex/connectors/postgres.md): Connect dex to PostgreSQL: credential discovery from pg_service.conf or the environment, database-seconds cost gating, and per-statement timeouts.
- [ClickHouse connector](https://docs.exmergo.com/dex/connectors/clickhouse.md): Connect dex to self-hosted ClickHouse or ClickHouse Cloud: two-part namespaces, database-seconds or compute-seconds pricing, and read-only server caps.
- [Querying the semantic layer](https://docs.exmergo.com/dex/semantic-layers/overview.md): Query a semantic layer with dex explore semantic: list metrics, read dimension values, and run governed metric queries on dbt, dbt Cloud, or Apache Ossie.
- [Apache Ossie compatibility](https://docs.exmergo.com/dex/semantic-layers/ossie.md): What dex accepts from a native Apache Ossie semantic document, what it validates, what it derives for exploration and drift, and what it declines to claim.
- [Apache Ossie tutorial: a semantic layer end to end](https://docs.exmergo.com/dex/guides/ossie-semantic-layer.md): Walk one Apache Ossie semantic document through every dex command on a local DuckDB warehouse: configure, read, query, detect drift, and author changes.
- [dex CLI overview](https://docs.exmergo.com/dex/cli/overview.md): Every dex CLI command at a glance: global options, connection flags shared by all subcommands, and where to start, generated from the released argparse tree.
- [dex connect](https://docs.exmergo.com/dex/cli/connect.md): Reference for dex connect test: check that a connector can reach its warehouse with discovered credentials and report what it can do, before any real work.
- [dex explore](https://docs.exmergo.com/dex/cli/explore.md): Reference for dex explore: every read-only subcommand for inventory, profiling, joins, diagrams, guarded queries, clustering, and semantic layers, with flags.
- [dex transform](https://docs.exmergo.com/dex/cli/transform.md): Reference for dex transform: every subcommand that authors, plans, applies, builds, and tests dbt changes, with each flag, default, and positional argument.
- [dex semantic](https://docs.exmergo.com/dex/cli/semantic.md): Reference for dex semantic: define, update, and plan dbt semantic models or native Apache Ossie documents as reviewable diffs, with every flag documented.
- [dex maintain](https://docs.exmergo.com/dex/cli/maintain.md): Reference for dex maintain: snapshot a baseline, check schema, volume, grain, and semantic drift, verify a project, and reconcile with proposed diffs.
- [dex config](https://docs.exmergo.com/dex/cli/config.md): Reference for dex config: read every effective setting, validate .dex/config.yml by line, and set or unset keys as reviewable in-place edits that keep comments.
- [dex viz](https://docs.exmergo.com/dex/cli/viz.md): Reference for dex viz preview, which is not yet implemented and returns a not_implemented envelope, with the flags it accepts and the shape of what it prints.
- [dex demo](https://docs.exmergo.com/dex/cli/demo.md): Reference for dex demo: create a seeded local DuckDB warehouse with realistic data quality problems, no credentials or network, to try every dex command on.
- [The command contract](https://docs.exmergo.com/dex/reference/command-contract.md): The dex command contract: every subcommand, the single sanitized JSON envelope it prints, the query firewall, and the rules an agent relies on between calls.
- [Project formats](https://docs.exmergo.com/dex/reference/project-formats.md): The project seam behind dex: the three tiers a project format can satisfy, where edits land, and how to write and prove a new format with conformance tests.
- [Storage backends](https://docs.exmergo.com/dex/reference/storage-backends.md): Where dex keeps its scratch state and how to replace it: the storage tiers, the spend ledger contract, serialized spend admission, and conformance tests.
- [Running the lifecycle across processes](https://docs.exmergo.com/dex/reference/host-integration.md): Split the dex lifecycle across processes: export a verifiable plan, inspect dependencies and edits, apply offline, and read build evidence in a sandbox safely.
- [Evaluation](https://docs.exmergo.com/dex/reference/evaluation.md): How dex is evaluated: unit and safety tests on every change, agent evals against a no-skill baseline, and published results on external analytics benchmarks.
- [Changelog](https://docs.exmergo.com/dex/changelog.md): Release notes for exmergo-dex-core and the dex skills: what was added, changed, and fixed in each of the recent releases, with links to the pull requests.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.