Deployment and infrastructure
Managed, your VPC, on-premises, or air-gapped: what runs where, what it needs, and how it is operated.
- Where does Context run?Managed by Context, in your own VPC, on-premises, or in an air-gapped environment. Endpoints, connectors, updates, and support are configured for the architecture you select.
- What data leaves our boundary?Run traces stay inside your deployment. In a VPC, on-premises, or air-gapped deployment the whole platform runs inside your perimeter; model inference is the one documented cross-boundary flow.
- Is the whole platform inside our perimeter, or just inference?The entire platform. Control plane, execution, and run history deploy in your VPC, on-premises, or air-gapped, not only model inference.
- Which clouds are supported for a VPC deployment?AWS is the reference deployment, delivered to your EKS cluster through Replicated or Helm. An Azure edition is documented. Ask about other clouds.
- How is a self-hosted install delivered?Through the Replicated admin console (license, preflight checks, a short configuration form) or Helm from the umbrella chart. Upgrades are an operator action.
- What do we need in our account before installing?A Kubernetes cluster with a load balancer controller, storage and ingress classes, and an IAM role; PostgreSQL with pgvector, S3-compatible storage, and a document server.
- 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.
- How do updates reach a self-hosted deployment?Connected installs see a new version in the admin console and an operator deploys it. Air-gapped installs side-load release bundles. Nothing updates without your action.
- How are agent sandboxes isolated?Every task run gets its own sandbox under a dedicated controller, with a network posture you set and no standing credentials inside it. The sandbox is discarded after the run.
- What monitoring ships with a deployment?An in-cluster observability stack (metrics, logs, traces, dashboards), trace analytics, and health endpoints. External export is opt-in.
- Who operates what in each deployment model?Managed: Context operates, you govern policy. Your VPC: your cloud controls, operations shared per the design. On-premises and air-gapped: you operate.
The evidence behind these answers is in the Trust Center: read the deep dive →
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 →