Your warehouse is every engine
you already own.
DVT is a dbt-compatible transformation engine that reads from all your databases, computes across them, and lands everything on one target — no cloud warehouse required.
Medallion architecture on the infrastructure you already have.
Raw data stays where it lives
No ingestion, no lake to fill first. sources.yml + meta.connection make every engine's raw tables addressable in place — Postgres, Oracle, Snowflake, all of them at once.
Learn more →
Writes converge on one target
Models read across engines and land on your default target — the engine you choose to be the warehouse. Reads fan out; writes converge. Federation, pushdown and DuckDB compute do the crossing.
Learn more →
A wrapper, not a fork
Stock dbt-core sits at DVT's heart. Your project, your DAG, your macros and tests — untouched. Two new materializations (f_table, f_incremental) are the entire learning curve.
Learn more →
Write it once. DVT speaks every dialect for you.
A federation model is plain SQL. DVT decomposes it per engine, transpiles each extraction into that engine's own dialect — quoting included — pushes your filters down to the source, computes the join, and lands the result. Every extraction is guaranteed to parse on its target engine.
We even publish what doesn't push down →One command, a whole workbench.
dvt serve opens the local suite — every app on its own port, one login-free door, loopback-safe by default.
DATA CATALOG
Cross-engine docs and lineage — every model, source and column across all your connections, one graph.
API PORTAL
Any model becomes a live REST endpoint — executed through federation per request, Denodo-style, with column governance.
DVT SCHEDULER
Your dvt commands on a cron or saved for manual runs — with kill switches, history and honest per-run feedback.
DVT SETTINGS
Account, machine sizing, a no-YAML connection manager for profiles.yml, AI credentials, and the hosting map.
We publish our limitations.
What degrades gracefully, where the hard walls are, and which guarantees are enforced by our test battery across ten dialects — on a public page, kept honest release by release. Engineers notice.
Read the limitations page →Air-gapped? First-class.
Offline machine-bound activation, credential writes that never leave loopback, a published port map for your network admins, and AI features that can run against local models. No phone-home required to do your job.
DVT for the enterprise →Keep your engines. Gain a warehouse.
Free for files and databases. Pay when you connect clouds.