DATA VIRTUALIZATION TOOLDVT
FeaturesEverything DVT does, honestly benchmarkedUse CasesReal cross-engine problems, solvedEnterpriseAir-gapped, loopback-safe, documentedPricingFree for files & databases — pay for cloudsReleasesWhat shipped, version by version
See everything DVT does
Start HereInstall, first federated model, the conventionsConnectProfiles, sources, every engine you ownModelFederated materializations and the engine underneathThe App SuiteHub, catalog, API portal, chat, profiling, scheduler, explorer, dashboardsTrustLimitations and benchmarks, published honestlyReferenceEvery command, dvt run to dvt killAdaptersEngines DVT connects and federatesBucket StoragesS3, GCS, Azure and the local filesystem
Browse all documentation
DiscordTalk to the team and other users — live nowForumsLong-form questions & answers — comingKnowledge BasePatterns, recipes, gotchas — comingArticles & NewsletterWhat we learn, written down — comingContactReach us directly
Join the Discord
Contact UsGet StartedSign In

START HERE

  • Overview
  • Quickstart
  • dbt Compatibility
  • The Style Guide

CONNECT

  • profiles.yml
  • sources.yml
  • Configuration
  • Supported Databases

MODEL

  • f_table & f_incremental
  • The Federation Engine
  • Predicate Pushdown
  • Execution Paths
  • .sql Models
  • .py Models
  • Seeds, Snapshots & Tests
  • Switching the Default Target

THE APP SUITE

  • Overview
  • The Hub & Settings
  • The Data Catalog
  • The API Portal
  • Chat with Martin
  • Data Profiling
  • The Scheduler
  • Data Explorer
  • Dashboards

TRUST

  • Limitations
  • Benchmarks

REFERENCE

  • CLI Commands

ADAPTERS

  • All Adapters
  • PostgreSQL
  • Snowflake
  • BigQuery
  • Redshift
  • Databricks
  • MySQL
  • MariaDB
  • SQL Server
  • Oracle
  • DuckDB
  • Microsoft Fabric
  • ClickHouse
  • Trino
  • SQLite
  • Amazon Athena

BUCKET STORAGES

  • All Bucket Storages
  • Amazon S3
  • Google Cloud Storage
  • Azure Blob Storage
  • Local Filesystem
OverviewQuickstartdbt CompatibilityThe Style Guideprofiles.ymlsources.ymlConfigurationSupported Databases

CONFIGURATION

DVT configuration is split into two files — one for connections, one for sources.

PROFILES.YML

Database connections, target environments, environment switches vs engine shifts, target resolution, and model config extensions.

SOURCES.YML

Bind every source to its engine with meta.connection — one rule, no exceptions. Common patterns and common mistakes.

PRODUCT

  • Features
  • Pricing
  • Documentation
  • Releases
  • Supported Databases

RESOURCES

  • Quickstart
  • CLI Reference
  • Configuration

COMPANY

  • Contact
  • Enterprise
  • Discord
  • PyPI

LEGAL

  • Terms of Service
  • Privacy Policy
  • License (EULA)

INSTALL

pip install dvt-core
© 2026 Data Virtualization Tool — a MetaThinking product, alongside AI-Proxy. All rights reserved.