Labor0 Docs

Pricing and credits

Labor0 uses credits to make AI/provider and hosted runtime usage visible before billable work expands.

Credit normalization

One dollar is 1,000,000 Labor0 credits. Public plan copy can show included usage as dollar-denominated values derived from canonical credits.

  • $5 of included credits is 5,000,000 credits.
  • $99 of included credits is 99,000,000 credits.
  • $1,000 of included credits is 1,000,000,000 credits.

Credits normalize AI/provider usage, hosted runtime usage, and other billable platform work into one customer-visible unit. Canonical usage ledgers, charging state, and billing records stay outside public docs.

Public plan frame

Labor0 public pricing currently frames Sandbox, Pay-as-you-go, Team, Business, and Enterprise plans. Team is the recommended plan for active teams adopting Labor0 with budget caps and visible overage controls.

  • Sandbox is $0/month with $5/month included credits and no overage until the customer upgrades.
  • Pay-as-you-go is $0/month with no included credits. Billable work uses AI/provider cost plus 25% markup after overage is enabled.
  • Team is $99/month with $99/month included credits. Overage uses AI/provider cost plus 15% markup.
  • Business is $1,000/month with $1,000/month included credits. Overage uses AI/provider cost plus 10% markup.
  • Enterprise uses a custom annual commit with 5-10% markup or a negotiated rate card, with overage defined by contract.

The public pricing page owns the customer-facing plan cards and offer presentation.

Billing profiles and invoices

A billing profile is the protected settlement record for a tenant or enterprise. Workspaces are where usage is authorized, attributed, budgeted, and shown to teams; the billing profile is where payment setup, invoice ownership, settlement settings, and included-credit accounting live.

Billing setup, payment instruments, invoices, payment setup sessions, and billing profile updates stay in authenticated product flows. Public docs describe the model, but they do not expose payment details, invoice contents, or private finance operations.

Budget controls and billing

Budgets are controls that limit or warn on workspace usage before work expands. They are additive controls on top of included credits and billing profiles, not a second settlement owner.

Budget caps, warning thresholds, projected month-end spend, overage enablement, and billing setup are authenticated app workflows. Public docs explain the model, while canonical billing state remains protected.

Usage visibility

Labor0 usage views help teams understand where credits are going before spend grows. Customer-facing summaries can roll up usage by period, workspace, service, project, environment, and actor when those dimensions are available.

Raw usage-ledger entries, adjustments, reversals, backfills, reconciliation details, and finance exports stay in protected app and service workflows. Public docs should explain what readers can expect to see without exposing private usage data.

Next