From 2540299168834c5f656a5d237af5a58c673e8452 Mon Sep 17 00:00:00 2001 From: Hong Yi Chen Date: Tue, 19 May 2026 16:57:17 -0700 Subject: [PATCH 01/15] docs(pricing-may-2026): plans, FAQs, and team-management copy MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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 --- .../docs/enterprise/team-management/teams.mdx | 20 ++ .../knowledge-and-collaboration/teams.mdx | 12 + .../plans-pricing-refunds.mdx | 17 ++ .../plans-and-billing/pricing-faqs.mdx | 246 ++++++++++-------- 4 files changed, 185 insertions(+), 110 deletions(-) diff --git a/src/content/docs/enterprise/team-management/teams.mdx b/src/content/docs/enterprise/team-management/teams.mdx index 544aa3ef..fed7fa48 100644 --- a/src/content/docs/enterprise/team-management/teams.mdx +++ b/src/content/docs/enterprise/team-management/teams.mdx @@ -64,6 +64,26 @@ If you've received an invite link, use it to sign up or log in and join the team If you're a Team Owner and choose to [delete your Warp account](/support-and-community/privacy-and-security/privacy/#delete-your-account-and-data), you'll need to assign a team member as the new owner before your account can be deleted. ::: +### Reload credit consequences when leaving or removing members + +On Build, Max, and Business plans, [Reload credits](/support-and-community/plans-and-billing/add-on-credits/) are scoped to the individual user under your team. Membership changes affect access to those credits: + +:::caution +**Leaving the team.** If you leave this team, you'll lose access to any remaining Reload credits tied to it. If you rejoin the same team later, you'll regain access to any unused, non-expired credits. +::: + +:::caution +**An admin removes a member.** When an admin removes a member, that member loses access to any remaining Reload credits tied to this team. If they rejoin later, they'll regain access to any unused, non-expired credits. +::: + +:::caution +**An admin deletes the team.** Deleting this team will remove all members' access to any remaining Reload credits tied to it. Team members will no longer be able to use those credits. +::: + +:::note +Reload credits require an active subscription. Downgrading to the Free plan forfeits access to Reload credits tied to your team. Pre-launch pooled balances are grandfathered and drain first. +::: + ## Team discoverability Team admins can make their team discoverable to colleagues who share the same email domain. When enabled, new users with a matching domain can find and join the team without needing a direct invite link. diff --git a/src/content/docs/knowledge-and-collaboration/teams.mdx b/src/content/docs/knowledge-and-collaboration/teams.mdx index 7c3f8f76..3474ca74 100644 --- a/src/content/docs/knowledge-and-collaboration/teams.mdx +++ b/src/content/docs/knowledge-and-collaboration/teams.mdx @@ -67,6 +67,18 @@ If you have received an invite link, you can use that link to sign up or log in If you’re a member of a team, you can visit **Settings** > **Teams** to leave a team at any time. Team admins (who created teams) may delete a team only after removing all team members. +:::caution +**Leaving a paid team forfeits access to Reload credits tied to it.** [Reload credits](/support-and-community/plans-and-billing/add-on-credits/) are scoped to your individual user under your team. If you leave a paid team, you lose access to any remaining Reload credits attributed to you. If you rejoin the same team later, you regain access to any unused, non-expired credits. +::: + +:::caution +**Deleting a team removes all members' access to Reload credits.** If an admin deletes the team, every member loses access to any remaining [Reload credits](/support-and-community/plans-and-billing/add-on-credits/) attributed to them under that team. +::: + +:::note +Reload credits require an active subscription. Downgrading to the Free plan also forfeits access to Reload credits. +::: + ## Team discoverability Team admins can make their teams discoverable to colleagues from the same email domain. This feature is available under **Settings** > **Teams** > **Make team discoverable**. diff --git a/src/content/docs/support-and-community/plans-and-billing/plans-pricing-refunds.mdx b/src/content/docs/support-and-community/plans-and-billing/plans-pricing-refunds.mdx index 10f9b086..fb673825 100644 --- a/src/content/docs/support-and-community/plans-and-billing/plans-pricing-refunds.mdx +++ b/src/content/docs/support-and-community/plans-and-billing/plans-pricing-refunds.mdx @@ -22,9 +22,26 @@ Visit [warp.dev/pricing](https://www.warp.dev/pricing) to see the latest plans a * [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. * [Overages (Legacy)](/support-and-community/plans-and-billing/overages-legacy/) — information for users on legacy plans with overages enabled. * [Pricing FAQs](/support-and-community/plans-and-billing/pricing-faqs/) — answers to common questions about plans, billing, and usage. Don’t have Warp yet? [Download Warp](https://www.warp.dev/download) and get started for free today. +### May 2026 plan summary + +Below is a high-level summary of Warp's plans as of May 14, 2026. Visit [warp.dev/pricing](https://www.warp.dev/pricing) for current monthly credit allowances and seat pricing. + +* **Free** — Up to 10 team members. For developers exploring Warp. Includes core terminal features and a monthly credit allowance for trying Warp's agents. Supports [Bring Your Own API Key](/support-and-community/plans-and-billing/bring-your-own-api-key/) and [custom inference endpoints](/support-and-community/plans-and-billing/custom-inference-endpoint/) so you can keep working with your own provider after the included allowance is used. +* **Build** — Up to 10 team members. For developers using Warp's agents as a daily driver. Includes a higher monthly credit allowance than Free, [Add-on Credits](/support-and-community/plans-and-billing/add-on-credits/) with auto-reload, and the same BYOK and custom inference endpoint support as Free. +* **Max** — Up to 10 team members. For heavy users. Includes everything in Build with a higher monthly credit allowance and a better effective Reload rate. +* **Business** — Up to 25 team members. For small-to-midsize teams. Includes everything in Max plus team-wide collaboration features, Reload credits with admin-managed auto-reload and team-wide spend caps, SAML-based SSO, and admin-configurable data controls. Platform credits apply to cloud agent runs and to local runs that use customer-supplied inference (BYOK or CIE). +* **Enterprise** — Unlimited team members (custom contract). For organizations with advanced security, compliance, or scale needs. Includes everything in Business plus [Bring your own LLM](/enterprise/enterprise-features/bring-your-own-llm/), the [Enterprise Analytics API](/enterprise/enterprise-features/analytics-api/), per-user spend limits, advanced admin controls, and Implementation Engineer Support (a structured multi-week implementation program with hands-on guidance from Warp engineers to help your team deploy production Oz Cloud Agent use cases). Platform credits apply to all cloud agent runs and to local runs using BYOLLM, BYOK, or CIE. + +:::note +BYOK and custom inference endpoint support are available for individual users and organizations with 10 or fewer employees, subject to Warp's Terms of Service. Companies or organizations with more than 10 employees require a Warp Business or Enterprise plan to use these features. +::: + +Model provider Zero Data Retention (ZDR) applies across all plans through Warp's contracted LLM providers. See [Pricing FAQs](/support-and-community/plans-and-billing/pricing-faqs/) for details on data controls. + ### Warp’s refund policies Please review the details of our refund policies below. To request a refund, email [**billing@warp.dev**](mailto:billing@warp.dev) with information about your situation — the more context you provide, the faster we can resolve your request. diff --git a/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx b/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx index 434d901e..67b1f97b 100644 --- a/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx +++ b/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx @@ -23,37 +23,39 @@ After entering your payment details, you’ll receive an invoice and confirmatio ### How can I get the most out of my Warp plan? :::caution -Warp's legacy paid plans included Pro, Turbo, and Lightspeed. +Warp's legacy paid plans included Pro, Turbo, and Lightspeed. These plans are no longer offered to new subscribers. -After **Oct 30, 2025**, we have rolled out the new Build plan to replace them. Existing subscribers will start to roll over onto the Build plan starting **Dec 1st, 2025**. For questions related to the new pricing changes, please refer to [Warp's pricing change FAQs](/support-and-community/plans-and-billing/pricing-faqs/#warps-pricing-change-faqs-oct-30-2025). - -To see more details on the latest plan, please visit [**warp.dev/pricing**](https://www.warp.dev/pricing). +For details on those legacy plans and how their usage was billed, see [Overages (Legacy)](/support-and-community/plans-and-billing/overages-legacy/). For the most up-to-date list of plans, seat limits, and credit allowances, visit [warp.dev/pricing](https://www.warp.dev/pricing). ::: -Warp's plans are designed for developers who rely on AI to code, debug, and move faster with their team. +Warp's plans are designed for developers who rely on AI to code, debug, and move faster with their team. Pick the plan that matches the scale of your usage and the controls your team needs: -* **Build**, one usage-based plan with a set of credits, ability to Bring Your Own API Key (BYOK), and access to [Add-on credits](/support-and-community/plans-and-billing/add-on-credits/) with volume-based discounts. See more on [Bring Your Own API Key](/support-and-community/plans-and-billing/bring-your-own-api-key/). -* **Business** includes everything in Build, with advanced features like automatically enforced team-wide Zero Data Retention, SAML-based SSO, and support for teams up to 50 seats. +* **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. +* **Business** — Multi-seat plan for teams. Includes everything in Build, plus admin-configurable data controls, SAML-based SSO, and centralized billing. Available up to the seat limit listed at [warp.dev/pricing](https://www.warp.dev/pricing). +* **Enterprise** — Custom plan for organizations that need higher seat counts, [Bring Your Own LLM (BYOLLM)](/enterprise/enterprise-features/bring-your-own-llm/) managed inference, granular admin controls, advanced security and compliance, and dedicated support. -Legacy plans (**No longer available for new subscribers**): +Legacy plans (**no longer available for new subscribers**): * **Pro** included higher credit limits than the Free plan, support for larger codebases with [Codebase Context](/agent-platform/capabilities/codebase-context/), and access to premium models with optional pay-as-you-go [Overages (Legacy)](/support-and-community/plans-and-billing/overages-legacy/). * **Turbo** included even higher credit limits, larger Codebase Context indexing, and the option to pay for additional usage beyond included credits via [Overages (Legacy)](/support-and-community/plans-and-billing/overages-legacy/). Add-on Credits were not available on this plan. * **Lightspeed** was Warp's most powerful legacy plan, offering the highest credit limits, expanded codebase indexing, access to top-tier models, and pay-as-you-go [Overages (Legacy)](/support-and-community/plans-and-billing/overages-legacy/) so you could keep working without interruption. -For the most up-to-date feature and usage details, visit [**warp.dev/pricing**](https://www.warp.dev/pricing). +For the most up-to-date feature and usage details — including current per-plan seat limits and monthly credit allowances — visit [warp.dev/pricing](https://www.warp.dev/pricing). ### How can I subscribe to a Warp Enterprise plan? Warp offers two options for larger teams and organizations: -* **Business Plan**: Supports up to 50 seats and is available for immediate upgrade. It includes automatically enforced team-wide Zero Data Retention by default and admin-controlled SAML-based SSO. -* **Enterprise Plan**: Offers custom pricing, credit limits, and terms. Along with support for larger engineering orgs or teams with advanced security, compliance, or support needs. +* **Business plan**: Self-serve multi-seat plan available for immediate upgrade. Includes admin-configurable data controls and admin-controlled SAML-based SSO. See [warp.dev/pricing](https://www.warp.dev/pricing) for the current seat limit. +* **Enterprise plan**: Custom pricing, credit allowances, and terms — built for larger engineering organizations or teams with advanced security, compliance, or support needs. Enterprise also includes [Bring Your Own LLM (BYOLLM)](/enterprise/enterprise-features/bring-your-own-llm/) managed inference, where Warp routes traffic through your AWS Bedrock, Google Vertex, Azure Foundry, or internal LLM gateway with routing, orchestration, governance, and observability provided by Warp. :::tip 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. + ### What counts as a team member and how does billing work for members? In Warp, a _team member_ is any seat with access to your Team — including the shared Warp Drive, Notebooks, Workflows, and other team resources. All plans allow you to invite unlimited users, but to unlock higher limits and advanced features, you’ll need to upgrade your team to a plan. Upgrading applies to your entire team, including your own account and all active members. @@ -99,7 +101,7 @@ You can use your Warp account on multiple personal computers. Warp is designed t ### What happens when I downgrade during a billing cycle? :::caution -Note this only applies when switching between legacy plans (Pro, Turbo, Lightspeed, or the Old Business) or switching the new plans (Build, New Business). When switching between legacy to new plans, the change is immediate, prorated, and the credits are reset. See more in [What happens when I change from my legacy plan to the new Build or Business plans?](/support-and-community/plans-and-billing/pricing-faqs/#what-happens-when-i-change-from-my-legacy-plan-to-the-new-build-or-business-plans). +This describes downgrades between current paid plans (Build, Max, Business). Users transitioning from a legacy plan (Pro, Turbo, Lightspeed, old Business) to a current plan saw an immediate, prorated change with a credit reset at renewal; see [Overages (Legacy)](/support-and-community/plans-and-billing/overages-legacy/) for details on the legacy plans. ::: The subscription will downgrade to the lower plan limits at the end of the billing cycle. If you’re switching between paid plans, any AI usage you've already accumulated will carry over.\ @@ -140,16 +142,83 @@ Warp now abstracts away token usage, so you don't need to manage or track it dir If you're curious, you can read the [OpenAI article on tokens](https://help.openai.com/en/articles/4936856-understanding-tokens), or refer to the pricing page for plan-level credit allocations. If you reach your monthly credit limits on a paid plan, premium models will be temporarily disabled until your quota resets at the start of your next billing cycle. -If you’d like to continue using premium models beyond your included quota, purchase [Add-on Credits](/support-and-community/plans-and-billing/add-on-credits/) in **Settings** > **Billing and usage** (users still on legacy Pro, Turbo, or Lightspeed plans continue to use [Overages (Legacy)](/support-and-community/plans-and-billing/overages-legacy/) until their first renewal after December 1, 2025). +If you’d like to continue using premium models beyond your included quota, purchase [Reload credits](/support-and-community/plans-and-billing/add-on-credits/) in **Settings** > **Billing and usage** (users still on legacy Pro, Turbo, or Lightspeed plans continue to use [Overages (Legacy)](/support-and-community/plans-and-billing/overages-legacy/) until their first renewal after December 1, 2025). ### How often do my credits reset? -Allotted credits refill every 30 days from your signup date. When you upgrade to a [paid plan](https://www.warp.dev/pricing), you will be given more credits immediately. You can follow along with your refill period by referencing **Settings** > **Billing and usage**. Alternatively, purchase [Add-on Credits](/support-and-community/plans-and-billing/add-on-credits/), or enable auto reload with a monthly spend limit, to continue using premium models beyond your included quota. Users still on legacy Pro, Turbo, or Lightspeed plans continue to use [Overages (Legacy)](/support-and-community/plans-and-billing/overages-legacy/) until their first renewal after December 1, 2025. +Allotted credits refill every 30 days from your signup date. When you upgrade to a [paid plan](https://www.warp.dev/pricing), you will be given more credits immediately. You can follow along with your refill period by referencing **Settings** > **Billing and usage**. Alternatively, purchase [Reload credits](/support-and-community/plans-and-billing/add-on-credits/), or enable auto-reload with a monthly spend limit, to continue using premium models beyond your included quota. Users still on legacy Pro, Turbo, or Lightspeed plans continue to use [Overages (Legacy)](/support-and-community/plans-and-billing/overages-legacy/) until their first renewal after December 1, 2025. :::note Unused credits do not rollover to the next cycle and can't be transferred to other accounts. ::: +### How do credits work for multi-seat teams? + +On the new multi-seat paid plans, credits attribute differently than they did on Warp's older pooled-credit teams: + +* **Plan-included monthly credits** — Each seat receives its own monthly credit allowance that resets every 30 days based on the team's renewal date. See [warp.dev/pricing](https://www.warp.dev/pricing) for the current per-seat allowance on your plan. +* **Reload credits** — As of May 14, 2026, [Reload credits](/support-and-community/plans-and-billing/add-on-credits/) are scoped to the individual user who purchased or was allocated them, not pooled across the team. A single heavy user can no longer drain the whole team's purchased credits. +* **Grandfathered pooled credits** — Teams that purchased Reload credits (formerly Add-on Credits) before May 14, 2026 keep their existing pooled balance until it's exhausted. Pooled credits are spent down first across the team; all new Reload credit purchases after May 14, 2026 are user-scoped. +* **Team-wide spend cap** — Admins set a single team-wide monthly spend cap that governs auto-reload across the team. See [How does auto-reload work for teams?](#how-does-auto-reload-work-for-teams) below. + +Enterprise plans support team-scoped credit pools and per-user spend limits separately — see [enterprise billing](/enterprise/support-and-resources/billing/). + +### How do platform credits factor in? + +Warp meters credits across three buckets: **AI credits** (the model call), **compute credits** (the sandbox a cloud agent runs in), and **platform credits** (run lifecycle, integrations, dashboard, APIs, and observability). All three draw from the same pool — your monthly Warp credits first, then [Reload credits](/support-and-community/plans-and-billing/add-on-credits/) once those are exhausted. + +Platform credits apply in two situations: + +* **Every cloud agent run, on every plan.** Warp's platform infrastructure coordinates every cloud run regardless of which agent or inference source it uses. +* **Local agent runs on Business and Enterprise that use customer-supplied inference** — BYOK, BYOLLM via Amazon Bedrock or Google Vertex, or a custom inference endpoint. Warp isn't paying for the model call, but Warp's platform infrastructure is still running the agent. + +Local agent runs on Free, Build, or Max — and local runs on Business or Enterprise that use Warp-managed inference — do not consume platform credits. See [platform credits](/support-and-community/plans-and-billing/platform-credits/) for the full breakdown. + +### What if I need more AI usage than my plan includes? + +If you regularly run through your plan's monthly credit allowance, you have a few options: + +* **Upgrade to Max** — Designed for developers with heavier AI usage. Max includes a higher monthly credit allowance than Build, plus a better effective rate for credits than buying [Reload credits](/support-and-community/plans-and-billing/add-on-credits/) on Build. See [warp.dev/pricing](https://www.warp.dev/pricing) for current allowances. +* **Purchase Reload credits** — Top up your account on demand at $10 / 400 credits, $20 / 1,000 credits, $50 / 3,000 credits, or $100 / 6,500 credits. Larger denominations have a better effective rate. Reload credits roll over month-to-month and remain valid for 12 months. +* **Enable auto-reload** — Pick a denomination and a monthly spend cap, and Warp will automatically purchase Reload credits when your balance drops below 100 credits, up to your cap. +* **Bring your own API key (BYOK)** — Point Warp at your own OpenAI, Anthropic, or Google API key. Requests routed through BYOK don't consume Warp credits — you're billed directly by the model provider. See [Bring Your Own API Key](/support-and-community/plans-and-billing/bring-your-own-api-key/). On Business and Enterprise, platform credits may apply for local agent runs — see [platform credits](/support-and-community/plans-and-billing/platform-credits/). +* **Use a custom inference endpoint** — Route requests through any OpenAI-compatible endpoint (OpenRouter, LiteLLM, z.ai, an internal gateway, etc.) without spending Warp credits. See [Custom Inference Endpoint](/support-and-community/plans-and-billing/custom-inference-endpoint/). On Business and Enterprise, platform credits may apply for local agent runs — see [platform credits](/support-and-community/plans-and-billing/platform-credits/). + +*BYOK and custom inference endpoint availability is subject to organization size — see [Can I bring my own API key?](#can-i-bring-my-own-api-key) for details.* + +For organization-scale needs (cloud-provider managed inference, granular admin controls, or higher seat counts), Enterprise plans include [Bring Your Own LLM (BYOLLM)](/enterprise/enterprise-features/bring-your-own-llm/). + +### How does auto-reload work for teams? + +Auto-reload prevents team members from getting blocked by credit exhaustion. It works the same way for single-user and multi-seat paid plans, with one extra knob for teams. + +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. +* All auto-reload purchases count against a single **team-wide monthly spend cap** that the admin sets. Once the team hits the cap in a given month, auto-reload pauses until the next billing cycle or until the admin raises the cap. + +When auto-reload is **off**, users keep working as long as they have plan credits, previously purchased Reload credits, or have routed Warp at their own API key or [custom inference endpoint](/support-and-community/plans-and-billing/custom-inference-endpoint/). Once those run out, premium-model usage is blocked until credits are topped up or the next billing cycle begins. + +Auto-reload can be enabled, paused, or reconfigured at any time in **Settings** > **Billing and usage**. + +### How are service account / team-scoped API key requests billed on self-serve plans? + +Some AI requests on Warp can't be linked to an individual user — for example, requests made with a team-scoped API key, a scheduled agent, or an agent identity. These requests have no individual *task billing principal*. On self-serve plans (Build, Max, Business), Warp bills these requests against the **team owner**, while attribution stays on the service account. + +The waterfall on the owner's account is: + +1. First, the owner's plan-included monthly credits are consumed. +2. Once those are exhausted, the owner's Reload credits are consumed. + +When auto-reload is **off**, the service account is blocked once both buckets are depleted. When auto-reload is **on**, service-account usage can trigger auto-reload on the owner's pool subject to the team-wide spend cap; further service-account requests then deplete that reloaded balance until the cap is reached. + +This waterfall keeps usage attributable to the service account in audit logs and usage breakdowns, while making billing predictable for the team owner. + +:::note +Enterprise plans support team-scoped credit pools, so service-account and scheduled-agent traffic draws from the team pool rather than an individual admin. When the team pool is depleted, traffic falls to pay-as-you-go (PAYG) if enabled in the contract; otherwise it's blocked. See [enterprise billing](/enterprise/support-and-resources/billing/). +::: + ### Can I use a Free plan if I'm a developer at a large company or organization? Yes. Developers at any company size are welcome to use Warp’s Free plan. @@ -173,12 +242,32 @@ For more details, please [visit the Security Overview](https://www.warp.dev/lega ### What happened to the Lite model? -Over time, the Lite model—originally designed as a fallback when premium models ran out—began to deliver inconsistent results, especially for users running complex, multi-step prompts. +Over time, the Lite model — originally designed as a fallback when premium models ran out — began to deliver inconsistent results, especially for users running complex, multi-step prompts. -For credit-efficient usage, we encourage you to try our new **Auto (cost-efficiency) model**, which automatically selects the optimal model based on task complexity to help extend your credits. To continue AI usage please either add [Add-on Credits](/support-and-community/plans-and-billing/add-on-credits/) or consider [using your own API key](/support-and-community/plans-and-billing/bring-your-own-api-key/). +For credit-efficient usage, we encourage you to try our new **Auto (cost-efficiency) model**, which automatically selects the optimal model based on task complexity to help extend your credits. To continue AI usage beyond your included credits, you can purchase [Reload credits](/support-and-community/plans-and-billing/add-on-credits/), [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/). BYOK and custom inference endpoints don't consume Warp credits, since requests go directly to your provider. If you have any questions or feedback, please connect with us in our [community Slack](/support-and-community/#sending-warp-feedback). +### Can I bring my own API key? + +Yes. On Free, Build, Max, Business, and Enterprise plans, you can configure your own OpenAI, Anthropic, or Google API key in **Settings** > **AI** > **Manage models**. Requests routed through your own key don't consume Warp credits — you're billed directly by the model provider. + +See [Bring Your Own API Key](/support-and-community/plans-and-billing/bring-your-own-api-key/) for setup steps, the list of supported providers and models, and the differences between BYOK, custom inference endpoints, and BYOLLM. + +BYOK and custom inference endpoint support are available for individual users and organizations with 10 or fewer employees, subject to Warp's Terms of Service. Companies or organizations with more than 10 employees require a Warp Business or Enterprise plan to use these features. + +On Business and Enterprise, local agent runs that use BYOK still consume platform credits for Warp's platform infrastructure. See [platform credits](/support-and-community/plans-and-billing/platform-credits/). + +### Does Warp support custom inference endpoints? + +Yes. In addition to BYOK, Warp can route requests to any OpenAI-compatible inference endpoint — including OpenRouter, LiteLLM, z.ai, and internal gateways your team already runs. Custom inference endpoint requests also don't consume Warp credits. + +Custom inference endpoints are available on Free, Build, Max, Business, and Enterprise. See [Custom Inference Endpoint](/support-and-community/plans-and-billing/custom-inference-endpoint/) for configuration steps, billing behavior, and how custom inference endpoints differ from BYOK and from Enterprise's [Bring Your Own LLM (BYOLLM)](/enterprise/enterprise-features/bring-your-own-llm/) managed inference. + +BYOK and custom inference endpoint support are available for individual users and organizations with 10 or fewer employees, subject to Warp's Terms of Service. Companies or organizations with more than 10 employees require a Warp Business or Enterprise plan to use these features. + +On Business and Enterprise, local agent runs that use a custom inference endpoint still consume platform credits for Warp's platform infrastructure. See [platform credits](/support-and-community/plans-and-billing/platform-credits/). + ### What payment options are available for Warp's self-service plans? Warp uses Stripe as our payments processor and currently accepts the following payment methods: credit card, debit card, Link, Apple Pay, Google Pay. @@ -231,122 +320,59 @@ The team at Warp is standing by and ready to help. For subscribers technical iss --- -### Warp's pricing change FAQs (Oct 30, 2025) - -For more details, see this blog post on [Warp's plan changes](https://www.warp.dev/blog/warp-new-pricing-flexibility-byok). - -#### How do I change from my current plan to the new Build or Business plan? - -You can switch to the new Warp Build or Business plan anytime from **Settings** > **Billing and usage** > **Manage billing** > **Update subscription** in the Warp app or at [app.warp.dev/upgrade](https://app.warp.dev/upgrade). Select Change plan, then choose the plan that fits your needs. - -If you take no action, your Pro, Turbo, Lightspeed, or legacy Business plan will automatically move to the new structure on your first renewal after **December 1, 2025**. You’ll receive an email before your renewal with details to make the transition easier. - -#### What happens when I change from my legacy plan to the new Build or Business plans? - -If you move from Warp’s legacy Pro, Turbo, Lightspeed, or old Business plans to the new Build or Business plans: - -* You’ll receive a prorated credit balance on Stripe for your current plan, based on how far you are into your billing cycle. This balance can be applied toward monthly Build fees or any Add-on Credits you purchase. - * You can view your credit balance by going to **Settings** > **Billing and usage** > **Manage Account**. You can also view your credit balance on the Stripe invoice that was sent when your plan changed to Build or Business. -* Your credit balance will reset to **0/1,500** when you switch to the Build or Business plan. - -If you switched immediately after the rollout, before a subsequent update was applied, we’ll retroactively reset your credit balance to 0/1,500. - -* You should see this reflected in **Settings** > **Billing and usage**. If you experience any issues, please contact us at **build-priority@warp.dev**. - -:::note -We recommend you use all the credits on your legacy plan before you switch over to the new plans. This way you can make best use of them before they are reset to the new plan limits. -::: - -:::caution -Add-on credit auto reload will be enabled by default for some legacy plan users when they transition to the Build plan. Please see more in our [Pricing FAQs](/support-and-community/plans-and-billing/pricing-faqs/#what-happens-to-my-current-plan-pro-turbo-lightspeed). -::: - -#### What should I keep in mind about this change? - -* **BYOK and Add-on credits**: These are only available on the new Build and Business plans. Switching early gives you immediate access. -* **Pricing differences**: Depending on your usage, your monthly cost may increase or decrease. You’ll now pay based on what you actually use. -* **Renewal timing**: You’ll stay on your current plan until your renewal date after December 1. No interruptions to service will occur. -* **Transparency**: You can view your credit balance, monthly spend limit, and Add-on settings anytime in **Settings** > **Billing and usage**. - -For full details, see [warp.dev/pricing](https://www.warp.dev/pricing) or reach out to billing@warp.dev if you have questions about your transition. - -#### For existing paid users: when will the new pricing take effect for my account? - -For **new customers**, the new pricing and packaging take effect immediately on Oct 30, 2025. - -For **existing monthly subscribers**, changes will apply on your first renewal after **December 1, 2025**; most likely during the month of December 2025. For **annual subscribers**, the new plan and pricing will take effect on your next renewal after December 1, 2025. - -If you have any questions, please reach out to us at **billing@warp.dev**. - -#### **What happens to my current plan (Pro, Turbo, Lightspeed, Business)?** - -You will retain your current plan and credits until the first renewal after December 1, 2025. At renewal, all current Pro, Turbo, Lightspeed, and Business plans will transition to the new Warp Build and Business plans. - -The Build and new Business plans include 1,500 monthly credits, the ability to purchase [Add-on Credits](/support-and-community/plans-and-billing/add-on-credits/) that roll over for 12 months, and the ability to bring your own API key. Learn more at [warp.dev/pricing](https://www.warp.dev/pricing). - -In addition, [Add-on credit auto reload](/support-and-community/plans-and-billing/add-on-credits/#id-2.-enable-auto-reload) will be automatically enabled for some legacy plan users in the following ways (but can be opted out of or modified at any time). Our goal is to maintain the same maximum monthly spend in line with your legacy plan subscription plus any Overages: - -* **Pro:** Will transition to the Build plan. Auto-reload _**will not**_** be enabled by default**. -* **Turbo:** Will transition to the Build plan. Auto-reload _**will**_** be enabled by default**. It will default to $30 auto-reload monthly spending limit for monthly subscribers and $22 for yearly subscribers. A handful of Turbo subscribers received a bulk discount for teams of 3 or more—please check your email for details on the default spending limits for your account. -* **Lightspeed:** Will transition to the Build plan. Auto-reload _**will**_** be enabled by default**. It will default to $205 auto-reload monthly spending limit for monthly subscribers and $182 for yearly subscribers. -* **Business:** Will transition to the new Business plan. Auto-reload _**will**_** be enabled by default**. It will default to $10 auto-reload monthly spending limit for both monthly and yearly subscribers. - -In any of the above cases, if Overages were enabled, we will set the monthly auto-reload spending limit equal to your Overage spending limit plus any of the amounts listed above.\ -\ -If your total auto-reload monthly spend limit is $80 or above, we will set the Add-on credit denomination to $20 / 1000 credits by default. If your total auto reload monthly spending limit is below $80, we will set the Add-on credit denomination to $10 / 400 credits by default. - -#### Can I continue to use Warp as my primary terminal? - -Yes, the terminal features of Warp will continue to be free to use for developers. Learn more at [Plans And Pricing](/support-and-community/plans-and-billing/plans-pricing-refunds/). +### Warp's pricing change FAQs (May 14, 2026) -#### How are Add-on credits different from overages? +The following questions cover the May 14, 2026 pricing updates: seat limits per plan, Reload credits attribution, Max plan credit allowance changes, BYOK on Free, the new Custom Inference Endpoint feature, and ZDR / data-controls clarifications. -Add-on credits replace overages with a simpler, prepaid system. They’re up to \~40% cheaper than the old overage rates, roll over month-to-month, and remain valid for 12 months. They also come with Warp’s full SOC 2 / Zero Data Retention protection. +#### Are there new seat limits per plan? -#### Do credits rollover? +Yes. As of May 14, 2026, each plan has an explicit seat limit. See [warp.dev/pricing](https://www.warp.dev/pricing) for the current per-plan caps. -For existing users on legacy plans, Warp credits on Pro, Turbo, and Lightspeed do not rollover. +Teams that already exceed the new seat limit on their current plan remain in good standing — you won't be downgraded or charged differently. However, you **cannot add new members above the seat cap**, including backfilling members who leave. To grow past the cap, switch to the next plan up (or to Enterprise) at any time in **Settings** > **Billing and usage**. -For the Build plan, credits will not rollover but Add-on credits will rollover and be valid for 12 months from the date of purchase. +#### How are Reload credits being attributed differently? -#### Can I purchase Add-on Credits on legacy plans (Pro, Turbo, Lightspeed)? +Before May 14, 2026, Reload credits (previously called Add-on Credits) on multi-seat teams were **pooled** — every team member drew from a single shared balance. As of May 14, 2026, **Reload credits are user-scoped**: each user has their own balance, and a single heavy user can no longer drain the whole team's purchased credits. -No. Add-on Credits (including auto-reload) are only available on the Build, Business, and Enterprise plans. If you attempt to purchase Add-on Credits on a legacy plan, the purchase will not go through. To access Add-on Credits, switch to the Build plan at any time from **Settings** > **Billing and usage** or at [app.warp.dev/upgrade](https://app.warp.dev/upgrade). If you need additional usage while on a legacy plan, you can use [Overages (Legacy)](/support-and-community/plans-and-billing/overages-legacy/) instead. +**Grandfathering for pre-May 2026 pooled credits**: Existing pooled Reload credit balances are honored. They drain first across the team before any new user-scoped Reload credits are consumed. No new credits will be added to the pooled balance — once it's exhausted, all future Reload credit purchases are user-scoped. -#### Can I bring my own key on legacy plans (Pro, Turbo, Lightspeed)? +For details, see [Reload credits](/support-and-community/plans-and-billing/add-on-credits/). -No, Bring-your-own API key for OpenAI, Anthropic, and Gemini is only available to users on the Warp Build plan. You can choose to switch your existing plan to Warp Build at any time before your applicable renewal date to access BYOK. +#### Is the Max plan's monthly credit allowance changing? -#### How does the monthly spend limit on Add-on Credits work? +Yes. The Max plan's monthly credit allowance is decreasing as of May 14, 2026. For the current allowance, see [warp.dev/pricing](https://www.warp.dev/pricing). -You set a monthly spend limit that applies to your AI usage for each calendar month. This limit acts as the maximum amount you can spend on credits during that period. +**Grandfathering for existing Max subscribers**: -If a purchase would exceed your limit, it won’t go through—you’ll need to either increase your limit or choose a smaller purchase amount. +* **Annual subscribers** are honored at the prior credit allowance through the end of their current annual contract. The new allowance takes effect on the first renewal after the contract ends. +* **Monthly subscribers** are honored at the prior credit allowance until their first renewal or payment on or after **July 1, 2026**. The new allowance takes effect at that renewal. +* **Any plan change forfeits grandfathering** — switching to or from Max during the grandfather window moves you to the new allowance immediately. -**For auto reload settings:** +Confirm the exact allowance applied to your account in **Settings** > **Billing and usage**. -* New users who enable auto reload will start with a $200 spend limit. -* Existing paid plan users who enable auto reload will have their limit match their existing Overages spend limit (if previously configured, otherwise $200). +#### Can I bring my own API key on the Free plan now? -#### I’m an individual developer and need more than 1,500 credits per month. What’s the right plan for me? +Yes. As of May 14, 2026, **bring your own API key (BYOK)** is available on all plans, including Free. Previously, BYOK required a Build, Business, or Enterprise subscription. You can configure your OpenAI, Anthropic, or Google key in **Settings** > **AI** > **Manage models**. -If you regularly use more than 1,500 credits per month, the Build plan is designed for you. It includes 1,500 monthly credits and gives you the flexibility to scale further with Add-on Credits, which you can purchase at discounted rates directly under **Settings** > **Billing and usage**. +See [Bring Your Own API Key](/support-and-community/plans-and-billing/bring-your-own-api-key/) for the full list of supported providers and setup steps. -Add-on Credits roll over month to month, remain valid for 12 months, and offer up to \~40% savings for larger denominations. You can also enable auto reload to automatically top up your credits when your balance runs low. +#### What is the new Custom Inference Endpoint feature? -If you’re part of a team that needs shared credit management, SSO, or enforced Zero Data Retention (ZDR), the Business plan provides all the same AI capabilities plus advanced security and administrative features. +**Custom Inference Endpoint (CIE)** is a new way to route Warp's AI traffic through any OpenAI-compatible inference endpoint — including OpenRouter, LiteLLM, z.ai, and internal gateways your team already runs. CIE is available on Free, Build, Max, Business, and Enterprise. -#### Should I subscribe to the Build plan or the Business plan? +CIE differs from BYOK and BYOLLM: -If you’re an individual developer or part of a small team, the Build plan is the best fit. It includes 1,500 monthly credits, discounted Add-on Credits for additional usage, and the ability to bring your own API key (BYOK) for OpenAI, Anthropic, or Google models. You’ll also get unlimited Warp Drive objects, collaboration tools, and the highest codebase indexing limits. +* **BYOK** sends requests directly to OpenAI, Anthropic, or Google using your own provider API key. +* **Custom inference endpoint** sends requests to any OpenAI-compatible URL you control (or that your team runs). +* **BYOLLM** is an Enterprise-only managed inference feature where Warp routes traffic through your AWS Bedrock, Google Vertex, Azure Foundry, or internal LLM gateway with full routing, orchestration, governance, and observability provided by Warp. -If you’re part of a larger team (up to 50 members) that needs advanced administrative and security controls, choose the Business plan. It includes everything in Build, plus SSO, enforced Zero Data Retention (ZDR), shared Add-on Credits that can be used by all team members, and centralized billing – ideal for organizations that need stronger security, compliance, and team-wide management. +For setup and details, see [Custom Inference Endpoint](/support-and-community/plans-and-billing/custom-inference-endpoint/). -#### How do credits work for multi-seat teams? +#### How does Zero Data Retention (ZDR) work on the new plans? -For teams on the Build or Business plans, credits are managed at two levels: +Two distinct things are sometimes both called "ZDR" — May 14, 2026 makes the distinction clearer: -* **Included monthly credits**: Each seat on a paid plan receives 1,500 individual credits per month. These credits are tied to the user and reset every 30 days based on their subscription or renewal date. -* **Add-on Credits**: Once individual credits are used up, team members draw from a shared Add-on Credit balance that can be topped up and managed by team admins. +* **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." -This shared model gives teams the flexibility to handle variable AI usage – heavy users can consume more when needed, while the entire team benefits from shared value and volume-based discounts. +If you previously relied on the "automatically enforced team-wide ZDR" language on Business, your data controls are unchanged — Warp still does not retain your team's data for training, and admins can still configure retention. The terminology change disambiguates Warp's controls from the provider-level ZDR that applies to every plan. From 372f6ccb36f73fca2802fe9289ef7f2879d78a8a Mon Sep 17 00:00:00 2001 From: Hong Yi Chen Date: Tue, 19 May 2026 17:09:27 -0700 Subject: [PATCH 02/15] docs(pricing-may-2026): add platform-credits preview FAQ, trim legacy plan content MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - 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 --- .../plans-and-billing/pricing-faqs.mdx | 27 ++++++++++++------- 1 file changed, 18 insertions(+), 9 deletions(-) diff --git a/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx b/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx index 67b1f97b..6ae52363 100644 --- a/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx +++ b/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx @@ -35,13 +35,7 @@ Warp's plans are designed for developers who rely on AI to code, debug, and move * **Business** — Multi-seat plan for teams. Includes everything in Build, plus admin-configurable data controls, SAML-based SSO, and centralized billing. Available up to the seat limit listed at [warp.dev/pricing](https://www.warp.dev/pricing). * **Enterprise** — Custom plan for organizations that need higher seat counts, [Bring Your Own LLM (BYOLLM)](/enterprise/enterprise-features/bring-your-own-llm/) managed inference, granular admin controls, advanced security and compliance, and dedicated support. -Legacy plans (**no longer available for new subscribers**): - -* **Pro** included higher credit limits than the Free plan, support for larger codebases with [Codebase Context](/agent-platform/capabilities/codebase-context/), and access to premium models with optional pay-as-you-go [Overages (Legacy)](/support-and-community/plans-and-billing/overages-legacy/). -* **Turbo** included even higher credit limits, larger Codebase Context indexing, and the option to pay for additional usage beyond included credits via [Overages (Legacy)](/support-and-community/plans-and-billing/overages-legacy/). Add-on Credits were not available on this plan. -* **Lightspeed** was Warp's most powerful legacy plan, offering the highest credit limits, expanded codebase indexing, access to top-tier models, and pay-as-you-go [Overages (Legacy)](/support-and-community/plans-and-billing/overages-legacy/) so you could keep working without interruption. - -For the most up-to-date feature and usage details — including current per-plan seat limits and monthly credit allowances — visit [warp.dev/pricing](https://www.warp.dev/pricing). +For details on Warp's legacy plans (Pro, Turbo, Lightspeed), see [Overages (Legacy)](/support-and-community/plans-and-billing/overages-legacy/). For the most up-to-date feature and usage details — including current per-plan seat limits and monthly credit allowances — visit [warp.dev/pricing](https://www.warp.dev/pricing). ### How can I subscribe to a Warp Enterprise plan? @@ -142,11 +136,11 @@ Warp now abstracts away token usage, so you don't need to manage or track it dir If you're curious, you can read the [OpenAI article on tokens](https://help.openai.com/en/articles/4936856-understanding-tokens), or refer to the pricing page for plan-level credit allocations. If you reach your monthly credit limits on a paid plan, premium models will be temporarily disabled until your quota resets at the start of your next billing cycle. -If you’d like to continue using premium models beyond your included quota, purchase [Reload credits](/support-and-community/plans-and-billing/add-on-credits/) in **Settings** > **Billing and usage** (users still on legacy Pro, Turbo, or Lightspeed plans continue to use [Overages (Legacy)](/support-and-community/plans-and-billing/overages-legacy/) until their first renewal after December 1, 2025). +If you’d like to continue using premium models beyond your included quota, purchase [Reload credits](/support-and-community/plans-and-billing/add-on-credits/) in **Settings** > **Billing and usage**. ### How often do my credits reset? -Allotted credits refill every 30 days from your signup date. When you upgrade to a [paid plan](https://www.warp.dev/pricing), you will be given more credits immediately. You can follow along with your refill period by referencing **Settings** > **Billing and usage**. Alternatively, purchase [Reload credits](/support-and-community/plans-and-billing/add-on-credits/), or enable auto-reload with a monthly spend limit, to continue using premium models beyond your included quota. Users still on legacy Pro, Turbo, or Lightspeed plans continue to use [Overages (Legacy)](/support-and-community/plans-and-billing/overages-legacy/) until their first renewal after December 1, 2025. +Allotted credits refill every 30 days from your signup date. When you upgrade to a [paid plan](https://www.warp.dev/pricing), you will be given more credits immediately. You can follow along with your refill period by referencing **Settings** > **Billing and usage**. Alternatively, purchase [Reload credits](/support-and-community/plans-and-billing/add-on-credits/), or enable auto-reload with a monthly spend limit, to continue using premium models beyond your included quota. :::note Unused credits do not rollover to the next cycle and can't be transferred to other accounts. @@ -376,3 +370,18 @@ Two distinct things are sometimes both called "ZDR" — May 14, 2026 makes the d * **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." If you previously relied on the "automatically enforced team-wide ZDR" language on Business, your data controls are unchanged — Warp still does not retain your team's data for training, and admins can still configure retention. The terminology change disambiguates Warp's controls from the provider-level ZDR that applies to every plan. + +#### When do platform credits start being charged on self-serve plans? + +[Platform credits](/support-and-community/plans-and-billing/platform-credits/) apply to self-serve cloud agent runs and to Business BYOK / custom inference endpoint usage where applicable, but **self-serve billing for platform credits doesn't start until July 1, 2026**. + +Between May 14 and June 30, 2026, self-serve plans (Build, Max, Business) are in a **preview period**: platform-credit consumption is visible in the Warp app's usage breakdown for transparency, but **no platform credits are deducted from your Reload pool or counted against your spend cap**. + +On **July 1, 2026**, Warp begins charging self-serve customers platform credits for: + +* Every cloud agent run on Build, Max, or Business. +* Local agent runs on Business that use BYOK or a custom inference endpoint. + +This date lines up with the rest of the May 2026 self-serve pricing transition (seat limits, Max credit allowance change, user-scoped Reload credits, and related grandfathering changes). + +Enterprise plans are billed for platform credits per your contract from May 14 and aren't affected by this preview period. From 044e655ff7cc07a4bd21d9f63e9767f1870293b1 Mon Sep 17 00:00:00 2001 From: Hong Yi Chen Date: Wed, 20 May 2026 11:01:05 -0700 Subject: [PATCH 03/15] docs(pricing-may-2026): correct launch date May 14 \u2192 May 21, 2026 Co-Authored-By: Oz --- .../plans-pricing-refunds.mdx | 2 +- .../plans-and-billing/pricing-faqs.mdx | 22 +++++++++---------- 2 files changed, 12 insertions(+), 12 deletions(-) diff --git a/src/content/docs/support-and-community/plans-and-billing/plans-pricing-refunds.mdx b/src/content/docs/support-and-community/plans-and-billing/plans-pricing-refunds.mdx index fb673825..67005a31 100644 --- a/src/content/docs/support-and-community/plans-and-billing/plans-pricing-refunds.mdx +++ b/src/content/docs/support-and-community/plans-and-billing/plans-pricing-refunds.mdx @@ -28,7 +28,7 @@ Visit [warp.dev/pricing](https://www.warp.dev/pricing) to see the latest plans a ### May 2026 plan summary -Below is a high-level summary of Warp's plans as of May 14, 2026. Visit [warp.dev/pricing](https://www.warp.dev/pricing) for current monthly credit allowances and seat pricing. +Below is a high-level summary of Warp's plans as of May 21, 2026. Visit [warp.dev/pricing](https://www.warp.dev/pricing) for current monthly credit allowances and seat pricing. * **Free** — Up to 10 team members. For developers exploring Warp. Includes core terminal features and a monthly credit allowance for trying Warp's agents. Supports [Bring Your Own API Key](/support-and-community/plans-and-billing/bring-your-own-api-key/) and [custom inference endpoints](/support-and-community/plans-and-billing/custom-inference-endpoint/) so you can keep working with your own provider after the included allowance is used. * **Build** — Up to 10 team members. For developers using Warp's agents as a daily driver. Includes a higher monthly credit allowance than Free, [Add-on Credits](/support-and-community/plans-and-billing/add-on-credits/) with auto-reload, and the same BYOK and custom inference endpoint support as Free. diff --git a/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx b/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx index 6ae52363..a466a93f 100644 --- a/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx +++ b/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx @@ -151,8 +151,8 @@ Unused credits do not rollover to the next cycle and can't be transferred to oth On the new multi-seat paid plans, credits attribute differently than they did on Warp's older pooled-credit teams: * **Plan-included monthly credits** — Each seat receives its own monthly credit allowance that resets every 30 days based on the team's renewal date. See [warp.dev/pricing](https://www.warp.dev/pricing) for the current per-seat allowance on your plan. -* **Reload credits** — As of May 14, 2026, [Reload credits](/support-and-community/plans-and-billing/add-on-credits/) are scoped to the individual user who purchased or was allocated them, not pooled across the team. A single heavy user can no longer drain the whole team's purchased credits. -* **Grandfathered pooled credits** — Teams that purchased Reload credits (formerly Add-on Credits) before May 14, 2026 keep their existing pooled balance until it's exhausted. Pooled credits are spent down first across the team; all new Reload credit purchases after May 14, 2026 are user-scoped. +* **Reload credits** — As of May 21, 2026, [Reload credits](/support-and-community/plans-and-billing/add-on-credits/) are scoped to the individual user who purchased or was allocated them, not pooled across the team. A single heavy user can no longer drain the whole team's purchased credits. +* **Grandfathered pooled credits** — Teams that purchased Reload credits (formerly Add-on Credits) before May 21, 2026 keep their existing pooled balance until it's exhausted. Pooled credits are spent down first across the team; all new Reload credit purchases after May 21, 2026 are user-scoped. * **Team-wide spend cap** — Admins set a single team-wide monthly spend cap that governs auto-reload across the team. See [How does auto-reload work for teams?](#how-does-auto-reload-work-for-teams) below. Enterprise plans support team-scoped credit pools and per-user spend limits separately — see [enterprise billing](/enterprise/support-and-resources/billing/). @@ -314,19 +314,19 @@ The team at Warp is standing by and ready to help. For subscribers technical iss --- -### Warp's pricing change FAQs (May 14, 2026) +### Warp's pricing change FAQs (May 21, 2026) -The following questions cover the May 14, 2026 pricing updates: seat limits per plan, Reload credits attribution, Max plan credit allowance changes, BYOK on Free, the new Custom Inference Endpoint feature, and ZDR / data-controls clarifications. +The following questions cover the May 21, 2026 pricing updates: seat limits per plan, Reload credits attribution, Max plan credit allowance changes, BYOK on Free, the new Custom Inference Endpoint feature, and ZDR / data-controls clarifications. #### Are there new seat limits per plan? -Yes. As of May 14, 2026, each plan has an explicit seat limit. See [warp.dev/pricing](https://www.warp.dev/pricing) for the current per-plan caps. +Yes. As of May 21, 2026, each plan has an explicit seat limit. See [warp.dev/pricing](https://www.warp.dev/pricing) for the current per-plan caps. Teams that already exceed the new seat limit on their current plan remain in good standing — you won't be downgraded or charged differently. However, you **cannot add new members above the seat cap**, including backfilling members who leave. To grow past the cap, switch to the next plan up (or to Enterprise) at any time in **Settings** > **Billing and usage**. #### How are Reload credits being attributed differently? -Before May 14, 2026, Reload credits (previously called Add-on Credits) on multi-seat teams were **pooled** — every team member drew from a single shared balance. As of May 14, 2026, **Reload credits are user-scoped**: each user has their own balance, and a single heavy user can no longer drain the whole team's purchased credits. +Before May 21, 2026, Reload credits (previously called Add-on Credits) on multi-seat teams were **pooled** — every team member drew from a single shared balance. As of May 21, 2026, **Reload credits are user-scoped**: each user has their own balance, and a single heavy user can no longer drain the whole team's purchased credits. **Grandfathering for pre-May 2026 pooled credits**: Existing pooled Reload credit balances are honored. They drain first across the team before any new user-scoped Reload credits are consumed. No new credits will be added to the pooled balance — once it's exhausted, all future Reload credit purchases are user-scoped. @@ -334,7 +334,7 @@ For details, see [Reload credits](/support-and-community/plans-and-billing/add-o #### Is the Max plan's monthly credit allowance changing? -Yes. The Max plan's monthly credit allowance is decreasing as of May 14, 2026. For the current allowance, see [warp.dev/pricing](https://www.warp.dev/pricing). +Yes. The Max plan's monthly credit allowance is decreasing as of May 21, 2026. For the current allowance, see [warp.dev/pricing](https://www.warp.dev/pricing). **Grandfathering for existing Max subscribers**: @@ -346,7 +346,7 @@ Confirm the exact allowance applied to your account in **Settings** > **Billing #### Can I bring my own API key on the Free plan now? -Yes. As of May 14, 2026, **bring your own API key (BYOK)** is available on all plans, including Free. Previously, BYOK required a Build, Business, or Enterprise subscription. You can configure your OpenAI, Anthropic, or Google key in **Settings** > **AI** > **Manage models**. +Yes. As of May 21, 2026, **bring your own API key (BYOK)** is available on all plans, including Free. Previously, BYOK required a Build, Business, or Enterprise subscription. You can configure your OpenAI, Anthropic, or Google key in **Settings** > **AI** > **Manage models**. See [Bring Your Own API Key](/support-and-community/plans-and-billing/bring-your-own-api-key/) for the full list of supported providers and setup steps. @@ -364,7 +364,7 @@ For setup and details, see [Custom Inference Endpoint](/support-and-community/pl #### How does Zero Data Retention (ZDR) work on the new plans? -Two distinct things are sometimes both called "ZDR" — May 14, 2026 makes the distinction clearer: +Two distinct things are sometimes both called "ZDR" — May 21, 2026 makes the distinction clearer: * **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." @@ -375,7 +375,7 @@ If you previously relied on the "automatically enforced team-wide ZDR" language [Platform credits](/support-and-community/plans-and-billing/platform-credits/) apply to self-serve cloud agent runs and to Business BYOK / custom inference endpoint usage where applicable, but **self-serve billing for platform credits doesn't start until July 1, 2026**. -Between May 14 and June 30, 2026, self-serve plans (Build, Max, Business) are in a **preview period**: platform-credit consumption is visible in the Warp app's usage breakdown for transparency, but **no platform credits are deducted from your Reload pool or counted against your spend cap**. +Between May 21 and June 30, 2026, self-serve plans (Build, Max, Business) are in a **preview period**: platform-credit consumption is visible in the Warp app's usage breakdown for transparency, but **no platform credits are deducted from your Reload pool or counted against your spend cap**. On **July 1, 2026**, Warp begins charging self-serve customers platform credits for: @@ -384,4 +384,4 @@ On **July 1, 2026**, Warp begins charging self-serve customers platform credits This date lines up with the rest of the May 2026 self-serve pricing transition (seat limits, Max credit allowance change, user-scoped Reload credits, and related grandfathering changes). -Enterprise plans are billed for platform credits per your contract from May 14 and aren't affected by this preview period. +Enterprise plans are billed for platform credits per your contract from May 21 and aren't affected by this preview period. From 6f980a2916625908754fded1e7b45ecee3cdc25d Mon Sep 17 00:00:00 2001 From: Hong Yi Chen Date: Wed, 20 May 2026 17:00:54 -0700 Subject: [PATCH 04/15] docs(pricing-may-2026): drop Max credit-allowance reduction from launch 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 --- .../plans-and-billing/pricing-faqs.mdx | 16 ++-------------- 1 file changed, 2 insertions(+), 14 deletions(-) diff --git a/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx b/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx index a466a93f..b1d237c8 100644 --- a/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx +++ b/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx @@ -316,7 +316,7 @@ The team at Warp is standing by and ready to help. For subscribers technical iss ### Warp's pricing change FAQs (May 21, 2026) -The following questions cover the May 21, 2026 pricing updates: seat limits per plan, Reload credits attribution, Max plan credit allowance changes, BYOK on Free, the new Custom Inference Endpoint feature, and ZDR / data-controls clarifications. +The following questions cover the May 21, 2026 pricing updates: seat limits per plan, Reload credits attribution, BYOK on Free, the new Custom Inference Endpoint feature, and ZDR / data-controls clarifications. #### Are there new seat limits per plan? @@ -332,18 +332,6 @@ Before May 21, 2026, Reload credits (previously called Add-on Credits) on multi- For details, see [Reload credits](/support-and-community/plans-and-billing/add-on-credits/). -#### Is the Max plan's monthly credit allowance changing? - -Yes. The Max plan's monthly credit allowance is decreasing as of May 21, 2026. For the current allowance, see [warp.dev/pricing](https://www.warp.dev/pricing). - -**Grandfathering for existing Max subscribers**: - -* **Annual subscribers** are honored at the prior credit allowance through the end of their current annual contract. The new allowance takes effect on the first renewal after the contract ends. -* **Monthly subscribers** are honored at the prior credit allowance until their first renewal or payment on or after **July 1, 2026**. The new allowance takes effect at that renewal. -* **Any plan change forfeits grandfathering** — switching to or from Max during the grandfather window moves you to the new allowance immediately. - -Confirm the exact allowance applied to your account in **Settings** > **Billing and usage**. - #### Can I bring my own API key on the Free plan now? Yes. As of May 21, 2026, **bring your own API key (BYOK)** is available on all plans, including Free. Previously, BYOK required a Build, Business, or Enterprise subscription. You can configure your OpenAI, Anthropic, or Google key in **Settings** > **AI** > **Manage models**. @@ -382,6 +370,6 @@ On **July 1, 2026**, Warp begins charging self-serve customers platform credits * Every cloud agent run on Build, Max, or Business. * Local agent runs on Business that use BYOK or a custom inference endpoint. -This date lines up with the rest of the May 2026 self-serve pricing transition (seat limits, Max credit allowance change, user-scoped Reload credits, and related grandfathering changes). +This date lines up with the rest of the May 2026 self-serve pricing transition (seat limits, user-scoped Reload credits, and related grandfathering changes). Enterprise plans are billed for platform credits per your contract from May 21 and aren't affected by this preview period. From 24893614f8ad024c809b01cfb4e74c7f1a6438bc Mon Sep 17 00:00:00 2001 From: Hong Yi Chen Date: Wed, 20 May 2026 17:42:11 -0700 Subject: [PATCH 05/15] docs(pricing-may-2026): drop service-account framing from FAQs, clarify 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 --- .../plans-and-billing/pricing-faqs.mdx | 20 +++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx b/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx index b1d237c8..71e24ecb 100644 --- a/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx +++ b/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx @@ -196,21 +196,19 @@ When auto-reload is **off**, users keep working as long as they have plan credit Auto-reload can be enabled, paused, or reconfigured at any time in **Settings** > **Billing and usage**. -### How are service account / team-scoped API key requests billed on self-serve plans? +### How are cloud agent runs on team plans billed when no individual user triggered them? -Some AI requests on Warp can't be linked to an individual user — for example, requests made with a team-scoped API key, a scheduled agent, or an agent identity. These requests have no individual *task billing principal*. On self-serve plans (Build, Max, Business), Warp bills these requests against the **team owner**, while attribution stays on the service account. +Some cloud agent runs aren't initiated by a specific team member — for example, scheduled runs or runs triggered through a team API key. On self-serve plans (Build, Max, Business), these runs are billed to the **team owner**. The waterfall on the owner's account is: 1. First, the owner's plan-included monthly credits are consumed. 2. Once those are exhausted, the owner's Reload credits are consumed. -When auto-reload is **off**, the service account is blocked once both buckets are depleted. When auto-reload is **on**, service-account usage can trigger auto-reload on the owner's pool subject to the team-wide spend cap; further service-account requests then deplete that reloaded balance until the cap is reached. - -This waterfall keeps usage attributable to the service account in audit logs and usage breakdowns, while making billing predictable for the team owner. +When auto-reload is **off**, the request is blocked once both buckets are depleted. When auto-reload is **on**, cloud agent usage can trigger auto-reload on the owner's pool subject to the team-wide spend cap; further cloud agent runs then draw from that reloaded balance until the cap is reached. :::note -Enterprise plans support team-scoped credit pools, so service-account and scheduled-agent traffic draws from the team pool rather than an individual admin. When the team pool is depleted, traffic falls to pay-as-you-go (PAYG) if enabled in the contract; otherwise it's blocked. See [enterprise billing](/enterprise/support-and-resources/billing/). +Enterprise plans support team-scoped credit pools, so this traffic draws from the team pool rather than an individual admin. When the team pool is depleted, traffic falls to pay-as-you-go (PAYG) if enabled in the contract; otherwise it's blocked. See [enterprise billing](/enterprise/support-and-resources/billing/). ::: ### Can I use a Free plan if I'm a developer at a large company or organization? @@ -361,15 +359,17 @@ If you previously relied on the "automatically enforced team-wide ZDR" language #### When do platform credits start being charged on self-serve plans? -[Platform credits](/support-and-community/plans-and-billing/platform-credits/) apply to self-serve cloud agent runs and to Business BYOK / custom inference endpoint usage where applicable, but **self-serve billing for platform credits doesn't start until July 1, 2026**. +[Platform credits](/support-and-community/plans-and-billing/platform-credits/) apply to every cloud agent run, plus local agent runs on Business that use BYOK or a custom inference endpoint. **For self-serve paid plans (Build, Max, Business), platform-credits billing doesn't start until July 1, 2026.** -Between May 21 and June 30, 2026, self-serve plans (Build, Max, Business) are in a **preview period**: platform-credit consumption is visible in the Warp app's usage breakdown for transparency, but **no platform credits are deducted from your Reload pool or counted against your spend cap**. +Between May 21 and June 30, 2026, self-serve paid plans are in a **preview period**: platform-credit consumption is visible in the Warp app's usage breakdown for transparency, but **no platform credits are deducted from your Reload pool or counted against your spend cap**. -On **July 1, 2026**, Warp begins charging self-serve customers platform credits for: +On **July 1, 2026**, Warp begins charging self-serve paid plans for: * Every cloud agent run on Build, Max, or Business. * Local agent runs on Business that use BYOK or a custom inference endpoint. This date lines up with the rest of the May 2026 self-serve pricing transition (seat limits, user-scoped Reload credits, and related grandfathering changes). -Enterprise plans are billed for platform credits per your contract from May 21 and aren't affected by this preview period. +**Free plan** cloud agent runs continue to draw from your plan-included credits as they always have — the preview period doesn't apply to Free, and there's no change to how Free is billed for cloud agent runs. + +**Enterprise plans** are billed for platform credits per your contract from May 21 and aren't affected by this preview period. From 29d9cd574bb19ee36cf3fe68f3f89bf1ed22bf9d Mon Sep 17 00:00:00 2001 From: Hong Yi Chen Date: Wed, 20 May 2026 17:44:49 -0700 Subject: [PATCH 06/15] Drop PAYG mention from Enterprise note in cloud-agent-runs FAQ Co-Authored-By: Oz --- .../support-and-community/plans-and-billing/pricing-faqs.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx b/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx index 71e24ecb..c11fc027 100644 --- a/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx +++ b/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx @@ -208,7 +208,7 @@ The waterfall on the owner's account is: When auto-reload is **off**, the request is blocked once both buckets are depleted. When auto-reload is **on**, cloud agent usage can trigger auto-reload on the owner's pool subject to the team-wide spend cap; further cloud agent runs then draw from that reloaded balance until the cap is reached. :::note -Enterprise plans support team-scoped credit pools, so this traffic draws from the team pool rather than an individual admin. When the team pool is depleted, traffic falls to pay-as-you-go (PAYG) if enabled in the contract; otherwise it's blocked. See [enterprise billing](/enterprise/support-and-resources/billing/). +Enterprise plans support team-scoped credit pools, so this traffic draws from the team pool rather than an individual admin. See [enterprise billing](/enterprise/support-and-resources/billing/) for overage and contract terms. ::: ### Can I use a Free plan if I'm a developer at a large company or organization? From 907ba2fbb922bfeedbe11cb7d3596bd688b0cc7b Mon Sep 17 00:00:00 2001 From: Hong Yi Chen Date: Wed, 20 May 2026 18:05:16 -0700 Subject: [PATCH 07/15] Address PR #116 review feedback - 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 --- .../docs/enterprise/team-management/teams.mdx | 16 ++----- .../knowledge-and-collaboration/teams.mdx | 12 ++--- .../plans-and-billing/index.mdx | 1 - .../plans-and-billing/overages-legacy.mdx | 43 ------------------ .../plans-pricing-refunds.mdx | 20 +-------- .../plans-and-billing/pricing-faqs.mdx | 44 +++++-------------- src/sidebar.ts | 1 - vercel.json | 12 ++--- 8 files changed, 24 insertions(+), 125 deletions(-) delete mode 100644 src/content/docs/support-and-community/plans-and-billing/overages-legacy.mdx diff --git a/src/content/docs/enterprise/team-management/teams.mdx b/src/content/docs/enterprise/team-management/teams.mdx index fed7fa48..524ae65f 100644 --- a/src/content/docs/enterprise/team-management/teams.mdx +++ b/src/content/docs/enterprise/team-management/teams.mdx @@ -68,21 +68,11 @@ If you're a Team Owner and choose to [delete your Warp account](/support-and-com On Build, Max, and Business plans, [Reload credits](/support-and-community/plans-and-billing/add-on-credits/) are scoped to the individual user under your team. Membership changes affect access to those credits: -:::caution -**Leaving the team.** If you leave this team, you'll lose access to any remaining Reload credits tied to it. If you rejoin the same team later, you'll regain access to any unused, non-expired credits. -::: - -:::caution -**An admin removes a member.** When an admin removes a member, that member loses access to any remaining Reload credits tied to this team. If they rejoin later, they'll regain access to any unused, non-expired credits. -::: +* **Leaving the team** - You lose access to any remaining Reload credits tied to it. If you rejoin the same team later, you regain access to any unused, non-expired credits. +* **An admin removes a member** - That member loses access to any remaining Reload credits tied to the team. If they rejoin later, they regain access to any unused, non-expired credits. +* **An admin deletes the team** - All members lose access to any remaining Reload credits tied to the team. -:::caution -**An admin deletes the team.** Deleting this team will remove all members' access to any remaining Reload credits tied to it. Team members will no longer be able to use those credits. -::: - -:::note Reload credits require an active subscription. Downgrading to the Free plan forfeits access to Reload credits tied to your team. Pre-launch pooled balances are grandfathered and drain first. -::: ## Team discoverability diff --git a/src/content/docs/knowledge-and-collaboration/teams.mdx b/src/content/docs/knowledge-and-collaboration/teams.mdx index 3474ca74..dfcc0b7a 100644 --- a/src/content/docs/knowledge-and-collaboration/teams.mdx +++ b/src/content/docs/knowledge-and-collaboration/teams.mdx @@ -67,17 +67,13 @@ If you have received an invite link, you can use that link to sign up or log in If you’re a member of a team, you can visit **Settings** > **Teams** to leave a team at any time. Team admins (who created teams) may delete a team only after removing all team members. -:::caution -**Leaving a paid team forfeits access to Reload credits tied to it.** [Reload credits](/support-and-community/plans-and-billing/add-on-credits/) are scoped to your individual user under your team. If you leave a paid team, you lose access to any remaining Reload credits attributed to you. If you rejoin the same team later, you regain access to any unused, non-expired credits. -::: +On Build, Max, and Business plans, [Reload credits](/support-and-community/plans-and-billing/add-on-credits/) are scoped to your individual user under your team. Membership changes affect access to those credits: -:::caution -**Deleting a team removes all members' access to Reload credits.** If an admin deletes the team, every member loses access to any remaining [Reload credits](/support-and-community/plans-and-billing/add-on-credits/) attributed to them under that team. -::: +* **Leaving the team** - You lose access to any remaining Reload credits attributed to you. If you rejoin the same team later, you regain access to any unused, non-expired credits. +* **An admin removes a member** - That member loses access to any remaining Reload credits attributed to them under this team. If they rejoin later, they regain access to any unused, non-expired credits. +* **An admin deletes the team** - All members lose access to any remaining Reload credits attributed to them under that team. -:::note Reload credits require an active subscription. Downgrading to the Free plan also forfeits access to Reload credits. -::: ## Team discoverability diff --git a/src/content/docs/support-and-community/plans-and-billing/index.mdx b/src/content/docs/support-and-community/plans-and-billing/index.mdx index 692b4fc9..c3de2b05 100644 --- a/src/content/docs/support-and-community/plans-and-billing/index.mdx +++ b/src/content/docs/support-and-community/plans-and-billing/index.mdx @@ -11,5 +11,4 @@ Warp offers flexible plans for individual developers, teams, and enterprises, wi * [**Credits**](/support-and-community/plans-and-billing/credits/) - How credits are used and calculated across AI features * [**Add-on Credits**](/support-and-community/plans-and-billing/add-on-credits/) - Purchase additional credits or enable automatic reloads * [**Bring Your Own API Key**](/support-and-community/plans-and-billing/bring-your-own-api-key/) - Connect your own model provider API keys -* [**Overages (Legacy)**](/support-and-community/plans-and-billing/overages-legacy/) - Information for users on legacy plans with overages * [**Pricing FAQs**](/support-and-community/plans-and-billing/pricing-faqs/) - Answers to common questions about plans and billing diff --git a/src/content/docs/support-and-community/plans-and-billing/overages-legacy.mdx b/src/content/docs/support-and-community/plans-and-billing/overages-legacy.mdx deleted file mode 100644 index 2aacddd7..00000000 --- a/src/content/docs/support-and-community/plans-and-billing/overages-legacy.mdx +++ /dev/null @@ -1,43 +0,0 @@ ---- -title: Overages (Legacy) -description: >- - Pay-as-you-go access to premium AI models after reaching your monthly - credits quota on Warps plans. ---- - -Warp offers usage-based pricing for Subscribers, allowing continued access to premium AI models even after reaching the monthly credits limit included in the plan (billed at $0.04 per additional credit). - -You can manage usage-based pricing directly in Warp under **Settings** > **Billing and usage**. - -
-![Billing and usage tab in settings, where admins can manage premium model usage overages](../../../../assets/support-and-community/overages-settings.png) -
Billing and usage settings.
-
- -### Enabling overages - -**Team admins** can enable or disable "premium model overages" and set a monthly spending limit from the settings dashboard. Individual subscribers can manage their own overage settings directly in the settings dashboard. - -:::note -Usage-based pricing only applies after you’ve reached the credit limit on your plan — you won’t be charged for any overages until that point, even if overages are enabled. -::: - -### How overages work - -Overages are managed **at the team level**, even if your team only has one member (i.e. individual users). Once overages are enabled, any team member who reaches their monthly credit quota can continue to have access to premium models — with **additional usage billed at cost ($0.04 per credit)**. - -Each user on the team has their **own credit limit**, but only **credits made beyond that personal quota** are considered overages. These charges are tracked and billed **collectively** at the team level. - -For example, if your plan includes 10,000 credits per team member: - -* If **User A** reaches their 10,000 limit, any further usage by them counts towards overages. -* If **User B** has only used 2,000 credits, they still have 8,000 included credits left. -* User A's overages **do not** consume User B's remaining quota. - -Overages are **billed monthly**, or when your team accumulates **$20 worth of charges**, whichever comes first. - -### Plan upgrades and cancellations - -If you upgrade from lower to a higher plan, your monthly credit limit will update immediately to match the higher plan. (For exact limits, see our [pricing page](https://www.warp.dev/pricing).) However, **any overages incurred while on the lower plan will still be billed** — upgrading does not retroactively remove or reduce existing overage charges. - -If you cancel your subscription, you’ll retain access to premium features until the end of your current billing period. Any usage-based overages accrued during that period will be charged at the time your plan ends.\\ diff --git a/src/content/docs/support-and-community/plans-and-billing/plans-pricing-refunds.mdx b/src/content/docs/support-and-community/plans-and-billing/plans-pricing-refunds.mdx index 67005a31..b6660a1b 100644 --- a/src/content/docs/support-and-community/plans-and-billing/plans-pricing-refunds.mdx +++ b/src/content/docs/support-and-community/plans-and-billing/plans-pricing-refunds.mdx @@ -23,25 +23,8 @@ Visit [warp.dev/pricing](https://www.warp.dev/pricing) to see the latest plans a * [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. -* [Overages (Legacy)](/support-and-community/plans-and-billing/overages-legacy/) — information for users on legacy plans with overages enabled. * [Pricing FAQs](/support-and-community/plans-and-billing/pricing-faqs/) — answers to common questions about plans, billing, and usage. Don’t have Warp yet? [Download Warp](https://www.warp.dev/download) and get started for free today. -### May 2026 plan summary - -Below is a high-level summary of Warp's plans as of May 21, 2026. Visit [warp.dev/pricing](https://www.warp.dev/pricing) for current monthly credit allowances and seat pricing. - -* **Free** — Up to 10 team members. For developers exploring Warp. Includes core terminal features and a monthly credit allowance for trying Warp's agents. Supports [Bring Your Own API Key](/support-and-community/plans-and-billing/bring-your-own-api-key/) and [custom inference endpoints](/support-and-community/plans-and-billing/custom-inference-endpoint/) so you can keep working with your own provider after the included allowance is used. -* **Build** — Up to 10 team members. For developers using Warp's agents as a daily driver. Includes a higher monthly credit allowance than Free, [Add-on Credits](/support-and-community/plans-and-billing/add-on-credits/) with auto-reload, and the same BYOK and custom inference endpoint support as Free. -* **Max** — Up to 10 team members. For heavy users. Includes everything in Build with a higher monthly credit allowance and a better effective Reload rate. -* **Business** — Up to 25 team members. For small-to-midsize teams. Includes everything in Max plus team-wide collaboration features, Reload credits with admin-managed auto-reload and team-wide spend caps, SAML-based SSO, and admin-configurable data controls. Platform credits apply to cloud agent runs and to local runs that use customer-supplied inference (BYOK or CIE). -* **Enterprise** — Unlimited team members (custom contract). For organizations with advanced security, compliance, or scale needs. Includes everything in Business plus [Bring your own LLM](/enterprise/enterprise-features/bring-your-own-llm/), the [Enterprise Analytics API](/enterprise/enterprise-features/analytics-api/), per-user spend limits, advanced admin controls, and Implementation Engineer Support (a structured multi-week implementation program with hands-on guidance from Warp engineers to help your team deploy production Oz Cloud Agent use cases). Platform credits apply to all cloud agent runs and to local runs using BYOLLM, BYOK, or CIE. - -:::note -BYOK and custom inference endpoint support are available for individual users and organizations with 10 or fewer employees, subject to Warp's Terms of Service. Companies or organizations with more than 10 employees require a Warp Business or Enterprise plan to use these features. -::: - -Model provider Zero Data Retention (ZDR) applies across all plans through Warp's contracted LLM providers. See [Pricing FAQs](/support-and-community/plans-and-billing/pricing-faqs/) for details on data controls. - ### Warp’s refund policies Please review the details of our refund policies below. To request a refund, email [**billing@warp.dev**](mailto:billing@warp.dev) with information about your situation — the more context you provide, the faster we can resolve your request. @@ -64,10 +47,9 @@ If you signed up for an annual Warp subscription by mistake, we can issue a full After 15 days, we will refund you for the remaining full months on your subscription, excluding the first month. -#### Add-on Credits | Overages refund policy +#### Add-on Credits refund policy * If you purchased [Add-on Credits](/support-and-community/plans-and-billing/add-on-credits/) by mistake, you can receive a refund **as long as none of the credits have been used**. Warp cannot refund Add-on Credits if there has been any usage. Add-on Credits remain available for up to **12 months** from the date of purchase, as long as you have an active subscription — if you move to the Free plan, you'll lose access to any remaining Add-on Credits. -* All [Overages (Legacy)](/support-and-community/plans-and-billing/overages-legacy/) credits are **non-refundable**. Because Overages are charges for credits that were already consumed, we cannot refund resources that have already been used. :::caution Warp does not offer a formal guaranteed uptime Service Level Agreement (SLA). Live incidents can be monitored on our [**Status Page**](https://status.warp.dev/), and open issues are tracked on our [**GitHub Issues**](https://github.com/warpdotdev/Warp/issues). diff --git a/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx b/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx index c11fc027..0d373c10 100644 --- a/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx +++ b/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx @@ -22,20 +22,14 @@ After entering your payment details, you’ll receive an invoice and confirmatio ### How can I get the most out of my Warp plan? -:::caution -Warp's legacy paid plans included Pro, Turbo, and Lightspeed. These plans are no longer offered to new subscribers. - -For details on those legacy plans and how their usage was billed, see [Overages (Legacy)](/support-and-community/plans-and-billing/overages-legacy/). For the most up-to-date list of plans, seat limits, and credit allowances, visit [warp.dev/pricing](https://www.warp.dev/pricing). -::: - Warp's plans are designed for developers who rely on AI to code, debug, and move faster with their team. Pick the plan that matches the scale of your usage and the controls your team needs: -* **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** — For individual developers (teams up to 10). 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** — For individual developers with heavier AI usage (teams up to 10). Includes a larger monthly credit allowance than Build, plus a better effective rate for credits than buying Reload credits on Build. * **Business** — Multi-seat plan for teams. Includes everything in Build, plus admin-configurable data controls, SAML-based SSO, and centralized billing. Available up to the seat limit listed at [warp.dev/pricing](https://www.warp.dev/pricing). * **Enterprise** — Custom plan for organizations that need higher seat counts, [Bring Your Own LLM (BYOLLM)](/enterprise/enterprise-features/bring-your-own-llm/) managed inference, granular admin controls, advanced security and compliance, and dedicated support. -For details on Warp's legacy plans (Pro, Turbo, Lightspeed), see [Overages (Legacy)](/support-and-community/plans-and-billing/overages-legacy/). For the most up-to-date feature and usage details — including current per-plan seat limits and monthly credit allowances — visit [warp.dev/pricing](https://www.warp.dev/pricing). +For the most up-to-date feature and usage details — including current per-plan seat limits and monthly credit allowances — visit [warp.dev/pricing](https://www.warp.dev/pricing). ### How can I subscribe to a Warp Enterprise plan? @@ -94,10 +88,6 @@ You can use your Warp account on multiple personal computers. Warp is designed t ### What happens when I downgrade during a billing cycle? -:::caution -This describes downgrades between current paid plans (Build, Max, Business). Users transitioning from a legacy plan (Pro, Turbo, Lightspeed, old Business) to a current plan saw an immediate, prorated change with a credit reset at renewal; see [Overages (Legacy)](/support-and-community/plans-and-billing/overages-legacy/) for details on the legacy plans. -::: - The subscription will downgrade to the lower plan limits at the end of the billing cycle. If you’re switching between paid plans, any AI usage you've already accumulated will carry over.\ \ You can downgrade at any point throughout your subscription through the billing portal by going to **Settings** > **Billing and usage** > **Manage billing**. @@ -152,7 +142,7 @@ On the new multi-seat paid plans, credits attribute differently than they did on * **Plan-included monthly credits** — Each seat receives its own monthly credit allowance that resets every 30 days based on the team's renewal date. See [warp.dev/pricing](https://www.warp.dev/pricing) for the current per-seat allowance on your plan. * **Reload credits** — As of May 21, 2026, [Reload credits](/support-and-community/plans-and-billing/add-on-credits/) are scoped to the individual user who purchased or was allocated them, not pooled across the team. A single heavy user can no longer drain the whole team's purchased credits. -* **Grandfathered pooled credits** — Teams that purchased Reload credits (formerly Add-on Credits) before May 21, 2026 keep their existing pooled balance until it's exhausted. Pooled credits are spent down first across the team; all new Reload credit purchases after May 21, 2026 are user-scoped. +* **Grandfathered pooled credits** — Teams that purchased Reload credits before May 21, 2026 keep their existing pooled balance until it's exhausted. Pooled credits are spent down first across the team; all new Reload credit purchases after May 21, 2026 are user-scoped. * **Team-wide spend cap** — Admins set a single team-wide monthly spend cap that governs auto-reload across the team. See [How does auto-reload work for teams?](#how-does-auto-reload-work-for-teams) below. Enterprise plans support team-scoped credit pools and per-user spend limits separately — see [enterprise billing](/enterprise/support-and-resources/billing/). @@ -173,7 +163,7 @@ Local agent runs on Free, Build, or Max — and local runs on Business or Enterp If you regularly run through your plan's monthly credit allowance, you have a few options: * **Upgrade to Max** — Designed for developers with heavier AI usage. Max includes a higher monthly credit allowance than Build, plus a better effective rate for credits than buying [Reload credits](/support-and-community/plans-and-billing/add-on-credits/) on Build. See [warp.dev/pricing](https://www.warp.dev/pricing) for current allowances. -* **Purchase Reload credits** — Top up your account on demand at $10 / 400 credits, $20 / 1,000 credits, $50 / 3,000 credits, or $100 / 6,500 credits. Larger denominations have a better effective rate. Reload credits roll over month-to-month and remain valid for 12 months. +* **Purchase Reload credits** — Top up your account on demand. Larger denominations have a better effective rate. Reload credits roll over month-to-month and remain valid for 12 months. See [Reload credits](/support-and-community/plans-and-billing/add-on-credits/) for current denominations. * **Enable auto-reload** — Pick a denomination and a monthly spend cap, and Warp will automatically purchase Reload credits when your balance drops below 100 credits, up to your cap. * **Bring your own API key (BYOK)** — Point Warp at your own OpenAI, Anthropic, or Google API key. Requests routed through BYOK don't consume Warp credits — you're billed directly by the model provider. See [Bring Your Own API Key](/support-and-community/plans-and-billing/bring-your-own-api-key/). On Business and Enterprise, platform credits may apply for local agent runs — see [platform credits](/support-and-community/plans-and-billing/platform-credits/). * **Use a custom inference endpoint** — Route requests through any OpenAI-compatible endpoint (OpenRouter, LiteLLM, z.ai, an internal gateway, etc.) without spending Warp credits. See [Custom Inference Endpoint](/support-and-community/plans-and-billing/custom-inference-endpoint/). On Business and Enterprise, platform credits may apply for local agent runs — see [platform credits](/support-and-community/plans-and-billing/platform-credits/). @@ -184,11 +174,11 @@ For organization-scale needs (cloud-provider managed inference, granular admin c ### How does auto-reload work for teams? -Auto-reload prevents team members from getting blocked by credit exhaustion. It works the same way for single-user and multi-seat paid plans, with one extra knob for teams. +Auto-reload prevents team members from getting blocked by credit exhaustion. It works the same way for individual and multi-seat paid plans, with one extra knob for teams. 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. +* The admin chooses a Reload credit **denomination**. 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. * All auto-reload purchases count against a single **team-wide monthly spend cap** that the admin sets. Once the team hits the cap in a given month, auto-reload pauses until the next billing cycle or until the admin raises the cap. @@ -232,14 +222,6 @@ Warp Drive data is securely stored on Google Cloud Platform servers located in t For more details, please [visit the Security Overview](https://www.warp.dev/legal/security) or contact [security@warp.dev](mailto:security@warp.dev). -### What happened to the Lite model? - -Over time, the Lite model — originally designed as a fallback when premium models ran out — began to deliver inconsistent results, especially for users running complex, multi-step prompts. - -For credit-efficient usage, we encourage you to try our new **Auto (cost-efficiency) model**, which automatically selects the optimal model based on task complexity to help extend your credits. To continue AI usage beyond your included credits, you can purchase [Reload credits](/support-and-community/plans-and-billing/add-on-credits/), [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/). BYOK and custom inference endpoints don't consume Warp credits, since requests go directly to your provider. - -If you have any questions or feedback, please connect with us in our [community Slack](/support-and-community/#sending-warp-feedback). - ### Can I bring my own API key? Yes. On Free, Build, Max, Business, and Enterprise plans, you can configure your own OpenAI, Anthropic, or Google API key in **Settings** > **AI** > **Manage models**. Requests routed through your own key don't consume Warp credits — you're billed directly by the model provider. @@ -324,7 +306,7 @@ Teams that already exceed the new seat limit on their current plan remain in goo #### How are Reload credits being attributed differently? -Before May 21, 2026, Reload credits (previously called Add-on Credits) on multi-seat teams were **pooled** — every team member drew from a single shared balance. As of May 21, 2026, **Reload credits are user-scoped**: each user has their own balance, and a single heavy user can no longer drain the whole team's purchased credits. +Before May 21, 2026, Reload credits on multi-seat teams were **pooled** — every team member drew from a single shared balance. As of May 21, 2026, **Reload credits are user-scoped**: each user has their own balance, and a single heavy user can no longer drain the whole team's purchased credits. **Grandfathering for pre-May 2026 pooled credits**: Existing pooled Reload credit balances are honored. They drain first across the team before any new user-scoped Reload credits are consumed. No new credits will be added to the pooled balance — once it's exhausted, all future Reload credit purchases are user-scoped. @@ -338,9 +320,9 @@ See [Bring Your Own API Key](/support-and-community/plans-and-billing/bring-your #### What is the new Custom Inference Endpoint feature? -**Custom Inference Endpoint (CIE)** is a new way to route Warp's AI traffic through any OpenAI-compatible inference endpoint — including OpenRouter, LiteLLM, z.ai, and internal gateways your team already runs. CIE is available on Free, Build, Max, Business, and Enterprise. +**Custom inference endpoints** are a new way to route Warp's AI traffic through any OpenAI-compatible inference endpoint — including OpenRouter, LiteLLM, z.ai, and internal gateways your team already runs. Custom inference endpoint support is available on Free, Build, Max, Business, and Enterprise. -CIE differs from BYOK and BYOLLM: +Custom inference endpoints differ from BYOK and BYOLLM: * **BYOK** sends requests directly to OpenAI, Anthropic, or Google using your own provider API key. * **Custom inference endpoint** sends requests to any OpenAI-compatible URL you control (or that your team runs). @@ -367,9 +349,3 @@ On **July 1, 2026**, Warp begins charging self-serve paid plans for: * Every cloud agent run on Build, Max, or Business. * Local agent runs on Business that use BYOK or a custom inference endpoint. - -This date lines up with the rest of the May 2026 self-serve pricing transition (seat limits, user-scoped Reload credits, and related grandfathering changes). - -**Free plan** cloud agent runs continue to draw from your plan-included credits as they always have — the preview period doesn't apply to Free, and there's no change to how Free is billed for cloud agent runs. - -**Enterprise plans** are billed for platform credits per your contract from May 21 and aren't affected by this preview period. diff --git a/src/sidebar.ts b/src/sidebar.ts index f64c9e80..7bdb5ce8 100644 --- a/src/sidebar.ts +++ b/src/sidebar.ts @@ -540,7 +540,6 @@ export const sidebarTopics: StarlightSidebarTopicsUserConfig = [ 'support-and-community/plans-and-billing/add-on-credits', { slug: 'support-and-community/plans-and-billing/platform-credits', label: 'Platform credits' }, 'support-and-community/plans-and-billing/bring-your-own-api-key', - 'support-and-community/plans-and-billing/overages-legacy', 'support-and-community/plans-and-billing/pricing-faqs', ], }, diff --git a/vercel.json b/vercel.json index f2b32ed3..78b980fb 100644 --- a/vercel.json +++ b/vercel.json @@ -2865,7 +2865,7 @@ }, { "source": "/support-and-community/plans-pricing-and-billing/overages-legacy", - "destination": "/support-and-community/plans-and-billing/overages-legacy/", + "destination": "/support-and-community/plans-and-billing/add-on-credits/", "statusCode": 308 }, { @@ -3040,7 +3040,7 @@ }, { "source": "/support-and-community/support-and-billing/plans-and-pricing/usage-overages", - "destination": "/support-and-community/plans-and-billing/overages-legacy/", + "destination": "/support-and-community/plans-and-billing/add-on-credits/", "statusCode": 308 }, { @@ -3140,7 +3140,7 @@ }, { "source": "/support-and-community/support-and-community/plans-pricing-and-billing/overages-legacy", - "destination": "/support-and-community/plans-and-billing/overages-legacy/", + "destination": "/support-and-community/plans-and-billing/add-on-credits/", "statusCode": 308 }, { @@ -6805,7 +6805,7 @@ }, { "source": "/support-and-community/plans-pricing-and-billing/overages-legacy/", - "destination": "/support-and-community/plans-and-billing/overages-legacy/", + "destination": "/support-and-community/plans-and-billing/add-on-credits/", "statusCode": 308 }, { @@ -6910,7 +6910,7 @@ }, { "source": "/support-and-community/support-and-billing/plans-and-pricing/usage-overages/", - "destination": "/support-and-community/plans-and-billing/overages-legacy/", + "destination": "/support-and-community/plans-and-billing/add-on-credits/", "statusCode": 308 }, { @@ -6980,7 +6980,7 @@ }, { "source": "/support-and-community/support-and-community/plans-pricing-and-billing/overages-legacy/", - "destination": "/support-and-community/plans-and-billing/overages-legacy/", + "destination": "/support-and-community/plans-and-billing/add-on-credits/", "statusCode": 308 }, { From d5202240d3532fa698cba5e90a3c61a650a4ab72 Mon Sep 17 00:00:00 2001 From: Hong Yi Chen Date: Wed, 20 May 2026 18:13:16 -0700 Subject: [PATCH 08/15] Add SOC 2, ZDR, BYOLLM, and multi-harness orchestration FAQs 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 --- .../plans-and-billing/pricing-faqs.mdx | 44 ++++++++++++++++++- 1 file changed, 42 insertions(+), 2 deletions(-) diff --git a/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx b/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx index 0d373c10..9b1a9519 100644 --- a/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx +++ b/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx @@ -222,6 +222,30 @@ Warp Drive data is securely stored on Google Cloud Platform servers located in t For more details, please [visit the Security Overview](https://www.warp.dev/legal/security) or contact [security@warp.dev](mailto:security@warp.dev). +### Does Warp have a SOC 2 Type 2 attestation? + +Yes. Warp has obtained a SOC 2 Type 2 attestation from an accredited third party. See the [Trust Center](/enterprise/security-and-compliance/trust-center/) to request the report. + +### Does Warp have Zero Data Retention policies with LLM providers? + +Warp integrates with multiple LLM providers — including Anthropic, OpenAI, Google, and Fireworks AI — to power its AI features. Warp has executed Zero Data Retention (ZDR) agreements with these providers. Across all plans, these agreements mean: + +* LLM providers commit not to train their models on any customer-generated data processed through Warp's services. +* LLM providers commit to delete inputs and outputs after generating the relevant output, within a fixed time period. + +Warp enforces these commitments through both technical measures and contractual safeguards with the LLM providers. + +### How can I enable Zero Data Retention in Warp? + +Zero Data Retention (ZDR) can be enabled in two ways: + +* **Individual level** — Any user can enable full ZDR for their own account by disabling **Help Improve Warp** in **Settings** > **Privacy**. +* **Organization-wide** — On Business and Enterprise plans, admins can enforce ZDR for all members from the [Admin Panel](/enterprise/team-management/admin-panel/), so team-wide compliance doesn't rely on individual settings. + +To discuss organization-wide ZDR for your team, [contact our sales team](https://www.warp.dev/contact-sales). + +Regardless of plan, Warp never allows OpenAI, Anthropic, Google, or other model providers to store, retain, or train their models on your data — see [Does Warp have Zero Data Retention policies with LLM providers?](#does-warp-have-zero-data-retention-policies-with-llm-providers) for details. + ### Can I bring my own API key? Yes. On Free, Build, Max, Business, and Enterprise plans, you can configure your own OpenAI, Anthropic, or Google API key in **Settings** > **AI** > **Manage models**. Requests routed through your own key don't consume Warp credits — you're billed directly by the model provider. @@ -242,6 +266,22 @@ BYOK and custom inference endpoint support are available for individual users an On Business and Enterprise, local agent runs that use a custom inference endpoint still consume platform credits for Warp's platform infrastructure. See [platform credits](/support-and-community/plans-and-billing/platform-credits/). +### Does Warp support other model routers or "Bring Your Own LLM"? + +On the Enterprise plan, Warp's [Bring Your Own LLM (BYOLLM)](/enterprise/enterprise-features/bring-your-own-llm/) lets you route inference through major cloud-provider Model-as-a-Service offerings — including AWS Bedrock, Google Vertex AI, and Azure AI Foundry. Warp still manages model support, routing, and orchestration, but inference runs in your cloud environment so you can maintain data locality, security controls, and existing cloud spend commitments. + +Custom or in-house model routers outside this list aren't supported by default today. If you have specific requirements, [contact our sales team](https://www.warp.dev/contact-sales). + +For lighter-weight routing through any OpenAI-compatible endpoint (OpenRouter, LiteLLM, z.ai, internal gateways), see [Does Warp support custom inference endpoints?](#does-warp-support-custom-inference-endpoints) above. + +### What features are available during multi-harness orchestration beta? + +Multi-harness orchestration is currently in beta and available to all users. You can use the [Warp Agent](/agent-platform/cloud-agents/harnesses/warp-agent/) alongside [Claude Code](/agent-platform/cloud-agents/harnesses/claude-code/) and [Codex](/agent-platform/cloud-agents/harnesses/codex/) in Oz cloud environments, and mix and match harnesses across workflows. + +[Agent Memory](/agent-platform/agent-memory/) is currently in Research Preview. It lets preferences, project knowledge, and learnings from past sessions carry across harnesses and future agent runs. [Contact our sales team](https://www.warp.dev/contact-sales) to request access. + +As these features move out of beta or Research Preview, availability, limits, and pricing may change. + ### What payment options are available for Warp's self-service plans? Warp uses Stripe as our payments processor and currently accepts the following payment methods: credit card, debit card, Link, Apple Pay, Google Pay. @@ -334,8 +374,8 @@ For setup and details, see [Custom Inference Endpoint](/support-and-community/pl Two distinct things are sometimes both called "ZDR" — May 21, 2026 makes the distinction clearer: -* **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." +* **Model provider ZDR** applies to **all plans, including Free**. See [Does Warp have Zero Data Retention policies with LLM providers?](#does-warp-have-zero-data-retention-policies-with-llm-providers) for the full provider list and what those agreements cover. +* **Admin-configurable data controls** are 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." See [How can I enable Zero Data Retention in Warp?](#how-can-i-enable-zero-data-retention-in-warp) for setup. If you previously relied on the "automatically enforced team-wide ZDR" language on Business, your data controls are unchanged — Warp still does not retain your team's data for training, and admins can still configure retention. The terminology change disambiguates Warp's controls from the provider-level ZDR that applies to every plan. From 8e7b9253048bb724b987966e1ee861343038612f Mon Sep 17 00:00:00 2001 From: Hong Yi Chen Date: Wed, 20 May 2026 18:50:18 -0700 Subject: [PATCH 09/15] Cleanup pass: BYOLLM scope, naming, AI token FAQ - 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 --- .../plans-and-billing/pricing-faqs.mdx | 12 +++++------- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git a/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx b/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx index 9b1a9519..a2e0dfdf 100644 --- a/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx +++ b/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx @@ -36,7 +36,7 @@ For the most up-to-date feature and usage details — including current per-plan Warp offers two options for larger teams and organizations: * **Business plan**: Self-serve multi-seat plan available for immediate upgrade. Includes admin-configurable data controls and admin-controlled SAML-based SSO. See [warp.dev/pricing](https://www.warp.dev/pricing) for the current seat limit. -* **Enterprise plan**: Custom pricing, credit allowances, and terms — built for larger engineering organizations or teams with advanced security, compliance, or support needs. Enterprise also includes [Bring Your Own LLM (BYOLLM)](/enterprise/enterprise-features/bring-your-own-llm/) managed inference, where Warp routes traffic through your AWS Bedrock, Google Vertex, Azure Foundry, or internal LLM gateway with routing, orchestration, governance, and observability provided by Warp. +* **Enterprise plan**: Custom pricing, credit allowances, and terms — built for larger engineering organizations or teams with advanced security, compliance, or support needs. Enterprise also includes [Bring Your Own LLM (BYOLLM)](/enterprise/enterprise-features/bring-your-own-llm/) managed inference, where Warp routes traffic through AWS Bedrock today — with Azure Foundry and Google Vertex coming soon — with routing, orchestration, governance, and observability provided by Warp. :::tip If you’d like to explore Enterprise, [contact our sales team](https://www.warp.dev/contact-sales) and someone from Warp will follow up. @@ -124,9 +124,7 @@ Tokens are chunks of text, such as words, parts of code, or characters, that lar Warp now abstracts away token usage, so you don't need to manage or track it directly. You only need to monitor your **credit usage**, which is what’s measured against your plan limits. ::: -If you're curious, you can read the [OpenAI article on tokens](https://help.openai.com/en/articles/4936856-understanding-tokens), or refer to the pricing page for plan-level credit allocations. If you reach your monthly credit limits on a paid plan, premium models will be temporarily disabled until your quota resets at the start of your next billing cycle. - -If you’d like to continue using premium models beyond your included quota, purchase [Reload credits](/support-and-community/plans-and-billing/add-on-credits/) in **Settings** > **Billing and usage**. +If you're curious, you can read the [OpenAI article on tokens](https://help.openai.com/en/articles/4936856-understanding-tokens), or refer to the pricing page for plan-level credit allocations. If you reach your monthly credit limits on the Free plan, premium models pause until your quota resets at the start of your next billing cycle. On paid plans, you can continue using premium models via [Reload credits](/support-and-community/plans-and-billing/add-on-credits/) and auto-reload — see [What if I need more AI usage than my plan includes?](#what-if-i-need-more-ai-usage-than-my-plan-includes) for the full list of options. ### How often do my credits reset? @@ -154,7 +152,7 @@ Warp meters credits across three buckets: **AI credits** (the model call), **com Platform credits apply in two situations: * **Every cloud agent run, on every plan.** Warp's platform infrastructure coordinates every cloud run regardless of which agent or inference source it uses. -* **Local agent runs on Business and Enterprise that use customer-supplied inference** — BYOK, BYOLLM via Amazon Bedrock or Google Vertex, or a custom inference endpoint. Warp isn't paying for the model call, but Warp's platform infrastructure is still running the agent. +* **Local agent runs on Business and Enterprise that use customer-supplied inference** — BYOK, BYOLLM via AWS Bedrock (with Azure Foundry and Google Vertex coming soon), or a custom inference endpoint. Warp isn't paying for the model call, but Warp's platform infrastructure is still running the agent. Local agent runs on Free, Build, or Max — and local runs on Business or Enterprise that use Warp-managed inference — do not consume platform credits. See [platform credits](/support-and-community/plans-and-billing/platform-credits/) for the full breakdown. @@ -268,7 +266,7 @@ On Business and Enterprise, local agent runs that use a custom inference endpoin ### Does Warp support other model routers or "Bring Your Own LLM"? -On the Enterprise plan, Warp's [Bring Your Own LLM (BYOLLM)](/enterprise/enterprise-features/bring-your-own-llm/) lets you route inference through major cloud-provider Model-as-a-Service offerings — including AWS Bedrock, Google Vertex AI, and Azure AI Foundry. Warp still manages model support, routing, and orchestration, but inference runs in your cloud environment so you can maintain data locality, security controls, and existing cloud spend commitments. +On the Enterprise plan, Warp's [Bring Your Own LLM (BYOLLM)](/enterprise/enterprise-features/bring-your-own-llm/) lets you route inference through major cloud-provider Model-as-a-Service offerings. BYOLLM currently supports AWS Bedrock, with Azure Foundry and Google Vertex coming soon. Warp still manages model support, routing, and orchestration, but inference runs in your cloud environment so you can maintain data locality, security controls, and existing cloud spend commitments. Custom or in-house model routers outside this list aren't supported by default today. If you have specific requirements, [contact our sales team](https://www.warp.dev/contact-sales). @@ -366,7 +364,7 @@ Custom inference endpoints differ from BYOK and BYOLLM: * **BYOK** sends requests directly to OpenAI, Anthropic, or Google using your own provider API key. * **Custom inference endpoint** sends requests to any OpenAI-compatible URL you control (or that your team runs). -* **BYOLLM** is an Enterprise-only managed inference feature where Warp routes traffic through your AWS Bedrock, Google Vertex, Azure Foundry, or internal LLM gateway with full routing, orchestration, governance, and observability provided by Warp. +* **BYOLLM** is an Enterprise-only managed inference feature where Warp routes traffic through your cloud provider — AWS Bedrock today, with Azure Foundry and Google Vertex coming soon — with full routing, orchestration, governance, and observability provided by Warp. For setup and details, see [Custom Inference Endpoint](/support-and-community/plans-and-billing/custom-inference-endpoint/). From 21dcb5ec47ba2685f7dd102df58e29e6aad13237 Mon Sep 17 00:00:00 2001 From: Hong Yi Chen Date: Wed, 20 May 2026 21:10:13 -0700 Subject: [PATCH 10/15] PR #116 review: normalize 'require' -> 'need' for plan-availability copy 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 --- .../support-and-community/plans-and-billing/pricing-faqs.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx b/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx index a2e0dfdf..6d7e9b00 100644 --- a/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx +++ b/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx @@ -250,7 +250,7 @@ Yes. On Free, Build, Max, Business, and Enterprise plans, you can configure your See [Bring Your Own API Key](/support-and-community/plans-and-billing/bring-your-own-api-key/) for setup steps, the list of supported providers and models, and the differences between BYOK, custom inference endpoints, and BYOLLM. -BYOK and custom inference endpoint support are available for individual users and organizations with 10 or fewer employees, subject to Warp's Terms of Service. Companies or organizations with more than 10 employees require a Warp Business or Enterprise plan to use these features. +BYOK and custom inference endpoint support are available for individual users and organizations with 10 or fewer employees, subject to Warp's Terms of Service. Companies or organizations with more than 10 employees need a Warp Business or Enterprise plan to use these features. On Business and Enterprise, local agent runs that use BYOK still consume platform credits for Warp's platform infrastructure. See [platform credits](/support-and-community/plans-and-billing/platform-credits/). @@ -260,7 +260,7 @@ Yes. In addition to BYOK, Warp can route requests to any OpenAI-compatible infer Custom inference endpoints are available on Free, Build, Max, Business, and Enterprise. See [Custom Inference Endpoint](/support-and-community/plans-and-billing/custom-inference-endpoint/) for configuration steps, billing behavior, and how custom inference endpoints differ from BYOK and from Enterprise's [Bring Your Own LLM (BYOLLM)](/enterprise/enterprise-features/bring-your-own-llm/) managed inference. -BYOK and custom inference endpoint support are available for individual users and organizations with 10 or fewer employees, subject to Warp's Terms of Service. Companies or organizations with more than 10 employees require a Warp Business or Enterprise plan to use these features. +BYOK and custom inference endpoint support are available for individual users and organizations with 10 or fewer employees, subject to Warp's Terms of Service. Companies or organizations with more than 10 employees need a Warp Business or Enterprise plan to use these features. On Business and Enterprise, local agent runs that use a custom inference endpoint still consume platform credits for Warp's platform infrastructure. See [platform credits](/support-and-community/plans-and-billing/platform-credits/). From f5f380af120c75339f04502078f3aceb37ec0d39 Mon Sep 17 00:00:00 2001 From: hongyi-chen Date: Thu, 21 May 2026 19:41:05 +0000 Subject: [PATCH 11/15] Align teams.mdx Reload credit consequences wording with PR #114 PR #116's "Reload credit consequences when leaving or removing members" section in both `enterprise/team-management/teams.mdx` and `knowledge-and-collaboration/teams.mdx` used "scoped to the individual user under your team" framing, which read as inconsistent with PR #114's authoritative `add-on-credits.mdx` model: - PR #114 establishes that Add-on Credits are *both* user-scoped (each user has their own balance) AND tied to the team they were purchased under (lose access on membership changes). - PR #114 also says "The admin pays a prorated rate for your seat on rejoin", which PR #116 was missing. - The team-deletion bullet now matches PR #114 verbatim ("Any remaining Reload credits tied to the team are no longer usable"). This commit rewrites the section in both files to: - Lead with "scoped to each individual user but tied to the team they were purchased under" to capture both halves of the model. - Mirror PR #114's bullets exactly, including the prorated-rate detail. - Keep the grandfathered pooled balance :::note unchanged. Validated with npm run build (334 pages, no broken links). Co-Authored-By: Oz --- src/content/docs/enterprise/team-management/teams.mdx | 8 ++++---- src/content/docs/knowledge-and-collaboration/teams.mdx | 10 +++++----- 2 files changed, 9 insertions(+), 9 deletions(-) diff --git a/src/content/docs/enterprise/team-management/teams.mdx b/src/content/docs/enterprise/team-management/teams.mdx index 274da7cc..921c8bc2 100644 --- a/src/content/docs/enterprise/team-management/teams.mdx +++ b/src/content/docs/enterprise/team-management/teams.mdx @@ -66,11 +66,11 @@ If you're a Team Owner and choose to [delete your Warp account](/support-and-com ### Reload credit consequences when leaving or removing members -On Build, Max, and Business plans, [Reload credits](/support-and-community/plans-and-billing/add-on-credits/) (also known as Add-on Credits) are scoped to the individual user under your team. Membership changes affect access to those credits: +On Build, Max, and Business plans, [Reload credits](/support-and-community/plans-and-billing/add-on-credits/) (also known as Add-on Credits) are scoped to each individual user but **tied to the team** they were purchased under. Membership changes affect access: -* **Leaving the team** - You lose access to any remaining Reload credits tied to it. If you rejoin the same team later, you regain access to any unused, non-expired credits. -* **An admin removes a member** - That member loses access to any remaining Reload credits tied to the team. If they rejoin later, they regain access to any unused, non-expired credits. -* **An admin deletes the team** - All members lose access to any remaining Reload credits tied to the team. +* **A user leaves a team** - You lose access to any Reload credits tied to that team. If you rejoin the same team later, you regain access to any unused, non-expired credits. The admin pays a prorated rate for your seat on rejoin. +* **An admin removes a member** - That member loses access to any Reload credits tied to the team. If they rejoin later, they regain access to any unused, non-expired credits. +* **An admin deletes the team** - Any remaining Reload credits tied to the team are no longer usable. Reload credits require an active subscription. Downgrading to the Free plan forfeits access to Reload credits tied to your team. diff --git a/src/content/docs/knowledge-and-collaboration/teams.mdx b/src/content/docs/knowledge-and-collaboration/teams.mdx index 9096d22a..883b4e41 100644 --- a/src/content/docs/knowledge-and-collaboration/teams.mdx +++ b/src/content/docs/knowledge-and-collaboration/teams.mdx @@ -67,13 +67,13 @@ If you have received an invite link, you can use that link to sign up or log in If you’re a member of a team, you can visit **Settings** > **Teams** to leave a team at any time. Team admins (who created teams) may delete a team only after removing all team members. -On Build, Max, and Business plans, [Reload credits](/support-and-community/plans-and-billing/add-on-credits/) (also known as Add-on Credits) are scoped to your individual user under your team. Membership changes affect access to those credits: +On Build, Max, and Business plans, [Reload credits](/support-and-community/plans-and-billing/add-on-credits/) (also known as Add-on Credits) are scoped to each individual user but **tied to the team** they were purchased under. Membership changes affect access: -* **Leaving the team** - You lose access to any remaining Reload credits attributed to you. If you rejoin the same team later, you regain access to any unused, non-expired credits. -* **An admin removes a member** - That member loses access to any remaining Reload credits attributed to them under this team. If they rejoin later, they regain access to any unused, non-expired credits. -* **An admin deletes the team** - All members lose access to any remaining Reload credits attributed to them under that team. +* **A user leaves a team** - You lose access to any Reload credits tied to that team. If you rejoin the same team later, you regain access to any unused, non-expired credits. The admin pays a prorated rate for your seat on rejoin. +* **An admin removes a member** - That member loses access to any Reload credits tied to the team. If they rejoin later, they regain access to any unused, non-expired credits. +* **An admin deletes the team** - Any remaining Reload credits tied to the team are no longer usable. -Reload credits require an active subscription. Downgrading to the Free plan also forfeits access to Reload credits. +Reload credits require an active subscription. Downgrading to the Free plan forfeits access to Reload credits tied to your team. :::note Grandfathered pooled Reload credits (purchased before May 21, 2026) remain attached to the team itself rather than any individual user, and are unaffected by individual membership changes. They continue to drain first across the team until exhausted; only post-May-21 purchases are user-scoped. From bb96d6df3c2579a42b3910b24e1fe670df402466 Mon Sep 17 00:00:00 2001 From: hongyi-chen Date: Thu, 21 May 2026 19:46:07 +0000 Subject: [PATCH 12/15] Align auto-reload FAQ with PR #114's add-on-credits.mdx constraints PR #114's `add-on-credits.mdx` documents two auto-reload constraints that PR #116's "How does auto-reload work for teams?" FAQ was missing: - **Auto-reload on**: "While auto-reload is on, individual users cannot purchase Add-on credits manually." - **Auto-reload off**: "When auto-reload is off, eligible team members can purchase Add-on credits for themselves, as long as the team stays below the team-wide spend cap." This commit folds both into the FAQ so the pricing-faqs.mdx and add-on-credits.mdx descriptions match. Validated with npm run build (334 pages, no broken links). Co-Authored-By: Oz --- .../support-and-community/plans-and-billing/pricing-faqs.mdx | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx b/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx index 9ccf0335..add574e3 100644 --- a/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx +++ b/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx @@ -179,10 +179,11 @@ When auto-reload is **on**: * The admin chooses a Reload credit **denomination**. Larger denominations have a better effective per-credit rate. * Whenever any individual user's balance (their plan credits plus their user-scoped Reload credits balance) drops below **100 credits**, Warp automatically purchases another bundle of the configured denomination on the team's behalf. * All auto-reload purchases count against a single **team-wide monthly spend cap** that the admin sets. Once the team hits the cap in a given month, auto-reload pauses until the next billing cycle or until the admin raises the cap. +* While auto-reload is on, **individual team members cannot purchase Reload credits manually** — the team-wide auto-reload configuration governs all purchases. Teams with a pre-May 21, 2026 grandfathered pooled Reload balance: that pooled balance drains first across the team before user-scoped Reload credits and is not counted toward any individual user's 100-credit auto-reload threshold. -When auto-reload is **off**, users keep working as long as they have plan credits, previously purchased Reload credits, or have routed Warp at their own API key or [custom inference endpoint](/agent-platform/inference/custom-inference-endpoint/). Once those run out, premium-model usage is blocked until credits are topped up or the next billing cycle begins. +When auto-reload is **off**, eligible team members can purchase Reload credits for themselves, as long as the team stays below the team-wide monthly spend cap. Users keep working as long as they have plan credits, previously purchased Reload credits, or have routed Warp at their own API key or [custom inference endpoint](/agent-platform/inference/custom-inference-endpoint/). Once those run out, premium-model usage is blocked until credits are topped up or the next billing cycle begins. Auto-reload can be enabled, paused, or reconfigured at any time in **Settings** > **Billing and usage**. From 2041f28460407adad5a5faba85bf831a0e892f40 Mon Sep 17 00:00:00 2001 From: hongyi-chen Date: Thu, 21 May 2026 20:05:48 +0000 Subject: [PATCH 13/15] Remove ephemeral grandfathered Reload credits note from canonical teams.mdx pages Per review feedback, the grandfathered pooled Reload credits :::note is launch-ephemeral messaging that doesn't belong on canonical docs pages. It still lives on the pricing FAQs page (under "How do credits work for multi-seat teams?" and the auto-reload-for-teams FAQ), which is the appropriate home for time-bound launch context. Removes the :::note block from: - src/content/docs/enterprise/team-management/teams.mdx - src/content/docs/knowledge-and-collaboration/teams.mdx Validated with npm run build (334 pages, no broken links). Co-Authored-By: Oz --- src/content/docs/enterprise/team-management/teams.mdx | 4 ---- src/content/docs/knowledge-and-collaboration/teams.mdx | 4 ---- 2 files changed, 8 deletions(-) diff --git a/src/content/docs/enterprise/team-management/teams.mdx b/src/content/docs/enterprise/team-management/teams.mdx index 921c8bc2..e714c3fb 100644 --- a/src/content/docs/enterprise/team-management/teams.mdx +++ b/src/content/docs/enterprise/team-management/teams.mdx @@ -74,10 +74,6 @@ On Build, Max, and Business plans, [Reload credits](/support-and-community/plans Reload credits require an active subscription. Downgrading to the Free plan forfeits access to Reload credits tied to your team. -:::note -Grandfathered pooled Reload credits (purchased before May 21, 2026) remain attached to the team itself rather than any individual user, and are unaffected by individual membership changes. They continue to drain first across the team until exhausted; only post-May-21 purchases are user-scoped. -::: - ## Team discoverability Team admins can make their team discoverable to colleagues who share the same email domain. When enabled, new users with a matching domain can find and join the team without needing a direct invite link. diff --git a/src/content/docs/knowledge-and-collaboration/teams.mdx b/src/content/docs/knowledge-and-collaboration/teams.mdx index 883b4e41..9a2c6b39 100644 --- a/src/content/docs/knowledge-and-collaboration/teams.mdx +++ b/src/content/docs/knowledge-and-collaboration/teams.mdx @@ -75,10 +75,6 @@ On Build, Max, and Business plans, [Reload credits](/support-and-community/plans Reload credits require an active subscription. Downgrading to the Free plan forfeits access to Reload credits tied to your team. -:::note -Grandfathered pooled Reload credits (purchased before May 21, 2026) remain attached to the team itself rather than any individual user, and are unaffected by individual membership changes. They continue to drain first across the team until exhausted; only post-May-21 purchases are user-scoped. -::: - ## Team discoverability Team admins can make their teams discoverable to colleagues from the same email domain. This feature is available under **Settings** > **Teams** > **Make team discoverable**. From 48bf6884135630df64ff5176e1f9e98678d2aea8 Mon Sep 17 00:00:00 2001 From: Hong Yi Chen Date: Thu, 21 May 2026 14:07:04 -0700 Subject: [PATCH 14/15] Update src/content/docs/enterprise/team-management/teams.mdx Co-authored-by: Rachael Rose Renk <91027132+rachaelrenk@users.noreply.github.com> --- src/content/docs/enterprise/team-management/teams.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/enterprise/team-management/teams.mdx b/src/content/docs/enterprise/team-management/teams.mdx index e714c3fb..ee7aa977 100644 --- a/src/content/docs/enterprise/team-management/teams.mdx +++ b/src/content/docs/enterprise/team-management/teams.mdx @@ -69,7 +69,7 @@ If you're a Team Owner and choose to [delete your Warp account](/support-and-com On Build, Max, and Business plans, [Reload credits](/support-and-community/plans-and-billing/add-on-credits/) (also known as Add-on Credits) are scoped to each individual user but **tied to the team** they were purchased under. Membership changes affect access: * **A user leaves a team** - You lose access to any Reload credits tied to that team. If you rejoin the same team later, you regain access to any unused, non-expired credits. The admin pays a prorated rate for your seat on rejoin. -* **An admin removes a member** - That member loses access to any Reload credits tied to the team. If they rejoin later, they regain access to any unused, non-expired credits. +* **A user leaves a team** - They lose access to any Reload credits tied to that team. If they rejoin the same team later, they regain access to any unused, non-expired credits. The admin pays a prorated rate for the seat when the user rejoins. * **An admin deletes the team** - Any remaining Reload credits tied to the team are no longer usable. Reload credits require an active subscription. Downgrading to the Free plan forfeits access to Reload credits tied to your team. From 79cb51790ef15a6853fb66b3b5cd8c0b29a0ff96 Mon Sep 17 00:00:00 2001 From: Hong Yi Chen Date: Thu, 21 May 2026 14:07:20 -0700 Subject: [PATCH 15/15] Update src/content/docs/knowledge-and-collaboration/teams.mdx Co-authored-by: Rachael Rose Renk <91027132+rachaelrenk@users.noreply.github.com> --- src/content/docs/knowledge-and-collaboration/teams.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/knowledge-and-collaboration/teams.mdx b/src/content/docs/knowledge-and-collaboration/teams.mdx index 9a2c6b39..c1ee26f3 100644 --- a/src/content/docs/knowledge-and-collaboration/teams.mdx +++ b/src/content/docs/knowledge-and-collaboration/teams.mdx @@ -70,7 +70,7 @@ If you’re a member of a team, you can visit **Settings** > **Teams** to leave On Build, Max, and Business plans, [Reload credits](/support-and-community/plans-and-billing/add-on-credits/) (also known as Add-on Credits) are scoped to each individual user but **tied to the team** they were purchased under. Membership changes affect access: * **A user leaves a team** - You lose access to any Reload credits tied to that team. If you rejoin the same team later, you regain access to any unused, non-expired credits. The admin pays a prorated rate for your seat on rejoin. -* **An admin removes a member** - That member loses access to any Reload credits tied to the team. If they rejoin later, they regain access to any unused, non-expired credits. +* **A user leaves a team** - They lose access to any Reload credits tied to that team. If they rejoin the same team later, they regain access to any unused, non-expired credits. The admin pays a prorated rate for the seat when the user rejoins. * **An admin deletes the team** - Any remaining Reload credits tied to the team are no longer usable. Reload credits require an active subscription. Downgrading to the Free plan forfeits access to Reload credits tied to your team.