Traffic, credentials, infrastructure, and provider charges
- Model request and response bodies
- AWS identity and provider access
- VPC, endpoints, runtime, and counters
- Bedrock usage and the AWS invoice
Keep model traffic, provider credentials, and the AWS bill inside an account you control. AI Gateway HQ supplies the signed release, spending limits, and lifecycle controls without receiving your prompts or long-lived AWS credentials.
The package installs a narrow, release-pinned gateway into your AWS account. Your team can inspect the CloudFormation template, approve every lifecycle action, and remove the stack. AI Gateway HQ can verify the declared stack through a read-only role. AI Gateway HQ cannot deploy, update, or delete resources in your account.
The control plane prepares the release. Your AWS session performs every infrastructure change.
The deployment is part of the software plan, not a separate inference reseller fee.
Review the account, Region, VPC, subnets, routes, model access, service quotas, template, limits, and modeled cost.
The buyer-local launcher uses your active AWS session. AI Gateway HQ never receives a long-lived AWS credential.
Read-only verification confirms the stack and request counter. Updates and removal require explicit buyer approval.
AI Gateway HQ does not add a percentage to the model bill. One deployment is included with Company and Portfolio; the customer pays AWS and Bedrock directly.
The reviewed two-Availability-Zone example has a modeled known subtotal of $44.923464 per month: $44.64 for interface endpoints and $0.283464 for the modeled Bedrock usage. API Gateway, Lambda, DynamoDB, CloudWatch Logs, endpoint data processing, data transfer, taxes, and actual usage are variable and excluded. Review the live preflight before approving a stack.
The release candidate deliberately limits the first buyer-owned path. External-account deployment, renewal update, rollback, first-request, and removal acceptance remain open before general availability.
us-east-1Supported models are Amazon Nova Micro, Nova Lite, and Claude Sonnet 5. The default and frozen cost example use Nova Lite. Claude Sonnet 5 uses AWS's single-region Bedrock Mantle endpoint; Nova uses Bedrock Runtime. The package grants no Marketplace subscription permissions, so the buyer reviews and enables any required third-party model terms and payment in its own AWS account.
No. In the buyer-owned AWS deployment, model request and response bodies stay in the customer's AWS account. The hosted control plane retains entitlement, release, stack, limit, status, and aggregate request-count evidence; it does not receive model traffic or AWS credentials.
No. The data plane runs in the customer's AWS account and VPC, while entitlement, signed-release issuance, and read-only deployment verification remain in the AI Gateway HQ control plane. Disconnected, on-premises, multi-region, and vendor-managed dedicated variants are not included in this release candidate.
One workspace-bound deployment in AWS us-east-1 using Amazon Nova Micro, Nova Lite, or Claude Sonnet 5, with 25 requests per day by default and a hard maximum of 100 requests per day. A no-charge preflight must confirm the exact account, Region, model, and token-count path before deployment. The package is digest-pinned and supports buyer-approved creation, update, verification, and removal. Buyers select and authorize third-party model terms in their own AWS account.
One deployment is included with the $499 monthly Company plan and the $1,500 monthly Portfolio base plan. AI Gateway HQ adds no inference markup. The customer pays AWS and Bedrock charges directly. The reviewed two-Availability-Zone example has a modeled known subtotal of $44.923464 per month; API Gateway, Lambda, DynamoDB, logging, data processing, transfer, taxes, and actual usage vary and are not included in that subtotal.
Review the live cost preflight and release evidence before your AWS account creates anything.