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.
:46103
π¬ CHAT WITH DATA PLANNED
Bring your own LLM key: prompts orchestrate DVT's capabilities on the fly
and come back as results and charts you can save for later.
:46104
π DATA PROFILING PLANNED
One click adds the profiler package via dvt deps, profiles any supported
adapter, and charts the results.
:46105
β± DVT SCHEDULER PLANNED
Scheduled dvt jobs β your commands on a cron, with history.
:46106
π DVT NOTEBOOKS PLANNED
SQL and Python scratchpads over your connections β try things fast,
save what's worth keeping.
:46107
π DVT DASHBOARDS PLANNED
BI dashboards from basic charts and everything saved out of
Chat with Data β multiple reports, one place.
Air-gapped server? Paste the activation key issued at
getdvt.net β it is verified locally and bound to this machine. No
internet required.
THIS MACHINE
Readingβ¦
Federation compute runs HERE:
cross-engine joins execute in DuckDB on this machine, bounded by these
cores, this RAM and this disk. Size accordingly β extraction is
parallel and pushdown shrinks it, but the join is local.
PROJECT CONNECTIONS
Profileβ¦
Default target
Scoped to THIS project's profile only β
other profiles in profiles.yml are never touched, and every write leaves a
timestamped backup. Secrets display masked and never leave this machine.
AI CREDENTIALS
Keys for the AI features ahead (Chat with Data, Build
with AI). Stored in ~/.dvt, chmod 600, masked here. Heads-up: direct
API keys bill per token.
DVT AI-PROXY Already paying for an AI subscription? AI-Proxy routes
DVT's AI features through the subscriptions you already own instead of
per-token API billing β and reaches offline models via Ollama for
air-gapped deployments. With AI-Proxy configured, every key above
becomes unnecessary.Learn more β
HOSTING β FOR NETWORK ADMINS
Every DVT app binds 127.0.0.1 by default; pass
--host to expose one. Settings writes stay loopback-only no
matter what. Reserved port range: 46100β46109.