The runtime in your VPC
Self-hosting
Mynd Self-Hosted runs the identical stack — runtime, context graph, trust kernel — inside your network, for organizations whose data cannot transit a third party. It is the same images we run, not a feature-trimmed edition. Available on Enterprise agreements.
Topology
The control plane (key management, billing metering, release distribution) stays with Mynd; the data plane (runs, graph, traces, files) runs entirely on your infrastructure. No prompt, document, or trace leaves your boundary — the control-plane link carries licensing heartbeats and signed release manifests only.
Requirements
| component | minimum |
|---|---|
| Kubernetes | 1.29+, 3 nodes for HA |
| GPU pool | 8× A100/H100-class for y0-fast + y0-deep serving |
| Postgres | 15+, 500 GB, for graph metadata and audit log |
| Object storage | S3-compatible, for files and traces |
| Egress | HTTPS to control.myndlabs.ai only (heartbeat + releases) |
Install
helm repo add mynd https://charts.myndlabs.ai helm install mynd mynd/runtime \ --namespace mynd --create-namespace \ -f values.yaml # license, GPU pool, storage bindings mynd-admin verify # checks kernel attestation and model checksums
Operations
Releases arrive as signed manifests; you choose the window and `mynd-admin upgrade` performs a rolling update with automatic rollback on failed health checks. The audit log is append-only at the storage layer. Air-gapped installs are supported with a quarterly offline release bundle; the licensing heartbeat then runs against a local token with a 90-day validity window.