Skip to content

docs: Add Gemini Enterprise (Vertex AI) BYOLLM documentation #407

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
hongyi-chen wants to merge 3 commits into
base: main
Choose a base branch
from
Open

docs: Add Gemini Enterprise (Vertex AI) BYOLLM documentation #407

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
a49e0c1
docs: Add Gemini Enterprise (Vertex AI) BYOLLM documentation
hongyi-chen Jul 28, 2026
b6f3254
docs: fix cloud-agent accuracy, 80% credit claim, and model picker label
oz-agent Jul 29, 2026
658aef1
Merge branch 'main' into docs/gemini-enterprise-byollm
hongyi-chen Jul 29, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/content/docs/agent-platform/inference/bring-your-own-api-key.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@ Warp offers several ways to bring your own AI infrastructure. Use this table to
| --- | --- | --- |
| **Bring Your Own API Key** (BYOK) | Use your own API key for OpenAI, Anthropic, or Google models. Keys are stored locally on your device. | Free and all eligible paid plans |
| **[Custom inference endpoint](/agent-platform/inference/custom-inference-endpoint/)** | Connect Warp to an OpenAI-compatible endpoint such as OpenRouter, LiteLLM, z.ai, or an internal gateway. | Free and all eligible paid plans |
| **[Bring Your Own LLM](/enterprise/enterprise-features/bring-your-own-llm/)** (BYOLLM) | Enterprise-managed inference through your cloud provider (AWS Bedrock today; Azure Foundry and Google Vertex coming soon), with Warp handling routing, orchestration, governance, and observability. | Enterprise only |
| **[Bring Your Own LLM](/enterprise/enterprise-features/bring-your-own-llm/)** (BYOLLM) | Enterprise-managed inference through your cloud provider (AWS Bedrock and Gemini Enterprise on Vertex AI today; Azure Foundry coming soon), with Warp handling routing, orchestration, governance, and observability. | Enterprise only |

@JaidenRatti JaidenRatti Jul 30, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: this can be "and Gemini Enterprise Agent Platform". i dont think "on vertex" makes sense (though i think its fine if we add vertex in brackets like in custom-inference-endpoint.mdx since ppl prob still think of it as vertex).

| **[SuperGrok subscription](/agent-platform/inference/grok-subscription/)** | Connect your SuperGrok subscription to use Grok models through your xAI account. Tokens are stored locally on your device. | Free and all eligible paid plans |

See [Warp pricing](https://www.warp.dev/pricing) for current plan availability.
Expand Down
4 changes: 2 additions & 2 deletions src/content/docs/agent-platform/inference/custom-inference-endpoint.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -119,7 +119,7 @@ Warp itself never stores your endpoint API key. Review your endpoint provider's

The custom inference endpoints described on this page are configured at the **user level** on every plan. Each user adds their own endpoint locally, and it works only for interactive requests, not [cloud agents](/platform/).

Enterprise teams can also configure **team-managed custom endpoints** centrally: an admin sets shared endpoints in the [Admin Panel](/enterprise/team-management/admin-panel/), and they work for both interactive requests and cloud agents. See [Team-managed API keys and endpoints](/enterprise/enterprise-features/team-managed-keys-and-endpoints/), or [Bring Your Own LLM](/enterprise/enterprise-features/bring-your-own-llm/) for AWS Bedrock routing.
Enterprise teams can also configure **team-managed custom endpoints** centrally: an admin sets shared endpoints in the [Admin Panel](/enterprise/team-management/admin-panel/), and they work for both interactive requests and cloud agents. See [Team-managed API keys and endpoints](/enterprise/enterprise-features/team-managed-keys-and-endpoints/), or [Bring Your Own LLM](/enterprise/enterprise-features/bring-your-own-llm/) for AWS Bedrock or Gemini Enterprise (Vertex AI) routing.

## How custom inference endpoints differ from BYOK and BYOLLM

Expand All @@ -129,7 +129,7 @@ Warp offers three ways to bring your own AI infrastructure. Use this table to pi
| --- | --- | --- |
| **[Bring Your Own API Key](/agent-platform/inference/bring-your-own-api-key/)** (BYOK) | Use your own API key for OpenAI, Anthropic, or Google models. Keys are stored locally on your device. | Free and all eligible paid plans |
| **Custom inference endpoint** | Connect Warp to an OpenAI-compatible endpoint such as OpenRouter, LiteLLM, z.ai, or an internal gateway. | Free and all eligible paid plans |
| **[Bring Your Own LLM](/enterprise/enterprise-features/bring-your-own-llm/)** (BYOLLM) | Enterprise-managed inference through your cloud provider (AWS Bedrock today; Azure Foundry and Google Vertex coming soon), with Warp handling routing, orchestration, governance, and observability. | Enterprise only |
| **[Bring Your Own LLM](/enterprise/enterprise-features/bring-your-own-llm/)** (BYOLLM) | Enterprise-managed inference through your cloud provider (AWS Bedrock and Gemini Enterprise on Vertex AI today; Azure Foundry coming soon), with Warp handling routing, orchestration, governance, and observability. | Enterprise only |

Platform credits may apply for local agent runs on Business and Enterprise when using BYOK, a custom inference endpoint, or BYOLLM. See [platform credits](/support-and-community/plans-and-billing/platform-credits/).

Expand Down
18 changes: 12 additions & 6 deletions src/content/docs/enterprise/enterprise-features/bring-your-own-llm.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,16 +1,21 @@
---
title: Bring Your Own LLM
description: >-
Route Warp's agents through your AWS Bedrock models for billing control and
infrastructure flexibility.
Route Warp's agents through your own AWS Bedrock or Google Cloud (Gemini
Enterprise) models for billing control 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 can use Warp's agents while routing inference through models hosted in your AWS Bedrock environment.
Warp supports **Bring Your Own LLM (BYOLLM)** for enterprise teams that need to run inference on their own cloud infrastructure. With BYOLLM, your team can use Warp's agents while routing inference through models hosted in your AWS Bedrock environment or your Google Cloud project.

This gives you control over cloud spend and model hosting, without changing how your team works in Warp.

## Supported providers

* **AWS Bedrock** - Route inference through 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. Setup is covered on this page.
* **Gemini Enterprise (Vertex AI)** - Route inference through your Google Cloud project using short-lived Workload Identity Federation credentials. See [BYOLLM: Gemini Enterprise](/enterprise/enterprise-features/byollm-gemini-enterprise/) for setup.

:::caution
BYOLLM currently supports **AWS Bedrock** only. Coming soon: Azure Foundry and Google Vertex support.
Azure Foundry support is coming soon. The rest of this page covers the AWS Bedrock configuration.

@JaidenRatti JaidenRatti Jul 30, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i think its a little confusing that the bring your own llm page explains the aws bedrock config - but its a separate page for just BYOLLM: Gemini Enterprise? Maybe they can both be their own pages?

:::

:::note
Expand Down Expand Up @@ -58,7 +63,7 @@ This approach ensures access management stays with your cloud provider, giving a

### Model availability

BYOLLM supports the intersection of models that Warp supports and models available on AWS Bedrock. Currently, only **Claude models** (Anthropic) are available through AWS Bedrock. OpenAI and Google models are not available on Bedrock.
BYOLLM supports the intersection of models that Warp supports and models available on your provider. On AWS Bedrock, only **Claude models** (Anthropic) are available; OpenAI and Google models are not available on Bedrock. To route Gemini models (or Claude partner models on Vertex AI) through your Google Cloud project, use [Gemini Enterprise BYOLLM](/enterprise/enterprise-features/byollm-gemini-enterprise/) instead.

To determine which models you can use with BYOLLM:

Expand Down Expand Up @@ -338,7 +343,7 @@ However, when using BYOLLM:

**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) using cloud-native IAM. Admins configure it at the admin level and it applies to the entire team.
**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. The table below compares BYOLLM with the self-serve, user-level form of BYOK. For a side-by-side comparison that also includes team-managed keys and endpoints, 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).

Expand Down Expand Up @@ -372,6 +377,7 @@ Yes. Admins can configure routing policies to require specific models to use BYO

## Related resources

* [BYOLLM: Gemini Enterprise (Vertex AI)](/enterprise/enterprise-features/byollm-gemini-enterprise/) — Route inference through your Google Cloud project
* [Bring Your Own API Key](/agent-platform/inference/bring-your-own-api-key/)
* [Team-managed API keys and endpoints](/enterprise/enterprise-features/team-managed-keys-and-endpoints/) — Enterprise admins configure shared provider keys and custom endpoints for the team
* [Model Choice](/agent-platform/inference/model-choice/) — Full list of supported models
Expand Down
Loading
Loading