CLI COMMANDS
If you know dbt, you already know most of this page — every dbt command works in DVT with the same flags and the same semantics, so dvt run, dvt test and dvt compile do exactly what your muscle memory says. On top of that parity DVT adds verbs of its own: for reaching across engines, for keeping a project healthy, and for the app suite.
Each page below opens with the command in action — real invocation, real output — and ends with the full flags table. Start with the group that matches what you're doing.
BUILD & RUN
The transformation verbs. Same flags, same semantics you already know — federation just comes along.
Execute your models in DAG order — cross-engine models run like any other.
Seeds, models, snapshots and tests in one DAG-ordered pass, honest about every skip.
Bulk-load CSV, Parquet, JSON and JSONL seeds to any output — buckets included.
Run your data tests on the target, exactly as you know it.
Capture type-2 history for changing sources.
See the SQL before it runs; build the manifest and hear about problems early.
INSPECT
Look before you leap: what exists, what a query returns, whether the wiring holds.
CROSS-ENGINE EDGE
The verbs dbt doesn't have — where owning a federation engine starts to pay.
Introspect a connection — database or bucket — and write its sources.yml for you.
Refresh, inspect and export source catalogs without ever touching sources.yml.
The mirror of build: remove everything the project materialized, ledger-accurate, in reverse order.
Move the default target and transpile your SQL to the new dialect — deterministically.
One engine-native SQL statement on any named connection, verbatim, from your terminal.
PROJECT HEALTH
One shared diagnosis, two verbs: one that only tells the truth, one that acts on it.
SETUP & APPS
From empty folder to a running app suite — and the agent that lives in both.
Scaffold a project that builds in seconds — DuckDB default target, no warehouse, no prompts.
Self-healing environment: scan profiles.yml and install exactly what your outputs need.
The whole app suite on one pinned port — catalog, chat, API portal, dashboards and more.
Martin in your terminal — the same agent as the suite's /chat, every edit gated behind apply.
Sign in through the browser, check your license, sign out — credentials stored locally.