Sub-processors
InfraSage relies on the third-party services below to operate the platform. In BYOC and self-hosted deployments, most of these are not applicable: the customer owns the AWS/Anthropic contract directly.
Data-plane sub-processors (touch customer telemetry)
| Sub-processor | Purpose | Data touched | BYOC | Self-hosted | SaaS |
|---|---|---|---|---|---|
| AWS (customer account) | Bedrock LLM inference, S3 backups | Prompt + tool responses sent to Claude Sonnet/Haiku; RCA outputs | ✅ Customer contract | ✅ Customer contract | Under InfraSage AWS agreement |
| Anthropic (via Bedrock) | Claude Sonnet/Haiku model inference | Prompts (with PII redacted) + completions | ✅ Customer contract | ✅ Customer contract | ✅ Under InfraSage BAA |
BYOC/self-hosted: you own the AWS + Anthropic-via-Bedrock relationship directly. InfraSage never sees your telemetry.
SaaS: InfraSage acts as sub-processor of your data to Anthropic-via-Bedrock, per AWS Bedrock Data Privacy terms.
Control-plane sub-processors (do NOT touch customer telemetry)
| Sub-processor | Purpose | Data touched |
|---|---|---|
| Cloudflare | DNS, CDN for infrasage.dev, console.infrasage.dev, api.infrasage.dev, docs.infrasage.dev | Public HTTPS traffic metadata (IP, User-Agent). No customer telemetry passes through Cloudflare; telemetry ingest is direct-to-gateway |
| GitHub | Source code, container registry (ghcr.io) for engine + UI images | No customer data. Images are cosign-signed |
| AWS SES + SMTP fallback | Email notifications (invites, incidents, RCA digests) | Email addresses + notification content (which references service names) |
| Vanta / Drata (planned) | SOC-2 attestation workflow | Access-review metadata and vendor evidence; no customer telemetry |
Integrations you may enable (opt-in per tenant)
InfraSage does not integrate with any of these automatically. Each one requires an explicit per-tenant credential and only touches data you route through it.
| Integration | Purpose | Direction |
|---|---|---|
| Slack, Microsoft Teams | Alert + RCA delivery, chat-ops | Outbound (webhook) |
| PagerDuty, OpsGenie | Alert escalation | Outbound (API) |
| Jira, Linear | Ticket creation from alerts | Outbound (API) |
| GitHub | RCA cross-reference to deploys, source-code context | Read-only |
| ArgoCD, Kubernetes API | Live-infra investigation (kubectl-equivalent reads) | Read-only |
| Datadog, Grafana, Prometheus, Loki, Tempo | Additional telemetry sources | Read-only ingest |
Change notification
We commit to notifying customers 30 days in advance of adding any new data-plane sub-processor or expanding the scope of an existing one. Subscribe at [email protected] with subject subprocessor-updates to receive advance notice.
Last updated
This list is reviewed quarterly. Last update: 2026-08-23.