> For the complete documentation index, see [llms.txt](/llms.txt).
> Markdown versions of each page are available by appending .md to any URL.

# Bring Your Own LLM

BYOLLM routes Warp's agents through your own AWS Bedrock or Google Cloud (Gemini Enterprise) environment for billing control, data locality, and infrastructure flexibility.

Warp supports **Bring Your Own LLM (BYOLLM)** for Enterprise teams that need to run inference on their own cloud infrastructure. With BYOLLM, your team keeps using Warp’s agents as usual, while eligible requests route through models hosted in your own cloud account instead of Warp’s direct provider integrations.

This gives you control over cloud spend, model hosting, and data locality, without changing how your team works in Warp. Admins configure BYOLLM centrally in the [Admin Panel](/enterprise/team-management/admin-panel/) — team members don’t need to change anything about how they use Warp (unless your admin asks them to opt in; see each provider’s page for details).

Note

BYOLLM is only available on Warp’s Enterprise plan. [Contact sales](https://www.warp.dev/contact-sales) to learn more.

## Supported providers

BYOLLM supports two cloud providers today, each with its own dedicated setup guide:

-   **[BYOLLM: AWS Bedrock](/enterprise/enterprise-features/byollm-aws-bedrock/)** - Route inference through Claude models hosted in your AWS account. Interactive requests use each member’s AWS CLI session credentials, and cloud agent runs assume an IAM role via OIDC.
-   **[BYOLLM: Gemini Enterprise (Vertex AI)](/enterprise/enterprise-features/byollm-gemini-enterprise/)** - Route inference through Gemini and Claude partner models hosted in your Google Cloud project, using short-lived Workload Identity Federation (WIF) credentials rooted in the member’s Warp session.

Caution

Azure Foundry support is coming soon.

Use the comparison below to pick a provider, then follow its setup guide for configuration steps.

| Aspect | AWS Bedrock | Gemini Enterprise (Vertex AI) |
| --- | --- | --- |
| Models | Claude (Anthropic) | Gemini (native) and Claude (Vertex AI partner models) |
| Credential mechanism | AWS CLI session (interactive); IAM role via OIDC (cloud agents) | Workload Identity Federation (WIF), rooted in the Warp session |
| Works with cloud agents | Yes | Not yet (planned) |
| Setup guide | [BYOLLM: AWS Bedrock](/enterprise/enterprise-features/byollm-aws-bedrock/) | [BYOLLM: Gemini Enterprise](/enterprise/enterprise-features/byollm-gemini-enterprise/) |

## Key features

-   **Cloud-native credentials** - No long-lived API keys stored by Warp. Each provider uses its own cloud-native identity mechanism — see the provider pages for details.
-   **Admin-controlled routing and models** - Admins choose exactly which models route through your cloud account, with the option to disable direct provider access entirely.
-   **Consolidated billing** - Inference costs are billed directly to your cloud account (AWS or Google Cloud), leveraging your existing cloud commitments.

## How BYOLLM works

When BYOLLM is enabled for a model, Warp redirects eligible inference calls to your configured cloud provider instead of using model providers’ direct APIs. The model runs in your cloud account, and the response streams back to the Warp client (or cloud agent worker, for providers that support it).

Each provider has its own request flow, credential lifecycle, and setup process. See [BYOLLM: AWS Bedrock](/enterprise/enterprise-features/byollm-aws-bedrock/#how-it-works) or [BYOLLM: Gemini Enterprise](/enterprise/enterprise-features/byollm-gemini-enterprise/#how-it-works) for the full details.

## Billing behavior

BYOLLM-routed inference **consumes no credits** — Warp doesn’t charge credits for requests that execute in your cloud. Inference costs are billed directly to your cloud account. Local agent runs that use BYOLLM still consume [platform credits](/support-and-community/plans-and-billing/platform-credits/) for Warp’s platform infrastructure.

See each provider’s page for provider-specific routing and fallback behavior: [AWS Bedrock](/enterprise/enterprise-features/byollm-aws-bedrock/#routing-and-fallback-behavior) or [Gemini Enterprise](/enterprise/enterprise-features/byollm-gemini-enterprise/#routing-and-fallback-behavior).

## FAQ

### How is BYOLLM different from BYOK?

**BYOK (Bring Your Own API Key)** lets individual users add their own API keys for direct model provider access (e.g., Anthropic, OpenAI, Google). Warp stores keys locally on the user’s device.

**BYOLLM (Bring Your Own LLM)** routes inference through your organization’s cloud infrastructure (AWS Bedrock or Google Cloud via Gemini Enterprise) using cloud-native IAM. Admins configure it at the admin level and it applies to the entire team.

Enterprise admins can also centrally manage BYOK itself: [team-managed API keys and endpoints](/enterprise/enterprise-features/team-managed-keys-and-endpoints/) let an admin configure shared provider keys and OpenAI-compatible endpoints that are stored server-side and work for both interactive requests and cloud agents. For a side-by-side comparison across all of Warp’s bring-your-own-infrastructure options, see [How team-managed providers differ from self-serve BYOK and BYOLLM](/enterprise/enterprise-features/team-managed-keys-and-endpoints/#how-team-managed-providers-differ-from-self-serve-byok-and-byollm).

| Feature | BYOK | BYOLLM |
| --- | --- | --- |
| Configuration level | User | Admin/Team |
| Authentication | API keys (local) | Cloud-native IAM (AWS) or Workload Identity Federation (Google Cloud) |
| Billing | Direct to provider | Your cloud account |
| Data locality | Provider infrastructure | Your cloud infrastructure |

### Does BYOLLM work with Auto?

Auto model selection is disabled if an admin disables **any** Direct API model, regardless of BYOLLM configuration. When Direct API models remain enabled and BYOLLM is configured, Auto picks the best model for the task; if the selected model is enabled for your configured provider, the request routes through your cloud account.

### What data does Warp store? Do you store our cloud credentials?

Warp **does not store or log** your cloud credentials for either provider. Credentials are used transiently, or minted as short-lived tokens, to authenticate requests and are never persisted on Warp’s servers. See the [AWS Bedrock](/enterprise/enterprise-features/byollm-aws-bedrock/#security-and-data-handling) or [Gemini Enterprise](/enterprise/enterprise-features/byollm-gemini-enterprise/#security-and-data-handling) security sections for provider-specific detail.

### Can admins enforce provider-only routing?

Yes. Admins can disable Direct API access for models on the **Models** page so eligible requests only route through your cloud account. Note that disabling any Direct API model also disables Auto model selection.

## Related resources

-   [BYOLLM: AWS Bedrock](/enterprise/enterprise-features/byollm-aws-bedrock/) - Route inference through your AWS account
-   [BYOLLM: Gemini Enterprise (Vertex AI)](/enterprise/enterprise-features/byollm-gemini-enterprise/) - Route inference through your Google Cloud project
-   [Team-managed API keys and endpoints](/enterprise/enterprise-features/team-managed-keys-and-endpoints/) - Admin-configured shared provider keys and custom endpoints
-   [Bring Your Own API Key](/agent-platform/inference/bring-your-own-api-key/) - Self-serve, user-level API keys
-   [Model Choice](/agent-platform/inference/model-choice/) - Full list of supported models
-   [Admin Panel](/enterprise/team-management/admin-panel/) - Configure team settings
-   [Contact sales](https://www.warp.dev/contact-sales) - Get help with Enterprise setup