> For the complete documentation index, see [llms.txt](https://docs.warp.dev/llms.txt).
> Markdown versions of each page are available by appending .md to any URL.

# Plans, pricing, and refunds

Find Warp Terminal, agent, and Warp Factories plan guidance, understand usage funding, and review subscription and usage refund policies.

Warp Terminal and agent plans are separate from Warp Factories plans. For the latest plans and offerings, see [Warp pricing](https://www.warp.dev/pricing).

## Warp Terminal and agent plans

Choose a Warp Terminal and local agent plan for interactive development:

| Plan for Warp Terminal and local agents | Choose it when |
| --- | --- |
| Free | You want terminal features without a subscription. Add usage or bring your own inference for agent work. |
| Build | You want a monthly included usage allowance, with additional purchases when needed. |
| Max | You need a larger included allowance for heavier agent usage. |
| Business | Your team needs per-seat billing, admin-configurable data controls, and SAML SSO. |
| Enterprise | Your organization needs custom allowances, managed cloud-provider inference, or contract-specific administration and support. |

See [Warp pricing](https://www.warp.dev/pricing) for current prices, allowances, and seat limits.

### Existing Warp plans

Existing Build, Max, and Business subscriptions for Warp Terminal and local agents retain their plan-specific per-seat allowances. Check **Settings** > **Billing and usage** in the Warp app for your account’s allowance. Existing Enterprise contracts retain their agreed pools and terms.

## Warp Factories plans

Choose a factory plan for your team’s automated workflows:

-   **Start** - For small teams getting started with Warp-hosted factory setup. Start is usage-based, without a monthly shared allowance.
-   **Scale** - For teams that need a monthly team subscription with shared included usage, agents such as [Claude Code or Codex](https://docs.warp.dev/factories/harnesses/), or a factory-definition repository they own.
-   **Enterprise** - For organizations that need custom usage terms, advanced administration, or [customer-hosted infrastructure](https://docs.warp.dev/factories/self-hosting/). Your contract sets funding and billing terms.

Hosting your factory definition in your own repository does not move execution or run data to your infrastructure. Enterprise teams configure self-hosted workers and [agent data storage](https://docs.warp.dev/factories/self-hosting/data-storage/) separately.

Start with the [Warp Factories quickstart](https://docs.warp.dev/factories/quickstart/). For Scale setup, see [SAML SSO](https://docs.warp.dev/enterprise/security-and-compliance/sso/) and [team-managed keys and endpoints](https://docs.warp.dev/enterprise/enterprise-features/team-managed-keys-and-endpoints/). Third-party harnesses use separate [harness authentication](https://docs.warp.dev/factories/harnesses/authentication/).

### Funding factory runs

Factory runs use shared team or workspace usage, including runs started by automations. A member’s included personal allowance does not fund factory runs.

On the Scale plan for Warp Factories, the shared included allowance covers eligible Warp-provided inference, Warp-hosted compute, and platform usage. After it runs out, runs draw from eligible purchased team or workspace usage. If no usable balance or contracted pay-as-you-go funding remains, runs can be blocked with an [insufficient credits error](https://docs.warp.dev/factories/api-and-sdk/troubleshooting/errors/insufficient-credits/).

In the [Warp Factories web app](https://platform.warp.dev), open **Settings** > **Billing and usage** to check your shared balance. [Add usage](https://docs.warp.dev/support-and-community/plans-and-billing/add-on-credits/#warp-factories) only if that balance does not cover the work. Enterprise funding follows your contract.

Your provider bills customer-supplied inference separately. That does not remove Warp’s [platform charges](https://docs.warp.dev/support-and-community/plans-and-billing/platform-credits/) or charges for [Warp-hosted compute](https://docs.warp.dev/support-and-community/plans-and-billing/credits/#compute-usage).

### Upgrading to Scale

Follow [upgrading your factory plan](https://docs.warp.dev/factories/managing-plans-and-billing/#upgrading-your-factory-plan) in the Warp Factories web app. An admin completes checkout or confirms the subscription update. For an existing Enterprise contract, contact your account team instead.

## Your included allowance

### Warp Terminal and local agents

In the Warp app, open **Settings** > **Billing and usage** for your personal allowance and reset date. Existing seats can have a different allowance from new subscriptions, so use the amount shown for your account.

### Warp Factories

In the Warp Factories web app, open **Settings** > **Billing and usage** for shared balances and the reset date. A personal allowance shown there cannot fund factory runs.

### Resets and billing units

Included usage resets monthly, even when you pay for your subscription annually. Unused included usage does not roll over. Purchased usage is separate: it rolls over until its original 12-month expiration.

If **Billing and usage** shows your allowance and balance in dollars, those amounts are your usage balance. Enterprise contracts that use credits retain their contracted pools, rates, and terms; a dollar cost display does not change those terms. See [Enterprise billing](https://docs.warp.dev/enterprise/support-and-resources/billing/).

## Existing purchased balances

If Warp converts an existing self-serve purchased credit pack to dollar usage, it keeps its face value or equivalent inference value, whichever is higher.

A converted, partially used pack retains the remaining proportion of that value and its original expiration. Check the balance shown in Billing and usage rather than applying a single exchange rate to every credit pack.

## Warp’s refund policies

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.

Caution

To request a refund or credit for a product defect, we require your [Conversation ID](https://docs.warp.dev/support-and-community/troubleshooting-and-support/sending-us-feedback/#gathering-ai-conversation-id) and [logs](https://docs.warp.dev/support-and-community/troubleshooting-and-support/sending-us-feedback/#gathering-warp-logs). You must have **Help improve Warp** enabled, so we can identify the issue before issuing any refund or credit. Learn how to enable it in [Crash reports and telemetry](https://docs.warp.dev/support-and-community/privacy-and-security/privacy/#how-to-disable-telemetry-and-crash-reporting).

### Subscription refund policy

**Monthly plans**

If you signed up for a monthly Warp subscription by mistake, we can issue a full refund if you cancel or downgrade within 24 hours of being charged and no usage has been consumed during that billing cycle.

After 24 hours, or if usage has been consumed, we will cancel your subscription so that no future charges occur, and you can continue to use your plan through the end of the current billing cycle.

**Annual plans**

If you signed up for an annual Warp subscription by mistake, we can issue a full refund if you cancel or downgrade within 15 days of being charged and no usage has been consumed during that billing period.

After 15 days, we will refund you for the remaining full months on your subscription, excluding the first month.

### Purchased usage refund policy

-   **Unused purchases** - If you bought [additional usage](https://docs.warp.dev/support-and-community/plans-and-billing/add-on-credits/) by mistake, you can receive a refund as long as none of that purchase has been used. Warp cannot refund a purchase after any of its usage has been consumed. Purchased usage remains available for up to 12 months, including after cancelling a subscription.
-   **Unexpected payment method** - Purchases charge the team’s saved payment method, and any active team member can make one. See [which card is charged](https://docs.warp.dev/support-and-community/plans-and-billing/pricing-faqs/#which-card-is-charged-when-a-team-member-buys-add-on-credits) before requesting a refund.

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).

## Related pages

-   [Usage and billing](https://docs.warp.dev/support-and-community/plans-and-billing/credits/) - Inference, compute, and platform charges
-   [Purchasing additional usage](https://docs.warp.dev/support-and-community/plans-and-billing/add-on-credits/) - Purchases and auto-reload
-   [Enterprise billing](https://docs.warp.dev/enterprise/support-and-resources/billing/) - Contract pools and spending controls
-   [Pricing FAQs](https://docs.warp.dev/support-and-community/plans-and-billing/pricing-faqs/) - Subscription changes and billing management
-   [Contact support](https://docs.warp.dev/support-and-community/#contact-support) - Billing and technical support contacts
