docs: Add Gemini Enterprise (Vertex AI) BYOLLM documentation - #407
docs: Add Gemini Enterprise (Vertex AI) BYOLLM documentation#407hongyi-chen wants to merge 3 commits into
Conversation
- New page: enterprise/enterprise-features/byollm-gemini-enterprise - Update BYOLLM overview page with supported providers section - Refresh stale 'AWS Bedrock only / Google Vertex coming soon' claims across pricing FAQs, BYOK, custom inference endpoint, enterprise billing, admin panel, security overview, and platform FAQs - Add sidebar entry Co-Authored-By: Oz <oz-agent@warp.dev>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![warp-agent-staging[bot]](https://avatars.githubusercontent.com/in/2196476?s=60&v=4){kind=small}
There was a problem hiding this comment.
Overview
This PR establishes a dedicated Gemini Enterprise BYOLLM page, places it correctly beside the existing BYOLLM overview, and adds useful cross-links across Enterprise, inference, and billing content. The WIF, IAM, model-routing, and credential-lifecycle descriptions align with the shipped client and server implementation; publication still needs release-state, billing, cloud-agent-support, and verified-UI-surface corrections.
Concerns
Messaging and accuracy — Clarify whether the public launch is intentional while the current production feature flag remains disabled, reconcile AI-credit and platform-credit language, and remove or verify the model-details UI claim.
Information architecture — The new page and sidebar placement are appropriate, and the AWS/Gemini pages now cross-link bidirectionally. Update the provider comparison table so its cloud-agent column does not imply that Gemini Enterprise supports cloud agents.
Tone and style — The new content follows the major frontmatter, header, callout, link, Settings-path, and second-person rules. The changed-file style lint reported glossary/unrecognized-term warnings and pre-existing hardcoded product-name variables; none identified a material new formatting defect.
Verdict
Checks: CI ✅ · internal links ✅ (3,204 checked) · changed-file style lint
Found: 0 critical, 3 important, 1 question
Request changes before publishing
Review run
https://oz.staging.warp.dev/runs/019faaca-2a9f-706b-bce4-d0b579f56ef3
| Gemini Enterprise is one of the providers supported by [Bring Your Own LLM (BYOLLM)](/enterprise/enterprise-features/bring-your-own-llm/). For AWS-based routing, see the [AWS Bedrock BYOLLM setup](/enterprise/enterprise-features/bring-your-own-llm/). | ||
|
|
||
| :::note | ||
| Gemini Enterprise BYOLLM is only available on Warp's Enterprise plan and requires Warp `v0.2026.06.17` or later. [Contact sales](https://www.warp.dev/contact-sales) to learn more. |
There was a problem hiding this comment.
❓ [QUESTION] Is this page intended to launch publicly now? The current production configuration keeps gemini_enterprise disabled, and v0.2026.06.17 is the client-compatibility threshold rather than an availability guarantee. Please confirm the release state; otherwise label the feature as preview/unavailable or hold the public page.
There was a problem hiding this comment.
we're going to launch this on thurs july 30
There was a problem hiding this comment.
Confirmed: the requester (hongyi-chen) has confirmed a public launch for Thursday, July 30. The docs are being prepared ahead of the flag flip intentionally. No doc change is needed — no 'coming soon' or feature-flag caveats will be added to the Gemini Enterprise page.
- team-managed-keys-and-endpoints.mdx: split BYOLLM row into AWS Bedrock (cloud agents: Yes) and Gemini Enterprise (cloud agents: No, interactive sessions only); qualify prose to state Gemini Enterprise is interactive-only in this iteration - billing.mdx: remove incorrect '80% reduced rate' credit claim; replace with correct model — customer-routed BYOLLM inference consumes no AI credits, local runs still consume platform credits - byollm-gemini-enterprise.mdx: remove unverified 'Inference via Gemini Enterprise Agent Platform' UI label; keep verified badge mention only The caution box on byollm-gemini-enterprise.mdx (interactive-only scope) and the FAQ entry were already accurate. platform/faqs.mdx already had the Bedrock vs. Gemini distinction for cloud agents. 80% grep: only one occurrence in the entire docs tree (billing.mdx:46), now corrected. Co-Authored-By: Oz <oz-agent@warp.dev>
There was a problem hiding this comment.
Final re-review — accepted
The rework at b6f32547def468d63663964c242c6e2e67e8cc95 resolves the four prior review items. I found no must-fix issues or follow-up polish.
Verified:
- Credits - No
80%claim remains insrc/content/docs/. The billing, BYOLLM overview, and Gemini Enterprise pages consistently state that customer-routed inference consumes no AI credits, provider inference is billed to the customer cloud account, and local runs still consume platform credits. - Cloud agents - The comparison table now distinguishes AWS Bedrock BYOLLM (Yes) from Gemini Enterprise BYOLLM (No, interactive sessions only). Related copy consistently scopes Gemini Enterprise to interactive requests and AWS Bedrock to current cloud-agent BYOLLM support.
- Model picker - The unverified model-details label was removed. The remaining references describe only the Gemini Enterprise badge without asserting an unverified UI string.
- Regression checks - The MDX table renders successfully in CI,
git diff --checkpasses, and no broken internal links were found.
Validation:
gh pr checks: passed (8/8).- Internal link checker: passed (3,207 internal links, 0 broken).
style_lint --changed: completed; reported 111 existing/non-blocking warnings, with no new material issue in this rework.- Local
npm run build: reached static-route generation, then hit the known/_llms-txt/support.txtstack-overflow failure under unsupported Nodev25.0.0; the PR's CI build/link/audit check passed.
Review run: https://oz.staging.warp.dev/runs/019faaca-2a9f-706b-bce4-d0b579f56ef3
|
I'm starting a first review of this pull request. You can view the conversation on Warp. I completed the review and no human review was requested for this pull request. Comment Powered by Oz |
![oz-for-oss[bot]](https://avatars.githubusercontent.com/in/3450139?s=60&v=4){kind=small}
There was a problem hiding this comment.
Overview
This PR adds a new Gemini Enterprise (Vertex AI) BYOLLM page and updates related Enterprise, billing, inference, and sidebar references to treat Gemini Enterprise as a supported BYOLLM provider. The structure and link placement are generally consistent with the docs, and no approved spec context was provided for a spec-drift pass.
Concerns
- The billing copy introduces
AI credits, which conflicts with the docs terminology standard to usecreditsfor the AI usage bucket. - The credential-security section says nothing sensitive leaves the customer's boundary, but the documented flow still sends request content and short-lived access tokens through Warp's backend; the claim needs to be narrowed to long-lived Google credentials.
Security
- Narrow the boundary claim so customers do not infer that prompts, responses, or access tokens never pass through Warp during Gemini Enterprise routing.
Verdict
Found: 0 critical, 3 important, 0 suggestions
Request changes
Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).
Powered by Oz
| ## BYOLLM billing | ||
|
|
||
| When using [Bring Your Own LLM (BYOLLM)](/enterprise/enterprise-features/bring-your-own-llm/), Warp routes requests through your cloud infrastructure (AWS Bedrock today, with Azure Foundry and Google Vertex coming soon). BYOLLM requests **consume credits at a reduced rate** which is approximately 80% lower than standard usage. Inference costs are also billed directly to your cloud account. | ||
| When using [Bring Your Own LLM (BYOLLM)](/enterprise/enterprise-features/bring-your-own-llm/), Warp routes requests through your cloud infrastructure (AWS Bedrock and [Gemini Enterprise on Vertex AI](/enterprise/enterprise-features/byollm-gemini-enterprise/) today, with Azure Foundry coming soon). Customer-routed BYOLLM inference **consumes no AI credits** — Warp does not charge AI 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. |
There was a problem hiding this comment.
AI credits; use credits for the AI usage bucket so this page stays consistent with the rest of billing docs.
| When using [Bring Your Own LLM (BYOLLM)](/enterprise/enterprise-features/bring-your-own-llm/), Warp routes requests through your cloud infrastructure (AWS Bedrock and [Gemini Enterprise on Vertex AI](/enterprise/enterprise-features/byollm-gemini-enterprise/) today, with Azure Foundry coming soon). Customer-routed BYOLLM inference **consumes no AI credits** — Warp does not charge AI 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. | |
| When using [Bring Your Own LLM (BYOLLM)](/enterprise/enterprise-features/bring-your-own-llm/), Warp routes requests through your cloud infrastructure (AWS Bedrock and [Gemini Enterprise on Vertex AI](/enterprise/enterprise-features/byollm-gemini-enterprise/) today, with Azure Foundry coming soon). Customer-routed BYOLLM inference **consumes no credits** — Warp does not 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. |
|
|
||
| When a request routes through Gemini Enterprise: | ||
|
|
||
| * **Warp doesn't consume AI credits** for that request. Inference is billed by Google Cloud to your project. |
There was a problem hiding this comment.
AI credits; use credits here to match the billing vocabulary.
| * **Warp doesn't consume AI credits** for that request. Inference is billed by Google Cloud to your project. | |
| * **No credits for inference** - Warp doesn't consume credits for that request. Inference is billed by Google Cloud to your project. |
| ### Credential security | ||
|
|
||
| * **No long-lived credentials** - The only long-lived credential involved is the member's Warp session. Access tokens are short-lived, held in memory, and never persisted. | ||
| * **Nothing sensitive leaves your boundary** - Warp stores only non-secret routing configuration (project ID, location, WIF audience, and optional service account email). Service account keys, refresh tokens, and credential files are never uploaded to Warp. |
There was a problem hiding this comment.
| * **Nothing sensitive leaves your boundary** - Warp stores only non-secret routing configuration (project ID, location, WIF audience, and optional service account email). Service account keys, refresh tokens, and credential files are never uploaded to Warp. | |
| * **No long-lived Google credentials leave your boundary** - Warp stores only non-secret routing configuration (project ID, location, WIF audience, and optional service account email). Service account keys, refresh tokens, and credential files are never uploaded to Warp. |
2 participants
Summary
Documents the newly shipped Gemini Enterprise (Vertex AI) BYOLLM support (REV-1599) and updates every page that claimed BYOLLM was "AWS Bedrock only, with Google Vertex coming soon." Content is sourced from
warp-server/specs/REV-1599/PRODUCT.md+TECH.mdand the client specwarp/specs/REV-1599/TECH.md.Changes
New page:
src/content/docs/enterprise/enterprise-features/byollm-gemini-enterprise.mdxhttps://app.warp.dev,sub/teamsclaim mapping, examplegcloudcommands, required IAM roles (roles/aiplatform.user,roles/serviceusage.serviceUsageConsumer), direct federated access vs. service account impersonation, and Admin Panel Models page configuration (project, location, WIF audience, optional SA, per-model refs, Enforce vs. Respect user setting).src/content/docs/enterprise/enterprise-features/bring-your-own-llm.mdxsrc/sidebar.tsStale claim refresh (Bedrock-only / "Google Vertex coming soon")
support-and-community/plans-and-billing/pricing-faqs.mdx(2 spots)agent-platform/inference/bring-your-own-api-key.mdx(comparison table)agent-platform/inference/custom-inference-endpoint.mdx(comparison table + centrally managed section)enterprise/support-and-resources/billing.mdx(BYOLLM billing)enterprise/team-management/admin-panel.mdx(Models settings)enterprise/index.mdx(key capabilities)enterprise/enterprise-features/team-managed-keys-and-endpoints.mdx(comparison + related resources)enterprise/security-and-compliance/security-overview.mdx(Models control + BYOLLM data locality)enterprise/getting-started/getting-started-enterprise.mdx(Admin Panel sections)platform/faqs.mdx(self-hosting LLM routing FAQ, now distinguishing Bedrock cloud-agent support from Gemini Enterprise's interactive-only scope)Validation
npm run buildpasses (351 pages, new page included)style_lint --changed: remaining flags on touched files are pre-existing or proper-noun false positives (e.g., "Gemini Enterprise", "Vertex AI", "ZDR" in headings, matching the existing Bedrock page's patterns)Notes for reviewers
gcloudexamples mirror the WIF contract in the specs (issuer,subshapescoped_principal:<team-uid>/<actor-type>:<principal-uid>,teamsclaim →google.groups); worth a skim from someone close to REV-1599 (cc Jaiden) to confirm the recommended IAM role set.Rework changes
Addressed code-review findings from review #4802286543:
Release state (❓ question — no doc change) — Confirmed with requester: public launch is Thursday July 30, docs intentionally prepared ahead of the flag flip. No "coming soon" or feature-flag caveats added. Thread replied and left open for reviewer acknowledgment.
Cloud agents — Gemini Enterprise interactive-only (⚠️ implemented, resolved) —
team-managed-keys-and-endpoints.mdx: split the single BYOLLM comparison-table row into two rows — AWS Bedrock (cloud agents: Yes) and Gemini Enterprise (cloud agents: No, interactive sessions only) — and rewrote the following prose to qualify cloud-agent support by provider.byollm-gemini-enterprise.mdxalready carried a correct caution box;platform/faqs.mdxalready distinguished the two providers. All other changed files were audited and found accurate.Credits — 80% claim removed (⚠️ implemented, resolved) —
billing.mdx:46: replaced the incorrect "reduced rate ≈ 80% lower" sentence with the correct model: customer-routed BYOLLM inference consumes no AI credits; inference billed to your cloud account; local runs still consume platform credits. Repo-wide grep for "80%": confirmedbilling.mdx:46was the only instance, now corrected.byollm-gemini-enterprise.mdxandbring-your-own-llm.mdxalready stated the correct model; no changes needed there.Model picker label — unverified string removed (⚠️ implemented, resolved) —
byollm-gemini-enterprise.mdx:179: removed the unverified "Inference via Gemini Enterprise Agent Platform" label string. The verified Gemini Enterprise badge mention is retained.Originating thread: https://warpdev.slack.com/archives/C0BDQDW8V5E/p1785276411828319
Conversation: https://staging.warp.dev/conversation/50ee6770-15d6-457e-9f45-6f85a8094710
Run: https://oz.staging.warp.dev/runs/019faaa2-a7cd-762c-889b-b9b653c45541
This PR was generated with Oz.
Co-Authored-By: Oz oz-agent@warp.dev