Pricing FAQs overhaul for May 14, 2026 changes#73
Open
hongyi-chen wants to merge 3 commits into
Open
Conversation
* Delete the entire 'Warp's pricing change FAQs (Oct 30, 2025)' section and remove the stale anchor link from the 'How can I get the most out of my Warp plan?' callout. * Rewrite plan-recommendation copy with qualitative Build / Max / Business / Enterprise positioning; replace 'enforced team-wide ZDR' language with 'admin-configurable data controls' and split model- provider ZDR out as a separate, all-plan concept. * Update the Lite-model FAQ to mention BYOK and Custom Inference Endpoint (CIE) alongside Reload credits. * Add new FAQs: multi-seat team credits with grandfathered pooled credits, what-to-do-when-you-need-more-AI-usage (Max + Reload + BYOK + CIE), how auto-reload works for teams, and how service-account / team-scoped API key requests are billed on self-serve plans. * Add BYOK-on-all-plans and CIE FAQs; rename 'Add-on Credits' to 'Reload credits' and fix one remaining stale anchor link inside the downgrade caution callout. * Add new tail-end 'Warp's pricing change FAQs (May 14, 2026)' section covering seat limits + grandfathering, Reload credits attribution change, Max plan credit-allocation change + grandfathering, BYOK on Free, the CIE launch, and the ZDR / data-controls clarification. Per the editorial rule, no per-plan monthly credit counts are hard-coded; the page links to warp.dev/pricing for current allowances. 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 refreshes the pricing FAQ for the May 14, 2026 plan changes, adds new FAQs for Reload credits, BYOK, CIE, and ZDR, and removes the older Oct 2025 pricing-change FAQ section. The structure is clear, but a few changes need correction before merge.
Concerns
- The ZDR language overstates Warp's provider-level protections for BYOK, custom inference endpoint, and BYOLLM traffic; those paths depend on the customer's provider or infrastructure settings.
- Deleting the Oct 2025 FAQ heading removes an anchor that existing docs still link to, so this PR can create broken in-site links unless those references are updated or a compatibility anchor remains.
- One auto-reload bullet still uses pooled-credit wording despite the new user-scoped Reload credit model.
Security
- The ZDR wording is privacy/security-sensitive because it could tell Free, BYOK, CIE, or BYOLLM users that Warp provider ZDR agreements cover traffic that may bypass Warp-managed model providers.
Verdict
Found: 0 critical, 3 important, 1 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
| If you’d like to explore Enterprise, [contact our sales team](https://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.
Suggested change
| 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. | |
| Independent of plan, Warp-managed model provider traffic is covered by Warp's Zero Data Retention (ZDR) agreements with the underlying model providers (OpenAI, Anthropic, Google). Requests routed through BYOK, a custom inference endpoint, or BYOLLM follow the retention policies of the provider or infrastructure you configure. Admin-configurable data controls — including team-wide retention policies and training opt-outs — are available on Business and Enterprise. |
| When auto-reload is **on**: | ||
|
|
||
| * The admin chooses a Reload credit **denomination** ($10 / 400, $20 / 1,000, $50 / 3,000, or $100 / 6,500). Larger denominations have a better effective per-credit rate. | ||
| * Whenever any individual user's balance (plan credits + their share of Reload credits) drops below **100 credits**, Warp automatically purchases another bundle of the configured denomination on the team's behalf. |
There was a problem hiding this comment.
💡 [SUGGESTION] their share of Reload credits sounds pooled, but the new FAQ says Reload credits are user-scoped.
Suggested change
| * Whenever any individual user's balance (plan credits + their share of Reload credits) drops below **100 credits**, Warp automatically purchases another bundle of the configured denomination on the team's behalf. | |
| * Whenever any individual user's balance (plan credits + their user-scoped Reload credit balance) drops below **100 credits**, Warp automatically purchases another bundle of the configured denomination on the team's behalf. |
|
|
||
| --- | ||
|
|
||
| ### Warp's pricing change FAQs (Oct 30, 2025) |
There was a problem hiding this comment.
#warps-pricing-change-faqs-oct-30-2025, but existing docs still link to that anchor; update those links or keep a compatibility anchor before this PR merges.
Comment on lines
+345
to
+346
| * **Model provider ZDR** — Warp has Zero Data Retention agreements with the underlying model providers (OpenAI, Anthropic, Google) so your prompts and completions aren't retained by those providers for training or logging. This applies to **all plans, including Free**. | ||
| * **Admin-configurable data controls** — Settings that let admins control what Warp itself retains for the team (data retention windows, training opt-outs, etc.). These are available on **Business and Enterprise**, and replace what was previously described as "automatically enforced team-wide ZDR." |
There was a problem hiding this comment.
Suggested change
| * **Model provider ZDR** — Warp has Zero Data Retention agreements with the underlying model providers (OpenAI, Anthropic, Google) so your prompts and completions aren't retained by those providers for training or logging. This applies to **all plans, including Free**. | |
| * **Admin-configurable data controls** — Settings that let admins control what Warp itself retains for the team (data retention windows, training opt-outs, etc.). These are available on **Business and Enterprise**, and replace what was previously described as "automatically enforced team-wide ZDR." | |
| * **Warp-managed model provider ZDR** — Warp has Zero Data Retention agreements with the underlying model providers (OpenAI, Anthropic, Google) for Warp-managed model requests, so prompts and completions for those requests aren't retained by those providers for training or logging. This applies to Warp-managed models on **all plans, including Free**. Requests routed through BYOK, a custom inference endpoint, or BYOLLM follow the retention policies of the provider or infrastructure you configure. | |
| * **Admin-configurable data controls** — Settings that let admins control what Warp itself retains for the team (data retention windows, training opt-outs, etc.). These are available on **Business and Enterprise**, and replace what was previously described as "automatically enforced team-wide ZDR." |
Per PR #73 follow-up: BYOK and custom inference endpoint support are available to individual users and organizations with 10 or fewer employees; larger organizations need a Business or Enterprise plan. * 'Can I bring my own API key?' FAQ: append the verbatim disclosure paragraph at the end of the answer. * 'Does Warp support custom inference endpoints?' FAQ: same. * 'What if I need more AI usage than my plan includes?' FAQ: add a one-line italicized cross-reference below the BYOK / CIE bullets pointing to the BYOK FAQ above. Co-Authored-By: Oz <oz-agent@warp.dev>
This file is the canonical version created on PR #71 (hyc/plan-updates-byok-cie). It is duplicated here so that the link checker on this branch can resolve the relative references to /support-and-community/plans-and-billing/custom-inference-endpoint/ that this PR introduces. When PR #71 merges into hyc/plan-updates, git will reconcile the identical file contents automatically. 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 2026 Warp pricing docs overhaul (umbrella branch:
hyc/plan-updates).This PR is Agent 1 in the fan-out plan and is scoped to a single file:
src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx.What changed
Removed
Warp's pricing change FAQs (Oct 30, 2025)section (Oct 30, 2025 + sub-FAQs).How can I get the most out of my Warp plan?callout.Updated
automatically enforced team-wide ZDRclaim in favor ofadmin-configurable data controls, with model-provider ZDR called out separately as an all-plan concept.Add-on Credits→Reload creditsrenamed in this file's references.warp.dev/pricingfor current allowances. The Reload-credit denomination SKU prices ($10 / 400, $20 / 1,000, $50 / 3,000, $100 / 6,500) and the 100-credit auto-reload threshold are retained — those are SKU prices and a mechanic, not plan-included credit counts.Added
New evergreen FAQs:
New tail-end section
Warp's pricing change FAQs (May 14, 2026)with sub-FAQs covering:Out of scope (and noted for the orchestrator)
/support-and-community/plans-and-billing/custom-inference-endpoint/) is owned by Agent 2.add-on-credits.mdx:51(Agent 3 owns) andknowledge-and-collaboration/teams.mdx:42,73(outside any current agent's ownership). Not touched here.Conversation: https://staging.warp.dev/conversation/96d38a96-d105-45ed-a1f1-7479f5bab615
Co-Authored-By: Oz oz-agent@warp.dev