Pricing and usage

Compare plan terms, included allowances, overage, and workspace usage.

Before you begin

Use Labor0 pricing for the public plan comparison. Use the authenticated app for current workspace usage, billing readiness, payment setup, and invoices.

Bring your own provider account or key (BYOK)

Codex, Claude Code, and OpenCode use a customer-owned provider account or credential. You remain responsible to the provider under that account or plan, and Labor0 adds no markup to those coding-agent provider costs. This applies to local and hosted agent execution on every public plan: Sandbox, Pay-as-you-go, Team, Business, and Enterprise. Provider access, subscriptions, credentials, and usage limits depend on the provider and configured execution environment; Labor0 does not supply a provider account and provider usage is not unlimited. Hosted execution can still incur Labor0-hosted runtime and network usage.

Current public terms

All prices below are tax-exclusive.

Plan	Public price (tax-exclusive)	Included grant	Labor0-managed AI usage	Metered overage and soft alert
Sandbox	$0	One $5 lifetime hosted grant	—	No overage. Hosted execution is blocked when the lifetime grant is exhausted.
Pay-as-you-go	$99/month	None	25%	Unlimited metered overage by default; $100 default soft alert
Team	$199/month	$99 pooled grant per billing period; expires without rollover	15%	Unlimited metered overage by default; $500 default soft alert
Business	$1,500/month	$1,000 pooled grant per billing period; expires without rollover	10%	Unlimited metered overage by default; $5,000 default soft alert
Enterprise (sales-managed)	$24,000/year platform fee	None; usage commitments and rate cards are contracted separately	Contracted separately	Contracted separately

Paid plans may have unlimited metered overage with soft alerts; allowances, pooling, expiry, and plan-specific Labor0-managed AI usage are governed by the current customer-facing terms.

Plan-independent Labor0-managed usage defaults

These plan-independent defaults apply unless a customer's billing profile overrides them. They do not vary by plan.

Usage	Default Labor0-managed usage markup
Cloudflare AI Search	35%
Cloudflare network	75%
Hosted runner compute	200%
Hosted runner network	50%
Envbox	25%
Meeting capture	50%

Signed in? Open the Labor0 app, then go to Settings > Billing & Security > Billing and review Billing details for your actual values.

Local execution

Local execution is available to active paid workspaces with an active subscription, regardless of member count, and to active Sandbox workspaces with at most one active member. Use the complete Labor0 CLI bundle, follow Set up and run, and use Manage and troubleshoot for recovery. Local execution remains available independently of hosted allowance and payment-method readiness. It does not create a SKU, change Sandbox's $0 recurring price, add overage, or change the $5 lifetime hosted allowance. Labor0 does not charge for local compute; you pay for your own machine resources and any customer-owned Codex, Claude Code, or OpenCode provider account or credential costs. Hosted execution can still incur Labor0-hosted runtime and network usage.

In the browser, Auto prefers an eligible active local runner but may use hosted fallback. An active online CLI-managed runner does not currently enable Local only because Labor0 cannot confirm readiness for the selected coding-agent runtime. Local only never falls back to hosted execution. Before approving work, confirm final Local runner attribution; if hosted fallback is unacceptable, do not submit the browser task with Auto, because hosted work may begin before final attribution is available; stop before retrying. Continue with Run your first task for the complete task flow.

Completed payments are not automatically refunded. Downgrades and cancellations do not provide a refund, unused-time proration, or unused-allowance rollover.

Procedure

Compare public plan terms on the marketing site.
Open Settings > Billing & Security > Billing in the Labor0 app.
Read Execution eligibility, then confirm the authenticated subscription and reporting period.
Compare Current month usage, Budget consumed, Balance available, and the current soft-alert threshold. Use the displayed values rather than reconstructing internal accounting.
Let the billing owner use the offered Start checkout, Resume checkout, or Preview change action and review the protected payment or invoice handoff before confirming anything.

Example interpretation

Visible state	Interpretation
Billable execution available	New AI and hosted-runner work can start under the current billing state
Active subscription with a future grant expiry	The displayed grant is available only under the shown period and expiry rules
No limit configured for budget	There is no monthly budget limit; a soft alert is not a hard stop
Start checkout	A Sandbox-to-paid checkout is available; the plan has not changed yet
Resume checkout	An incomplete checkout can continue; the paid subscription is not active yet
Preview change	The plan is available for review; selecting it has not yet completed a plan change
No pending change reported	The app currently has no scheduled plan change to display

Expected result

The public plan name and terms match the authenticated subscription, while the app provides the workspace-specific period, usage, balance, alerts, and payment state. A plan change is not complete until the authenticated app reports the new or pending subscription state.

Permission guidance

Plan changes, payment setup, invoices, and budget controls are protected billing actions. Docs never ask for card data or a provider reference.

If a usage total surprises you

Symptom: a balance or alert differs from expectation. Likely cause: period, pooled allowance, expiry, or overage policy. Safe recovery: confirm plan and period in the app, then ask the billing owner or support for a customer-level review.