docs(pricing-may-2026): BYOLLM reframe, plan summary, Enterprise billing, and plans-and-billing index

[hongyi-chen]

Summary

Part of the May 2026 Warp pricing docs overhaul (umbrella branch hyc/plan-updates, plan artifact 825dd175-1815-4df6-8c55-8cda72e35131). This PR is Agent 4's slice: BYOLLM update, plan summary, Enterprise billing alignment, and the plans-and-billing landing page.

Changes

bring-your-own-llm.mdx

• Reframe BYOLLM as Enterprise-only managed inference infrastructure: cloud-provider Model-as-a-Service (Bedrock GA today; Vertex AI and AI Foundry on the roadmap) or approved internal gateways.
• Replace the AWS-only "Coming soon" caveat with cleaner roadmap framing.
• Add a new `## How BYOLLM differs from BYOK and Custom inference endpoint` section with a three-row Name / Meaning / Plans table. Link out to the BYOK and CIE pages.
• Add a `:::note` callout that centrally configured BYOK/CIE for Enterprise is a fast-follow, not at launch.
• Replace the old BYOK-only FAQ with a pointer to the new comparison section.
• Add the CIE link to Related resources.

`plans-pricing-refunds.mdx`

• Add a new `### May 2026 plan summary` section listing Free, Build, Max, Business, and Enterprise with seat limits and qualitative descriptions of each plan's value.
• Per the editorial rule, no per-plan monthly credit counts: link out to warp.dev/pricing for current monthly credit allowances.
• Include the short multi-week Implementation Engineer Support tooltip phrasing on the Enterprise bullet.
• Add a Custom inference endpoint bullet to the existing sub-page list.
• Refund policy section untouched.

`enterprise/support-and-resources/billing.mdx`

• Add a `:::note` clarifying that team-wide spending limits (cloud, local, total) are also available on Warp's self-serve paid plans, while per-user spending limits are Enterprise-only.
• Add an Enterprise Analytics API link to Related resources and reference it from the spend-controls note.

`plans-and-billing/index.mdx`

• Add the Custom inference endpoint bullet using the orchestrator-specified title and description so the upcoming page (owned by Agent 2) is discoverable from the plans-and-billing landing page.

Editorial rule compliance

• No per-plan monthly credit counts anywhere in the diff. Confirmed with a grep for `1,500`, `15,000`, `18,000`, etc. across edited files.
• Reload-credit SKU denomination prices and the 100-credit auto-reload threshold are not touched (those belong to Agent 3).

Coordination notes

• Stayed within Agent 4's file ownership. Did not touch `src/sidebar.ts`, `bring-your-own-api-key.mdx`, `pricing-faqs.mdx`, `add-on-credits.mdx`, or `credits.mdx`.
• The CIE link target (`custom-inference-endpoint`) will resolve once Agent 2's PR lands.
• Assumption: seat limits stated as "Single seat" for Free/Build/Max, "Up to 50 seats" for Business (existing FAQ), and "Custom seat counts" for Enterprise. Flagged this in messaging — happy to revise if other agents' research surfaces different numbers.

Validation

• Did not run `npm run build` per the orchestrator's instructions (integrated build is the orchestrator's responsibility after all four PRs land).
• Manually reviewed each diff for MDX syntax (callouts, tables, links).

Co-Authored-By: Oz oz-agent@warp.dev

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs	Error		May 13, 2026 1:51am

[oz-for-oss]

@hongyi-chen

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 /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

[oz-for-oss]

Overview

This PR updates pricing/BYOLLM documentation, adds plan-summary content, and cross-links the upcoming Custom inference endpoint docs. The changed docs are generally coherent, and I did not find security-specific issues in this docs-only diff.

Concerns

• The BYOLLM page now describes Vertex, Foundry, and internal gateway support, but the key features section still states AWS IAM as the authentication model.
• The new Custom inference endpoint links point to a page that is not added by this PR, so this branch can ship broken links unless the dependency is merged first or included here.

Verdict

Found: 0 critical, 2 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

[oz-for-oss]

⚠️ [IMPORTANT] The intro now covers Vertex, Foundry, and internal gateways, but this key feature still documents AWS IAM as the only authentication path. Generalize it or split provider-specific behavior so the expanded BYOLLM scope is accurate.

Suggested change

	* **Cloud-native credentials** - Authenticate using each user’s AWS IAM identity. Warp does not store API keys.
	* **Cloud-native or gateway credentials** - Authenticate using the approved provider or gateway identity model. For AWS Bedrock, Warp uses each user’s AWS IAM identity; Warp does not store API keys.

[oz-for-oss]

⚠️ [IMPORTANT] This adds a public link to /support-and-community/plans-and-billing/custom-inference-endpoint/, but the target page is not part of this PR. Include the page in the same merge path or hold these links until the dependency lands so the docs build does not ship broken links.