Deployment options
Deploy DT on your infrastructure, including air-gapped environments, or choose a DT-hosted arrangement. Place the application, inference, data, and tools where the work requires them, with clear operating ownership.
Customer-hosted or DT-hosted
Air-gapped deployment available
Explicit operating responsibilities
01 / Hosting arrangements
Choose who runs the platform and where its components live. Either arrangement can serve enterprise or government teams; the right choice follows your infrastructure and operating needs.
Run the application, durable state, workers, and configured execution services on infrastructure you control. The documented Docker Compose stack provides a starting point. Production sizing, hardening, networking, and operational support are scoped for your environment.
Have DT operate the platform under an agreed hosting and support arrangement. We confirm infrastructure location, connectivity, enabled features, data handling, and operating responsibilities during scoping. Discuss dedicated or organization-specific requirements with us.
Scroll the table horizontally to compare arrangements.
| Part of the system | Customer-hosted | DT-hosted |
|---|---|---|
| Application and state | Customer-controlled infrastructure. Customer operates it, with DT implementation or support as agreed. | DT-operated infrastructure. Location, organization setup, and service responsibilities are agreed in scope. |
| Model inference | Configured provider or accessible model endpoint; customer manages credentials and network approval. | Agreed model endpoints and credentials, configured by platform operators. Inference may run separately from the application. |
| Files and working data | Configured customer storage. Customer owns storage access, retention, backup, and recovery operations. | Storage and operational handling defined in the hosting arrangement. Customer defines information policy and permitted use. |
| Tool and computer execution | Configured workers, browser services, and optional sandboxes in the approved topology. Paired computers require separate access decisions. | DT-managed execution services as agreed. Connected apps, private systems, and paired computers retain their own boundaries. |
| Connected systems | Customer authorizes accounts, scopes, and destinations. External systems and model providers process requests under their own terms and configuration. | |
02 / Models and network paths
Platform operators configure providers, model endpoints, routing, and applicable fallback behavior. The model used for an agent can differ from the services used for browsing, document interpretation, or generated media.
We assess the selected endpoint against the intended workflow, tool use, capacity, and network requirements. An accessible endpoint is not evidence that every platform feature works with it.
Document the information sent to models, integrations, email, browser services, and telemetry. Keeping the application on customer infrastructure does not by itself keep all traffic within that boundary.
03 / Air-gapped AI deployment
DT supports air-gapped deployment. The supported configuration places the platform, model inference, and the tools needed for the workflow inside the isolated environment. Select the available capabilities around those internal services.
Configure model access, API and MCP connections, identity, storage, execution, and logging within the boundary. External SaaS connections are replaced with internal alternatives or left disabled in the air-gapped configuration.
Explore internal integrationsEstablish installation artifacts, software and model updates, malware definitions, backup and recovery, and maintenance access. Document the dependencies and test representative work in the target configuration.
Use platform documentation with your own team, or bring in DT engineers for initial consulting, deployment, and integration. Independent advice can also evaluate other approaches.
Explore air-gapped implementation servicesExplore the components and boundaries in our air-gapped AI reference architecture, then use the model update lifecycle guide to plan controlled changes. These educational guides provide evaluation questions to apply to your DT configuration.
04 / Getting to production
A working installation is the beginning of an operating service. Establish the roles, evidence, and support needed to sustain it.
Set information-handling rules, authorize connections, provide infrastructure and identity access where required, and designate administrators and reviewers.
Define acceptance tests, monitoring, incident escalation, upgrades, recovery, and training. Software, hosting, implementation, and support are scoped as distinct commercial components.
Plan an engagementReview Security & Governance with the people responsible for your deployment.
Next steps
Explore the platform around your systems and workflows. Your team can lead implementation, with DT engineering or independent consulting available when you need it.