Skip to content
Warp

Enterprise > Support and resources

Enterprise billing

Open in ChatGPT ↗
Ask ChatGPT about this page
Open in Claude ↗
Ask Claude about this page
Copied!

Billing for Warp Enterprise: contract-specific usage pools, cloud agent costs, spending controls, and BYOLLM billing.

Your Enterprise contract sets usage pools, rates, and billing terms. Contracts that bill in credits continue to do so; dollar amounts in usage reports do not change those terms. Contact your Warp account manager for your team’s terms.

Usage under your contract

Section titled “Usage under your contract”

How credits work

Section titled “How credits work”

Inference usage depends on the model and tokens processed, including prompt caching. Similar prompts can consume different amounts because their context and responses differ.

See usage and billing for charge components and cost reporting.

Credit allocation

Section titled “Credit allocation”

Enterprise plans use a contract-specific shared team pool rather than the per-seat allowances on self-serve plans.

Cloud agent billing

Section titled “Cloud agent billing”

Cloud runs incur inference, Warp-hosted compute, and platform charges according to your contract. Platform usage measures billable active time, not the run’s total duration. Self-hosted runs do not incur Warp-hosted compute charges, but platform charges still apply.

How credits are consumed

Section titled “How credits are consumed”

Local and cloud usage draw from the shared Enterprise pool. Applicable charges depend on the inference source, hosting, and platform usage.

Agent API key runs use shared team usage. User-created schedules run as their creator by default, or as a cloud agent when configured to do so. Enterprise funding follows your contract.

For more details, see Access, Billing, and Identity.

BYOLLM billing

Section titled “BYOLLM billing”

With BYOLLM, your cloud provider bills inference directly rather than consuming Warp-provided inference usage. Applicable platform and Warp-hosted compute charges remain. External inference costs are not fully represented in Warp’s usage totals.

If a BYOLLM request falls back to Warp-provided inference, that request consumes usage at your contract’s applicable rate.

Managing billing

Section titled “Managing billing”

Your Warp account manager handles all billing for your Enterprise contract. Contact your account manager or dedicated Slack/Teams channel for:

  • Invoices and payment changes
  • Contract modifications
  • Credit allocation adjustments

For urgent billing issues, email billing@warp.dev.

Spending controls

Section titled “Spending controls”

Administrators can configure monthly spending limits and receive alerts to prevent unexpected charges. Configure these controls in the Warp Admin Panel under the Billing tab.

Monthly spending limits

Section titled “Monthly spending limits”

Enterprise administrators can set monthly spending limits across the following four categories:

  • Cloud spending limit - Cap monthly spend on cloud agent usage.
  • Local spending limit - Cap monthly spend on local agent usage in the Warp app.
  • Total spending limit - Cap combined monthly spend across both cloud and local agents.
  • Per-user spending limit - Cap monthly spend for any individual user. Set a default that applies to all users, or configure limits on a per-user basis for predictable individual spend.

Spending limits apply to both purchased usage and pay-as-you-go usage.

Multi-team workspaces can also have a workspace-level cap above their team limits. See Workspace spend limits.

Monthly spend alerts

Section titled “Monthly spend alerts”

Warp sends alerts to administrators as team usage approaches each configured spending limit, so you can adjust caps, purchase more credits, or communicate with your team before agent usage is blocked at the cap.

Credit pool depletion alerts

Section titled “Credit pool depletion alerts”

For enterprises with credit pools, administrators receive alerts as the team credit pool approaches full consumption. This gives you time to top up your credits or change your reload configuration before agent usage is interrupted for the entire team.

Section titled “Related pages”