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
DVT's AI features (Chat with Martin, Build with AI ahead) run
through one outlet: AI-Proxy — a self-hosted OpenAI-compatible
gateway over the subscriptions you already own (Claude, Gemini, ChatGPT,
Codex) and local Ollama for air-gapped floors. Individuals run it on
their machine; on-prem, one connected box runs it and everyone reaches
models over the internal network. No per-token API keys in DVT, ever.
The credential is stored in ~/.dvt, chmod 600, write-only; TEST
asks the gateway for its model list.
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 other
credential becomes unnecessary.Learn more →
HOSTING — FOR NETWORK ADMINS
ONE server per project: dvt serve hosts the
whole suite on this project's sticky port (first free in
46100–46149, remembered in .dvt/suite_port; pin it with
suite_port: in dvt_project.yml). Every app is a path on
that one origin. Binds 127.0.0.1 by default; pass --host
to expose it. Non-local Host headers are refused suite-wide
(DNS-rebinding guard); settings and other writes stay
loopback-only no matter what.