docs(pricing-may-2026): plans, FAQs, and team-management copy#116
docs(pricing-may-2026): plans, FAQs, and team-management copy#116hongyi-chen wants to merge 3 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.
|
|
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 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. |
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.
| * **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. |
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.
| * **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. |
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>
1 participant
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