Billing & Limits

Platform Team and Platform Production pricing, act run-minutes, guarded tokens, rate limits, and spend caps.

Open billingUsage

Blekline prices the control plane (policy, enforce, audit) and meters act run-minutes on hosted and orchestrated paths. This is not commodity sandbox pricing. Platform Team ships on Blekline runtime; Platform Production connects your cluster for cells in your VPC.

Plans

List prices are per workspace, not per engineer. Plan names below match checkout and the workspace billing UI.

PlanPlatform feeIncluded act run-minutesConnected agentsConnect compute
Local$0Not included (local hooks only)1—
Platform Team$499/mo900 min (≈ 54,000 s)25—
Platform Production$1,490/mo7,500 min (≈ 450,000 s)100Yes
Enterprisefrom $5,000/mo60,000 min (≈ 3,600,000 s)ContractYes

Upgrade or change cycle in the app or via Stripe customer portal. Enterprise starts around a $5k/mo platform commit with negotiated pools and SAML.

Usage-based meters

Hero metering is act run-minutes for cell-backed act paths. Guarded tokens apply on the hosted MCP/mask path. Enclave nodes bill separately on Production when the sidecar SKU is active.

MeterApplies toIncludedOverage
Act run-minutes
Included enforced now; Stripe overage billing rolling out
Platform Team, Production, EnterprisePer plan table (UTC month)$125 / 100 min (Team) · $200 / 500 min (Production)
Guarded tokens (GT)
Live
Hosted MCP / mask path on Team3,000,000/mo$150 / 5M GT
Guarded tokens (control plane)
Live
Production fallback sync2,000,000/moHosted fallback only
Enclave nodes
Live
Production+ with in-cluster sidecar5 on Production$125/node · min 3 when SKU active

How act run-minutes work

  • Only executionTier: act runs that launch a cell count toward the monthly pool. Think and observe steps without cells are not metered as act run-minutes.
  • Quotas reset at UTC month boundaries. Usage is the sum of billable minutes for runs created in that month.
  • Hosted runtime (Platform Team): billable minutes match wall-clock cell duration after the run completes (1 minute minimum).
  • Your cluster (Platform Production): bill orchestration minutes only, capped per run, so you are not double-charged for CPU in your cloud.
  • While a run is pending or running, the workspace holds a small optimistic minute (1 min) against the pool, not the full cell profile cap.
  • Act run-minute overage invoices are rolling out on Stripe. Included pools are enforced on the control plane today.

Rate limits

Limits protect the control plane. Exceeding them returns HTTP 429 with Retry-After. Concurrent act runs are enforced separately from the monthly minute pool.

LimitPlatform TeamPlatform ProductionEnterprise
Concurrent act runs525100
POST cell-runs / minute (workspace)1060120
Control plane API / minute (typical workspace routes)1206001200
Max cell profile duration5–120 min5–120 min5–120 min (exceptions on request)

Spend caps

Platform Team sets a default overage spend cap of 2× the platform fee ($998/mo) across metered SKUs (guarded tokens today; act run-minutes when enabled). Workspace owners can raise or disable the cap in billing settings.

Monitor usage

Open Workspace → Usage for included act run-minutes, recent runs, and guarded-token balance. Run-level proof (compileHash, infrastructure, duration) lives under Runs.

FAQ

Why not price per engineer?
Connected agents are a flat cap per workspace, not a seat SKU. A 20-person team on Platform Team pays $499/mo, not per developer.
What happens when I hit the act run-minute cap?
New act runs return a quota error until the UTC month resets or you upgrade. Enable pay-as-you-go overage in workspace billing when your plan supports metered act run-minutes.
Do failed runs count?
Terminal runs with no recorded duration bill 1 minute. Short successful runs bill actual duration (minimum 1 minute).
Local tier?
Blekline Local stays free for hooks and stdio MCP. Hosted act runs require Platform Team or higher.