Run the same civilization locally, in ChatGPT Hosting, Cloudflare, AWS, or Azure while keeping credentials, runtime state, and model execution inside the selected trust boundary.
Conversations, governance schemas, and connector contracts can move between deployment profiles. Credentials remain in the profile’s own secret boundary and are never exported during migration.
Optional · not connected
Sovereign Server (Docker Compose)
This is the current recommended always-on profile. Do not install it for an ordinary browser session. Use it when cognition, autonomous missions, external connectors, or a multi-model portfolio must survive browser closure.
1
Prepare the hostInstall Docker and clone the Compacitas repository.
2
Pair onceCreate a 64-character token in Chat connection setup and save it as secrets/sites.token.
3
Mount runtime filesCopy config.example.json, use container paths, and provide an approved llama-server binary plus a durable state/model volume.
4
Start the nodedocker compose -f apps/embassy/packages/sovereign-node/compose.yaml up -d --build
Identity
Single local operator
Runtime
unreported
Secrets
Owner-readable files or container secrets
Use
Closed-tab, always-on operation
Docker is recommended today, but it is not the only runtime: native Python, Linux systemd, Windows, and Kubernetes profiles are included. No macOS .app is required.
The authenticated Sites edge protects operator APIs; encrypted D1 records coordinate either this browser session or a paired outbound Sovereign Server. ChatGPT Hosting never receives local model files or connector credentials.
Identity
Authenticated ChatGPT operator
Secrets
Hosting environment + browser/server boundary
Use
Private hosted pilot
The worker pairing is a scoped connector, not a general remote shell.Production gate required
Cloudflare B2C
The application bundle is Cloudflare-native, but a public B2C release still needs tenant identity, per-user encryption keys, a managed secret vault, quotas, billing, abuse controls, and data-region policy.
Identity
Customer IdP / Cloudflare Access
Secrets
Managed per-tenant vault
Use
Future multi-tenant production
It is not yet safe to expose the operator bypass or a shared worker to B2C users.Reference architecture
AWS
Run the web and Multiplex Genesis images as separate ECS services. Keep the runtime in private subnets, inject secrets from Secrets Manager, persist evidence outside ephemeral task storage, and permit outbound relay only.
Identity
Cognito or enterprise OIDC
Runtime
ECS/Fargate private workers
Secrets
AWS Secrets Manager + KMS
Use
Single-tenant evaluation; future B2C
Production requires the tenant-aware storage adapter and isolation gates documented in the repository.Reference architecture
Azure
Run the two images as separate Azure Container Apps. Use managed identity and Key Vault references, keep Multiplex internal-only, persist its state on an approved volume, and expose only the web ingress.
Identity
Microsoft Entra External ID / OIDC
Runtime
Private Container Apps workers
Secrets
Azure Key Vault
Use
Single-tenant evaluation; future B2C
Production requires the same tenant, recovery, quota, and evidence-isolation gates as every B2C profile.
One connector interface does not mean one universal key.
Every adapter presents the same configure, test, status, rotate, and revoke experience. Independent services still issue independent credentials; collapsing them into one bearer secret would create a dangerous single point of compromise.