Tenant-scoped authorization
Tenant context is mandatory across current data access, queue, encryption, audit, and policy paths.
See what is deployed today, what requires a customer agreement, and who is responsible for each part.
Tenant context is mandatory across current data access, queue, encryption, audit, and policy paths.
The hosted production cell uses KMS encryption context per tenant and credential. Plaintext is short-lived and excluded from telemetry.
Gateway code does not persist prompt/response bodies or tool schemas, arguments, and results. Events contain identity, route, policy, bounded tool names/types/MCP hosts, usage, cost, and timing metadata.
Production changes pass protected GitHub OIDC deployment, signed-release, infrastructure-plan, CodeQL, dependency, and release scans.
Good architecture reduces later rework. Certification still requires sustained operations, documented proof, remediation, legal review, independent testing, and an audit.
Threat model, data inventory, least privilege, encryption, audit logs, incident response, backups, change records, and vulnerability handling.
Penetration test, policy review, vendor assessment, evidence sample, and legal and insurance review.
An independent SOC 2 audit program and any BAA require separate legal, operating, security, and customer-scope review. Neither is offered today.
AI Gateway HQ operates a hosted production gateway with published pricing and Stripe-hosted self-service billing. Managed Amazon Bedrock is limited to reviewed U.S. conversational models and requires purchased credit plus a reusable payment method. Security controls and evidence collection support SOC 2 readiness work, but no independent SOC 2 audit has been completed or scheduled. AI Gateway HQ does not offer a BAA or claim HIPAA compliance today. It also does not claim PCI certification, FedRAMP authorization, or a general-availability SLA. Any future assurance claim requires the applicable contracts, sustained operations, independent testing, and audit work.