> ## Documentation Index
> Fetch the complete documentation index at: https://docs.orq.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# BYOK | Bring Your Own Key | AI Gateway

> Bring Your Own Key (BYOK) to the AI Gateway. Connect OpenAI, Anthropic, Google, AWS, and 20+ other providers using your own credentials for full cost control and rate limit ownership.

**BYOK** (Bring Your Own Key) connects provider API keys directly to the **AI Gateway**. Every request is routed through those credentials, keeping billing, rate limits, and data residency under the organization's control.

## Connecting a provider key

1. Go to **BYOK** in the **AI Gateway** sidebar.
2. Find the provider and click <kbd className="key">Connect</kbd>.
3. Select <kbd className="key">Setup your own API key</kbd> and paste the key.

<Frame caption="Configure your API integration based on the criteria set by the provider.">
  <img src="https://mintcdn.com/orqai/HoEQFybclS_NnUdX/images/router-providers-aws-bedrock.png?fit=max&auto=format&n=HoEQFybclS_NnUdX&q=85&s=35458d72c1002d58a1ad412ae7acb586" alt="Providers configuration screen showing provider API key setup options." width="1483" height="1047" data-path="images/router-providers-aws-bedrock.png" />
</Frame>

<Card title="Browse all supported providers" icon="plug" href="/docs/ai-gateway/integrations/providers/overview">
  View the full list of providers available in the **AI Gateway**, including OpenAI, Anthropic, Google, AWS Bedrock, Azure, and more.
</Card>

## Multiple keys per provider

Add more than one key per provider by selecting <kbd className="key">Add a new API key</kbd> from the provider panel.

### Why use multiple keys

**Failover**: if one key is revoked or exhausted, a fallback model configured with a second key keeps requests flowing.

**Environment separation**: use different keys for production, staging, and development without mixing spend.

## Why use own keys

For production workloads, BYOK provides:

* **Rate limit ownership**: provider rate limits apply to the organization's account, not a shared pool
* **Direct billing**: spend is billed by the provider directly; configure limits and alerts independently
* **Data residency**: requests go from the **AI Gateway** to the provider account with no shared credential layer