Deployment modes
InfraSage has three deployment shapes, chosen at install time. In BYOC and self-hosted modes, no customer telemetry ever reaches InfraSage-managed infrastructure. That is a hard architectural boundary, not a policy claim: the engine, ClickHouse, and LLM invocation all happen inside your VPC.
BYOC (Bring Your Own Cloud): recommended for regulated buyers
You deploy the Helm chart into your K8s cluster; you own the AWS/GCP/Azure account; your telemetry never traverses InfraSage-controlled infrastructure.
Data residency: guaranteed. Your data stays in whichever region your K8s cluster is provisioned in.
Setup:
- 1 Kubernetes cluster (any provider, minimum 3 nodes for HA CH/keeper)
- 1 ClickHouse StatefulSet (grows to sharded cluster past ~50 services)
- 1 AWS Bedrock account (Anthropic Sonnet + Haiku)
- Optional: Redpanda broker for high-volume ingest
Install:
helm repo add infrasage https://helm.infrasage.dev
helm install infrasage infrasage/infrasage \
--set clickhouse.storage=200Gi \
--set aiopsEngine.env.BEDROCK_REGION=eu-west-1 \
--set aiopsEngine.env.BEDROCK_INFERENCE_PROFILE=... \
-n infrasage --create-namespace
What InfraSage sees from you: license activation ping (every 24h) and aggregate usage counters (RCAs/day, tenants, service count). No customer telemetry, no RCA content.
Self-hosted (no license activation)
Same as BYOC but with no license ping, for air-gapped environments or customers who prefer zero outbound egress.
Additional constraints:
- Requires offline license key
- Container images must be pulled and mirrored to your registry (see
scripts/airgap-bundle.sh, shipping Q4 2026) - Optional: local-LLM mode via
LOCAL_LLM_MODE=1(llama.cpp / ollama endpoints supported)
Managed SaaS (not yet available, Q1 2027 target)
InfraSage hosts a single-tenant ClickHouse per customer + shared Bedrock account. You point your OTLP collector at api.infrasage.dev/v1/* with your API key.
Data residency: customer chooses region at signup (us-east-1, eu-west-1, ap-south-1); data pinned to that region.
When to pick this: SMB / mid-market who wants zero infra ops burden and doesn't have a residency mandate.
Comparison
| BYOC | Self-hosted | Managed SaaS | |
|---|---|---|---|
| Telemetry residency | Your VPC | Your VPC (air-gap) | Region of your choice |
| Ops burden on you | High (you run CH cluster) | High + no auto-updates | Zero |
| LLM cost billing | Your Bedrock account | Your Bedrock (or local LLM) | Bundled in InfraSage subscription |
| SOC-2 attestation applies to | Your cluster | Your cluster | InfraSage-managed infra |
| Cross-tenant vectorizer opt-in available | Yes (per DPA) | Not applicable | Yes |
| Suitable for | F500, regulated, EU/APAC residency | Air-gapped, federal, defense | SMB, mid-market |