docs(pricing-may-2026): plans, FAQs, and team-management copy#116
Open
hongyi-chen wants to merge 10 commits into
Open
docs(pricing-may-2026): plans, FAQs, and team-management copy#116hongyi-chen wants to merge 10 commits into
hongyi-chen wants to merge 10 commits into
Conversation
Part of the May 14, 2026 pricing-and-packaging docs launch.
- May 2026 plan summary on plans-pricing-refunds.mdx — qualitative blurbs
for Free/Build/Max/Business/Enterprise. Links out to warp.dev/pricing.
Platform-credits one-liners on Business and Enterprise bullets.
- Pricing FAQs overhaul on pricing-faqs.mdx:
- Removed superseded Oct 30 2025 pricing change FAQ section.
- Refreshed plan recommendations (Build/Max/Business/Enterprise).
- Added evergreen FAQs: multi-seat credits, 'more AI usage' options,
auto-reload for teams, service-account waterfall, BYOK/CIE, and
'How do platform credits factor in?'.
- New 'Warp's pricing change FAQs (May 14 2026)' section covering
seat limits, Reload-credit attribution change, Max plan allowance
change + grandfathering, BYOK on Free, CIE, and ZDR clarifications.
- Replaced 'automatically enforced team-wide ZDR' with the new
model-provider ZDR vs admin-configurable data controls distinction.
- Renamed 'Add-on Credits' references to 'Reload credits' (slug stays).
- Team-management consequences added to teams.mdx in both
knowledge-and-collaboration and enterprise/team-management: ::caution
callouts covering leave/remove/delete + Reload-credit forfeiture +
rejoin restoration + active-subscription requirement.
Co-Authored-By: Oz <oz-agent@warp.dev>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
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}
Contributor
There was a problem hiding this comment.
Overview
This PR updates the pricing and billing docs for the May 2026 plan changes, including plan summaries, pricing FAQs, and team Reload-credit consequences. I found copy accuracy issues that would make the published docs misleading unless corrected before merge. The attached spec context contains no approved repository spec to compare against, and the supplemental security pass did not identify code-level security issues.
Concerns
- The new custom inference endpoint links point to a page that is not included in this diff and is not present in the docs tree I reviewed, so the PR depends on that target landing first or those links will 404.
- The plan recommendation FAQ calls Build and Max single-user plans, but the plan summary and later team billing copy describe Build/Max as team-capable self-serve plans.
- The new ZDR wording should be scoped to Warp-managed model-provider traffic; as written, it can be read to cover BYOK/CIE traffic routed through customer-controlled providers or endpoints.
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
| * [Add-on Credits](/support-and-community/plans-and-billing/add-on-credits/) — purchase additional credits or enable automatic reloads at discounted rates. | ||
| * [Platform credits](/support-and-community/plans-and-billing/platform-credits/) — learn how platform credits cover Warp's platform infrastructure for cloud agent runs and local runs with customer-supplied inference. | ||
| * [Bring Your Own API Key](/support-and-community/plans-and-billing/bring-your-own-api-key/) — connect your own model provider API keys for custom usage and billing. | ||
| * [Custom inference endpoint](/support-and-community/plans-and-billing/custom-inference-endpoint/) — connect an OpenAI-compatible endpoint such as OpenRouter, LiteLLM, z.ai, or an internal gateway. |
Contributor
There was a problem hiding this comment.
/support-and-community/plans-and-billing/custom-inference-endpoint/, but that page is not included in this PR and is not present in the docs tree reviewed here. Merge or include the CIE page/redirect before publishing this link, otherwise the pricing page will ship with a 404.
Comment on lines
+33
to
+34
| * **Build** — Single-user usage-based plan with monthly credits, the ability to [bring your own API key (BYOK)](/support-and-community/plans-and-billing/bring-your-own-api-key/) or point Warp at a [custom inference endpoint](/support-and-community/plans-and-billing/custom-inference-endpoint/), and access to [Reload credits](/support-and-community/plans-and-billing/add-on-credits/) with volume-based discounts. | ||
| * **Max** — Single-user plan for developers with heavier AI usage. Includes a larger monthly credit allowance than Build, plus a better effective rate for credits than buying Reload credits on Build. |
Contributor
There was a problem hiding this comment.
plans-pricing-refunds.mdx says both support up to 10 team members and this FAQ later includes Build/Max in self-serve team billing behavior. Remove the single-user framing so the pages do not contradict each other.
Suggested change
| * **Build** — Single-user usage-based plan with monthly credits, the ability to [bring your own API key (BYOK)](/support-and-community/plans-and-billing/bring-your-own-api-key/) or point Warp at a [custom inference endpoint](/support-and-community/plans-and-billing/custom-inference-endpoint/), and access to [Reload credits](/support-and-community/plans-and-billing/add-on-credits/) with volume-based discounts. | |
| * **Max** — Single-user plan for developers with heavier AI usage. Includes a larger monthly credit allowance than Build, plus a better effective rate for credits than buying Reload credits on Build. | |
| * **Build** — Usage-based plan for individuals or small teams with monthly credits, the ability to [bring your own API key (BYOK)](/support-and-community/plans-and-billing/bring-your-own-api-key/) or point Warp at a [custom inference endpoint](/support-and-community/plans-and-billing/custom-inference-endpoint/), and access to [Reload credits](/support-and-community/plans-and-billing/add-on-credits/) with volume-based discounts. | |
| * **Max** — Plan for individuals or small teams with heavier AI usage. Includes a larger monthly credit allowance than Build, plus a better effective rate for credits than buying Reload credits on Build. |
| If you’d like to explore Enterprise, [contact our sales team](https://www.warp.dev/contact-sales) and someone from Warp will follow up. | ||
| ::: | ||
|
|
||
| Independent of plan, all model provider traffic is covered by Warp's Zero Data Retention (ZDR) agreements with the underlying model providers (OpenAI, Anthropic, Google). Admin-configurable data controls — including team-wide retention policies and training opt-outs — are available on Business and Enterprise. |
Contributor
There was a problem hiding this comment.
… plan content - Add a new 'When do platform credits start being charged on self-serve plans?' FAQ in the May 14, 2026 pricing change section. Explains the May 14 → June 30 preview window (visible but not billed) and the July 1, 2026 cutover for self-serve cloud agent runs and Business BYOK / CIE usage. Calls out that the date aligns with the rest of the May 2026 self-serve transition and that Enterprise is billed per contract from May 14 and isn't affected. - Remove the per-legacy-plan Pro / Turbo / Lightspeed bulleted feature descriptions from the plan recommendation section. Keep a single pointer to Overages (Legacy) instead. - Remove the two stale 'continue to use Overages (Legacy) until their first renewal after December 1, 2025' caveats from the Lite-model and credit-reset FAQs — that cutoff passed months ago. Co-Authored-By: Oz <oz-agent@warp.dev>
Co-Authored-By: Oz <oz-agent@warp.dev>
The Max plan is no longer changing its monthly credit allowance as part of the May 21, 2026 launch, so remove the associated FAQ and grandfathering content: - Drop 'Max plan credit allowance changes' from the FAQ-section intro list. - Remove the 'Is the Max plan's monthly credit allowance changing?' FAQ in full, including the grandfathering bullets for annual and monthly Max subscribers. - Trim 'Max credit allowance change' from the 'This date lines up with...' sentence in the platform-credits preview FAQ, leaving seat limits, user-scoped Reload credits, and related grandfathering as the surviving transition items. Co-Authored-By: Oz <oz-agent@warp.dev>
…fy Free plan platform-credits billing Two changes to pricing-faqs.mdx: 1. Rewrite the 'How are service account / team-scoped API key requests billed on self-serve plans?' FAQ to drop the 'service account', 'agent identity', and 'task billing principal' terminology. New heading reads 'How are cloud agent runs on team plans billed when no individual user triggered them?'. Body is plain-language: cloud agent runs not initiated by a specific team member are billed to the team owner on self-serve plans, with the existing waterfall and auto-reload behavior preserved. 2. Clarify the platform-credits preview FAQ to call out that Free plan is unchanged. The preview period and July 1 cutover are self-serve paid plan transitions; Free plan cloud agent runs already consume from your plan allowance and don't change on July 1. Tightens the FAQ to say 'self-serve paid plans (Build,\n Max, Business)' instead of 'self-serve customers' so the scope is\n unambiguous, and adds an explicit 'Free plan' callout next to the\n Enterprise callout. Co-Authored-By: Oz <oz-agent@warp.dev>
Co-Authored-By: Oz <oz-agent@warp.dev>
- Convert Reload-credit team-membership :::caution / :::note callouts to plain prose under their existing subsections (enterprise teams.mdx, knowledge-and-collaboration/teams.mdx). - Remove the May 2026 plan snapshot from plans-pricing-refunds.mdx and drop legacy Overages bullets in the same file. - Strip legacy-plan (Pro/Turbo/Lightspeed) mentions and the Overages (Legacy) page entirely: delete overages-legacy.mdx, drop the index bullet, drop the sidebar entry, and repoint vercel.json's four legacy-overages redirects to add-on-credits. - Stop calling Build and Max single-user; describe them as for individual developers (teams up to 10). - Drop explicit Reload denominations ($10 / 400, etc.) from pricing-faqs and point readers to add-on-credits. - Remove the What happened to the Lite model? FAQ. - Trim the platform-credits-preview FAQ tail (date-lines-up, Free plan, Enterprise wrap-up paragraphs). - Drop the CIE acronym in the Custom Inference Endpoint FAQ. - Remove (formerly/previously called Add-on Credits) parentheticals; Reload credits has always been the name. Co-Authored-By: Oz <oz-agent@warp.dev>
Five new FAQs added to the main pricing-faqs.mdx body: - Does Warp have a SOC 2 Type 2 attestation? - points to Trust Center. - Does Warp have Zero Data Retention policies with LLM providers? - lists the providers (Anthropic, OpenAI, Google, Fireworks AI) and the contractual commitments (no training, deletion within fixed window). - How can I enable Zero Data Retention in Warp? - individual (Help Improve Warp toggle) and organization-wide (Admin Panel on Business and Enterprise) options. - Does Warp support other model routers or 'Bring Your Own LLM'? - clarifies that BYOLLM covers AWS Bedrock, Google Vertex AI, and Azure AI Foundry on Enterprise, and that arbitrary in-house routers aren't supported by default today. - What features are available during multi-harness orchestration beta? - flags that multi-harness orchestration is beta and Agent Memory is in Research Preview, with the standard 'availability, limits, and pricing may change' caveat. The launch-section ZDR FAQ is trimmed to point at the new general FAQs instead of repeating the provider list and setup details. Co-Authored-By: Oz <oz-agent@warp.dev>
- Enterprise plan answer + platform-credits FAQ + Custom Inference
Endpoint FAQ + new BYOLLM/multi-router FAQ: tighten BYOLLM scope so
it reflects current launch state (AWS Bedrock today; Azure Foundry
and Google Vertex coming soon) instead of implying all three ship.
- New BYOLLM/multi-router FAQ: normalize provider names ('Google
Vertex AI' -> 'Google Vertex', 'Azure AI Foundry' -> 'Azure
Foundry') to match the canonical short forms used by the BYOLLM
page.
- 'What counts as an AI token?' FAQ: drop the outdated claim that
paid plans get temporarily disabled at the monthly limit. Paid
plans now continue via Reload credits and auto-reload; only the
Free plan pauses access. Cross-link to the 'more AI usage' FAQ for
the full list of options.
Co-Authored-By: Oz <oz-agent@warp.dev>
hongyi-chen
added a commit
that referenced
this pull request
May 21, 2026
- bring-your-own-api-key.mdx 'Platform credits' note: Tyler correctly
pointed out that platform credits also apply for cloud agent runs.
Rewrite the line to lead with the cloud-agent case ('apply to every
cloud agent run on any plan') and then cover the local-runs case
('and to local agent runs on Business and Enterprise when using
BYOK, a custom inference endpoint, or BYOLLM').
- bring-your-own-api-key.mdx 'How BYOK works' opening: drop the
misleading 'directly to the model provider' phrasing since requests
still flow through Warp's infrastructure. Now reads 'Warp uses
these API keys when routing your agent requests to the model
provider you've configured.'
Tyler's third comment was a stylistic preference for 'need' over
'require' on the page note, which already uses 'need' here. The
parallel 'require' phrasing in pricing-faqs.mdx will be normalized on
PR #116.
Co-Authored-By: Oz <oz-agent@warp.dev>
Tyler's stylistic preference (raised on PR #115) was for 'need' over 'require' on the BYOK/CIE plan-availability sentences. The PR #115 page already uses 'need'; the equivalent phrasing in pricing-faqs.mdx ('Companies or organizations with more than 10 employees require a Warp Business or Enterprise plan to use these features') now reads 'need' in both places (BYOK FAQ + Custom Inference Endpoint FAQ). Co-Authored-By: Oz <oz-agent@warp.dev>
hongyi-chen
added a commit
that referenced
this pull request
May 21, 2026
Umbrella tracker for the May 21, 2026 pricing and packaging docs launch. Populates as the three thematic PRs land: - #114 - Credits, billing, and cloud-agent team billing - #115 - BYOK + custom inference endpoint + BYOLLM - #116 - Plans summary, pricing FAQs, teams copy Co-Authored-By: Oz <oz-agent@warp.dev>
hongyi-chen
added a commit
that referenced
this pull request
May 21, 2026
…LLM) (#115) * docs(pricing-may-2026): customer-supplied inference (BYOK + CIE + BYOLLM) Part of the May 14, 2026 pricing-and-packaging docs launch. - BYOK is now available on the Free plan; page rewritten to open eligibility, refresh model examples, and add the BYOK/CIE/BYOLLM comparison table. - New Custom Inference Endpoint (CIE) page for OpenAI Chat Completions– compatible endpoints (OpenRouter, LiteLLM, z.ai, internal gateways). Sidebar entry added under Plans and billing. - BYOLLM reframed as Enterprise-only managed inference. AWS Bedrock GA; Google Vertex AI and Azure AI Foundry on the roadmap. Cloud-native credentials now span IAM/OIDC across all three cloud providers. - 10-employee org rule applies to BYOK and CIE; larger orgs need Business or Enterprise. - Platform-credits caveats: on Business/Enterprise local agent runs, customer-supplied inference still consumes platform credits even though no AI credits are charged. - plans-and-billing/index.mdx updated to surface the new CIE page. Co-Authored-By: Oz <oz-agent@warp.dev> * docs(pricing-may-2026): note July 1 self-serve preview period in BYOK + CIE platform-credits callouts Both BYOK and CIE pages now spell out that self-serve billing for platform credits (including Business BYOK / CIE) doesn't start until July 1, 2026. Between May 14 and June 30, 2026, platform-credit consumption is visible in the Warp app's usage breakdown for transparency on Build, Max, and Business, but no platform credits are deducted from your Reload pool or counted against your spend cap. Enterprise plans are billed per contract from May 14 and aren't affected by this preview period. Co-Authored-By: Oz <oz-agent@warp.dev> * docs(pricing-may-2026): correct launch date May 14 \u2192 May 21, 2026 Co-Authored-By: Oz <oz-agent@warp.dev> * docs(pricing-may-2026): revert BYOLLM page to main, keep changes minimal Per launch direction: keep the Enterprise BYOLLM page largely unchanged for this launch. The BYOK/CIE/BYOLLM comparison still lives on the BYOK and CIE pages, so readers landing on either of those will see the three-way framing. This restores: - The original AWS-Bedrock-focused frontmatter description and opening paragraph (instead of the cross-provider reframing). - The original 'BYOLLM currently supports AWS Bedrock only. Coming soon: Azure Foundry and Google Vertex support.' caveat. - The original 'Cloud-native credentials - Authenticate using each user's AWS IAM identity' key feature. - The original 'How is BYOLLM different from BYOK?' FAQ with its 4-row comparison table. - The original Related resources list. Drops the launch-era additions: - The 'How BYOLLM differs from BYOK and Custom inference endpoint' section with the three-way comparison table. - The :::note about centrally configured BYOK / CIE for Enterprise being a fast-follow. - The :::note about platform credits for BYOLLM-routed local runs. Co-Authored-By: Oz <oz-agent@warp.dev> * docs(pricing-may-2026): drop CIE abbreviation, narrow credit claims, remove preview-period notes, restore File locations sidebar - Restore the 'File locations' sidebar entry under Settings file (added on main by PR #110, accidentally dropped during the rebase). - Drop the 'CIE' abbreviation throughout the customer-supplied inference pages. Use the full name 'custom inference endpoint' (or 'your endpoint' / 'endpoint-routed model' in context) instead. - Narrow the 'never consumes Warp credits' claim to 'doesn't consume AI credits' on the BYOK and custom inference endpoint pages, since Business / Enterprise local agent runs still consume platform credits. - Rewrite the 'No Warp credits consumed' Key features bullet on the custom inference endpoint page so it accurately calls out the platform-credits caveat on Business / Enterprise. - Drop the 'Self-serve preview period' paragraph from the platform-credits :::note callouts on the BYOK and custom inference endpoint pages. The July 1, 2026 cutover lives only in pricing-faqs.mdx now \u2014 canonical feature pages don't carry the launch-period detail. Co-Authored-By: Oz <oz-agent@warp.dev> * docs(pricing-may-2026): de-emphasize billing in BYOK + custom inference endpoint openings, consolidate plan notes - Reframe the BYOK and custom inference endpoint opening copy around model selection and data routing instead of billing. Move the AI-credits-consumption details out of the intro and down into the dedicated billing sections where they belong. - Collapse the two stacked :::note callouts about plan availability and the 10-or-fewer-employees rule into a single, briefer note on each page. - Move the Business / Enterprise platform-credits caveat off the top of the BYOK page and into the 'Credit usage' subsection alongside the related credit details. - Trim the 'BYOK on Enterprise and Business plans' section on the BYOK page so it doesn't restate the org-size rule already covered up top. - Replace the redundant 'Plan availability' section on the custom inference endpoint page with a focused 'Centrally managed configuration' section that only covers what's still unique to that page (user-level config today, admin-managed coming later).\n - Light copy polish on phrasing in both files. Co-Authored-By: Oz <oz-agent@warp.dev> * docs(pricing-may-2026): restore original BYOK opening, narrow only the credits claim to AI credits Per follow-up review, undo the polish on the BYOK intro and restore the original three-paragraph opening verbatim: - Title back to 'Bring Your Own API Key' (Title Case) - 'Warp supports Bring Your Own Key (BYOK) for users who want to connect Warp's agents to their own Anthropic, OpenAI, or Google API accounts.' - 'This lets you use your own API keys to access models directly, giving you full control over model selection, billing, and data routing. See Model Choice for a list of supported models.' - 'BYOK provides greater flexibility in model access and ensures Warp never consumes your AI credits for requests routed through your own keys.' The only substantive change vs the original is narrowing 'credits' to 'AI credits' in that last sentence, per earlier feedback that the unqualified 'never consumes Warp credits' claim is too broad now that Business / Enterprise local runs can consume platform credits. The combined plan-availability + 10-employee :::note below the intro stays as-is. Everything below the intro (BYOK works, Enabling BYOK, billing behavior, Credit usage with the platform-credits note, ZDR, Enterprise/Business config, Related resources) is unchanged. Co-Authored-By: Oz <oz-agent@warp.dev> * docs(pricing-may-2026): soften absolute 'no AI credits / 0 credits' claims in BYOK + CIE credit sections - Drop the 'No AI credits are consumed' bullet and the 'credit transparency footer shows 0 credits used' sentence from BYOK's Credit usage subsection. Replaced with a more general framing that says inference is billed through your provider account rather than drawing from your Warp AI credits, alongside the existing platform credits caveat for Business / Enterprise. - Same softening on the custom inference endpoint page's Warp AI credits subsection \u2014 collapse the three firm bullets into one general sentence and keep the platform-credits note. This avoids the misleadingly absolute '0 credits' claim, which is inaccurate for Business / Enterprise local runs where platform credits can still apply. Co-Authored-By: Oz <oz-agent@warp.dev> * docs(pricing-may-2026): reframe custom inference endpoint intro to lead with powering Warp's agents Mirror the BYOK page's intro pattern so it's explicit upfront that a custom inference endpoint is used to power Warp's agents. New opening: Warp supports custom inference endpoints for users who want to power Warp's agents with any OpenAI-compatible inference endpoint \u2014 a model router, hosted gateway, or internal infrastructure they already run. This lets you route AI requests through your preferred provider, run inference behind your own gateway, or use a router like OpenRouter or LiteLLM, while keeping the agent experience inside Warp. No other changes. Co-Authored-By: Oz <oz-agent@warp.dev> * Cleanup pass: BYOK acronym + BYOLLM table scope - bring-your-own-api-key.mdx intro: fix the wrong BYOK expansion ('Bring Your Own Key (BYOK)') to match the page title and standard usage ('Bring Your Own API Key (BYOK)'). - bring-your-own-api-key.mdx + custom-inference-endpoint.mdx comparison tables: tighten the BYOLLM row so it reflects current launch scope ('AWS Bedrock today; Azure Foundry and Google Vertex coming soon') instead of implying all three ship at launch. Co-Authored-By: Oz <oz-agent@warp.dev> * PR #115 review: address Tyler's comments - bring-your-own-api-key.mdx 'Platform credits' note: Tyler correctly pointed out that platform credits also apply for cloud agent runs. Rewrite the line to lead with the cloud-agent case ('apply to every cloud agent run on any plan') and then cover the local-runs case ('and to local agent runs on Business and Enterprise when using BYOK, a custom inference endpoint, or BYOLLM'). - bring-your-own-api-key.mdx 'How BYOK works' opening: drop the misleading 'directly to the model provider' phrasing since requests still flow through Warp's infrastructure. Now reads 'Warp uses these API keys when routing your agent requests to the model provider you've configured.' Tyler's third comment was a stylistic preference for 'need' over 'require' on the page note, which already uses 'need' here. The parallel 'require' phrasing in pricing-faqs.mdx will be normalized on PR #116. Co-Authored-By: Oz <oz-agent@warp.dev> --------- Co-authored-by: Oz <oz-agent@warp.dev>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part of the May 14, 2026 Warp pricing-and-packaging docs launch. Targets the umbrella branch
hyc/plan-updates.This PR carries the user-facing plan summary, pricing FAQs, and team-management consequences. Companion thematic PRs:
hyc/plan-updates-credits-billing— credits, billing, service-account modelhyc/plan-updates-byok-cie-byollm— customer-supplied inference pages (BYOK, CIE, BYOLLM)What's covered
plans-pricing-refunds.mdx— short qualitative blurbs for Free, Build, Max, Business, Enterprise. No per-plan monthly credit counts hard-coded; links out towarp.dev/pricingfor current allowances. Platform-credits one-liners on the Business and Enterprise bullets.pricing-faqs.mdx:knowledge-and-collaboration/teams.mdxandenterprise/team-management/teams.mdx::::cautioncallouts covering leave/remove/delete + Reload-credit forfeiture, rejoin restoration, and the active-subscription requirement.Files changed
src/content/docs/support-and-community/plans-and-billing/plans-pricing-refunds.mdxsrc/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdxsrc/content/docs/knowledge-and-collaboration/teams.mdxsrc/content/docs/enterprise/team-management/teams.mdxEditorial rules followed
warp.dev/pricing.Co-Authored-By: Oz oz-agent@warp.dev