Air-gapped deployment

A deployment with no network path to the public internet, used when data must never leave a physically or logically isolated environment.

An air-gapped deployment has no route out to the public internet at all, not a firewalled connection, no connection. Everything the system needs, models, dependencies, updates, has to be brought in through a controlled process rather than fetched live from the network. This is a stricter requirement than a private cloud or an on-premises install that still reaches the internet for updates or provider APIs.

Some regulated environments, defense and intelligence systems, certain government networks, the most sensitive banking workloads, require this level of isolation as a baseline, not an option. A vendor that can only offer a shared cloud service has no path into that kind of environment at all.

A classified or otherwise physically isolated network that cannot exchange traffic with any outside system under any circumstance.

In Dynamiq, fully isolated and air-gapped environments are delivered with Dynamiq's engineers rather than offered as a self-service option, built on top of the standard self-hosted path: your own AWS, Azure, GCP, IBM Cloud, Red Hat OpenShift, or any Kubernetes 1.32+ cluster, or on-prem.

See an agent on your own workflow.

Bring a process and its documents. Our engineers will show you how Dynamiq runs it, in your environment or ours.