1. Production service providers
- Amazon Web Services, Inc. (United States and configured AWS regions): hosted infrastructure, compute, networking, object and database storage, encryption-key services, secrets storage, identity, monitoring, queues, notification delivery, and transactional email. The current hosted production baseline uses a U.S. AWS region.
- Stripe, Inc. (United States and Stripe service locations): active provider for hosted checkout, payment processing, subscriptions, invoices, the customer billing portal, refunds, disputes, tax calculation where configured, and fraud controls.
- Google LLC (global service locations): Google Analytics measurement for the public marketing site only after the visitor permits analytics. Google Analytics is not intended to receive gateway prompts, outputs, provider credentials, or authenticated tenant configuration.
2. Customer-directed model providers
For BYOK traffic, Customer selects a model provider, supplies credentials tied to Customer's own provider relationship, and instructs AI Gateway HQ to relay eligible requests to that provider. Examples can include Amazon Bedrock, Anthropic, Google, Microsoft Azure, and OpenAI when the corresponding adapter is implemented and enabled. These providers process request content under Customer's account, configuration, region, and agreement; they are not silently selected as a general AI Gateway HQ subprocessor for unrelated traffic.
When AI Gateway HQ offers managed-provider access, the specific provider, model, region, price, and data path must be disclosed in the product before Customer enables it. The current hosted managed Amazon Bedrock catalog includes reviewed conversational models routed within disclosed U.S. AWS Regions and requires settled purchased credit plus a reusable payment method before Customer can enable it. Availability can change when AWS access, model lifecycle, compatibility, or verified pricing changes.
3. Engineering and business systems
GitHub, Inc. hosts the private source repository and isolated continuous-integration workflows used to build, scan, review, and deploy AI Gateway HQ. Production secrets and routine Customer Content are not committed to source control. A deliberately sanitized fixture or redacted diagnostic may be used in engineering only under access controls.
Search-engine webmaster services, including Google Search Console and Bing Webmaster Tools, receive public website URLs, crawl information, and search-performance data. They are not part of authenticated gateway request processing.
4. Scope and customer responsibility
This list covers providers used by AI Gateway HQ to process Customer personal data or Customer Content for the Services and material adjacent systems. It does not list every telecommunications carrier, customer-owned identity provider, customer-owned SIEM, end-user browser, bank, card network, legal adviser, or provider a Customer independently contracts and controls.
Customer must evaluate its selected model providers and integrations. The public roadmap does not make a planned or disabled integration a current subprocessor. An enterprise Order or data processing addendum may provide a narrower approved list, region, advance-change notice, objection process, or customer-VPC boundary.
5. Changes
This page is updated before a new material subprocessor is placed in the production data path when practical. The effective date identifies the current public list. Customers with a contractual notice right receive notice through the method and period stated in their Order or data processing addendum.
Questions, requests, or notices
Use the encrypted contact workflow for account, billing, privacy, cancellation, or legal requests. Do not submit passwords, card data, provider credentials, gateway keys, or sensitive prompt content.