Can Context run fully air-gapped?
Yes. Release bundles and images are side-loaded into your registry, sandbox egress is closed or allow-listed, and open-weight models are served inside the boundary.
Air-gapped deployment exists for environments designed for disconnected operation. The entire platform deploys inside the boundary: control plane, execution, the context filesystem, and run history. Installs use an air-gap bundle pushed to your own container registry, and updates arrive the same way.
Model inference runs on open-weight models served inside the boundary, because a disconnected environment cannot call a commercial API; the trade for total isolation is the model catalog available inside it. Sandbox network access is set to workspace-only or a domain allow-list.
Written for deployment engineers, it and security. Last reviewed 2026-09-15.
Related questions
Still need an answer?
Tell us what you were looking for and we reply within one business day.
Contact the team →Running a security review?
Documents, controls, and the request form live in the Trust Center.
Open the Trust Center →