Commercial CI/CD

Billing and usage controls

Choose Free, Team, or Business; set hosted runner hard caps; monitor shared storage; and use Stripe checkout and Customer Portal safely.

Compare plans

Plans

Free, Team, and Business define users, repositories, pipelines, hosted minutes, Agent Tasks, storage, retention, and hosted concurrency entitlements. Claim-time scheduling enforces workspace concurrency in addition to worker capacity.

Hosted spend controls

The claim transaction checks finalized billable usage plus one reserved minute for each active assignment and the next claim when overages are disabled. This minimum reservation does not bound the full active duration. Overage reconciliation can be invoked explicitly or by an opt-in web/control-plane background service for the completed prior month, using pending exact-period reservations and Stripe idempotency.

Shared storage

Artifacts, logs, reports, coverage, cache archives, recorded Shipline Git sizes, and unique Registry blob digests contribute to usage. Registry manifest metadata is not counted. Git pushes preflight bounded pack request size against remaining quota before exact post-push accounting; compressed request size does not guarantee final object size.

Billing launch checklist

Set a real billing contact, confirm Stripe checkout for Team and Business, open Customer Portal, request hosted runner access, choose hard caps, decide overage policy, and verify billing usage API fields including Agent Task activity before inviting production users.

Billing persistence limits

Checkout attempts persist before Stripe calls and reuse unexpired ready URLs for the same plan. Webhook acquisition is atomic by global event ID; failed inbox entries can be reacquired on redelivery, and older subscription lifecycle events are ignored. Subscription mutation and inbox completion are separate operations. Checkout correlation, stale-processing recovery, invoice/payment/refund reconciliation, and live Stripe evidence remain required.