DATABASE ADAPTERS

DVT supports every engine that both dbt and Sling support — dbt provides the execution layer for your default target, Sling moves the data during federation. Every adapter below works as a federation source, a federation target, and a seed target.

All drivers are installed automatically by dvt sync based on what your profiles.yml actually uses.

Click any adapter for its setup guide, supported features, and federation notes.

BEYOND ENGINES: PYTHON MODEL SOURCES

Python models run locally and can pull from anything Python reaches — the result lands in your DAG like any other model and materializes to any target above. Like everything in DVT, they're free for individuals. That makes systems without a dbt+Sling adapter first-class sources anyway. Python models docs →

REST APIS

requests

Stripe, HubSpot, internal services — anything with an HTTP endpoint

MONGODB

pymongo

documents → DataFrames

ELASTICSEARCH

elasticsearch-py

search indexes and aggregations

STARROCKS

pymysql

MySQL-wire protocol

EXCEL / LOCAL FILES

pandas

spreadsheets, exports, anything pandas reads

ML INFERENCE

scikit-learn

score, classify, embed — inline in the DAG

Not supported:engines without a Sling connector — Vertica, SingleStore, and self-hosted Spark Thrift — are outside the dbt + Sling intersection and have no native adapter. MongoDB, Elasticsearch, and StarRocks are best reached through Python models (above). Adapters marked SUPPORTED follow the same dbt + Sling rule but haven't been run in our live verification suite yet; VERIFIED adapters are exercised end-to-end (federation source + target, seeds, debug) on every release.