Customer-controlled deployment
Deploy on-premises or in a customer VPC. Your source, regression data, tools, credentials, and surrounding systems stay under customer control.
Governance and security
Autonomy under your control.
Choose where dVI runs, what it can access, which actions need approval, how proof is established, and how usage is limited.
Your controls
Every consequential step has a boundary.
Every closure step follows the limits set for deployment, access, approvals, verification, model usage, and remaining budget.
Isolated change work
Protect the original source while approved investigation and change happen in a separate, controlled copy.
Access and approval
Limit who can start or control work, what dVI can do, and which consequential actions require approval.
Approved verification and replay
Use project-approved checks to prove closure and preserve enough context for controlled reruns, retries, and review.
Usage and capacity limits
Set limits for model usage, elapsed time, attempts, verification runs, concurrent work, and computing resources.
Provider choice and audit
Use approved model providers while keeping actions, approvals, changes, verification, usage, and outcomes inspectable.
Deployment boundary
Keep closure close to the work.
dVI has been deployed on customer premises and is designed for customer-controlled operation. Source, regression evidence, approved runners, credentials, and dVI records retain explicit ownership.
Your deployment boundary
Customer-owned
Source, runner, evidence, tools, credentials
dVI-owned
Closure controls, evidence record, audit, verified outcome
Governed interface
Policy-checked actions, isolated work, approved reruns, usage limits, and visible outcomes.
No hidden outcome
What never happens silently.
- ✓An approved model provider is unavailable
- ✓A proposed change cannot be applied safely
- ✓Reproduction or verification infrastructure fails
- ✓A time or usage limit is reached
- ✓A change is rejected by policy
- ✓A person cancels or takes over the work
Governance working session
Map your policy boundary before the first closure.
Bring one representative regression scope. We will map deployment, approved runners, access, proof, and budget controls.