Sovereign by defaultAir-gap · BYO LLM · BYO cloud

AiSOC runs where you do.
Sovereign by default.

Deploy the same MIT-licensed agent loop into an air-gapped network, an on-prem Kubernetes cluster, your VPC on any major cloud, or a sovereign-cloud region. Pick the LLM trust boundary that fits your policy — including a fully local one — and pin data residency to a specific region.

Four control points, in your hands

Air-gap by config flag

Set AISOC_AIRGAPPED=true and the platform refuses to make outbound calls — no LLM provider, no threat-intel feed, no telemetry. The Ollama overlay ships a pinned local model so the demo seed runs end-to-end with zero external calls.

docker-compose.airgap.yml

BYO LLM endpoint

Per-tenant LLM credentials live in the encrypted vault (Fernet AES-128-CBC + HMAC-SHA256). Point a tenant at OpenAI, Anthropic, an Azure deployment, a Bedrock model, or a private LiteLLM gateway — the agent loop is identical.

BYOK + tenant LLM credential vault

Helm + Terraform first-class

A single Helm release deploys every service into your cluster; Terraform modules cover AWS EKS, GCP Cloud Run, and a generic BYOC blueprint. Bring your own VPC, KMS, and IAM — the modules consume them rather than reinventing them.

infra/helm/aisoc · infra/terraform/{aws,gcp,byoc}

Data residency by VPC

Because the entire stack runs in your account, residency is decided by which region you provision into. Pin to eu-west-1, ap-south-1, us-east-2, or any other region your provider exposes — including sovereign-cloud regions.

Operator-controlled provisioning

Deployment matrix

One platform, five deployment modes. Every row maps to a shipping artefact in the repo — no special edition, no enterprise binary, no closed components.

ModeLLM trust boundaryData residencyCompliance postureShipping artefact
Air-gappedLocal Ollama sidecarOperator-definedSOC 2 · ISO 27001 · GDPR · DPDPdocker-compose.airgap.yml
On-premLocal Ollama or BYO endpointOperator-definedSOC 2 · ISO 27001 · GDPR · DPDPHelm chart (infra/helm/aisoc)
HybridCloud APIs · Ollama · BYOEU · US · India · CustomSOC 2 · ISO 27001 · GDPR · DPDPTerraform (infra/terraform/byoc)
Public cloudCloud APIs · BYO endpointEU · US · India · CustomSOC 2 · ISO 27001 · GDPR · DPDPTerraform (infra/terraform/{aws,gcp})
Managed SaaS (waitlist)Cloud APIs (default) · BYOEU · US · IndiaSOC 2 · GDPR (target)tryaisoc.com
Compliance frameworks supported across the matrix:SOC 2ISO 27001GDPRDPDP (India)

Any cloud × any region

Because deployment is operator-controlled (Helm or Terraform into your account), the supported cloud / region pairs are the ones your provider supports — including sovereign-cloud regions.

CloudUSEUIndiaSingaporeCustom
AWS
Azure
GCP
OCI
DigitalOcean
Hetzner

“Custom” covers sovereign-cloud regions (e.g. AWS GovCloud, Azure Germany, OVH, Scaleway, IBM Cloud) and on-prem Kubernetes clusters reachable from your operator network.

Talk to us about sovereign deployment

Tell us the cloud, region, LLM trust boundary, and compliance regime you need to land. We'll point you at the right Helm values, Terraform module, or air-gap overlay — and stay on the line for the first deployment.