The hub — every DVT app on this machine, one door.
Cross-engine documentation and lineage: every model, source and column across all your connections, one graph.
Switch models on for REST consumption, control column access, and hand out endpoints instead of database credentials.
Martin, the DVT data agent: ask in English, he writes governed SQL and DVT answers it live through federation — tables, charts, saved assets.
Null counts, distincts, min/max and averages for every model and source — computed live through federation, any engine, any bucket.
Your dvt commands on a cron — nightly builds, hourly syncs, scheduled retracts — with history and full logs per run.
Everything saved out of Chat with Martin, on a wall — every card reruns LIVE through federation with one click.
Visual development: connections and default target set from a GUI, sources and models dragged into a query editor as source()/ref(), git sidebar, runner, mini-lineage, data preview — and a Build-with-AI pane.
SQL and Python scratchpads over your connections — try things fast, save what's worth keeping.
Account & subscription, offline activation, this machine's specs, project connections & sync, AI credentials, and the hosting map — one place.