What happens if I exceed a limit

Overage rates, which limits refuse instead of billing, and what is not priced.

Written By Dustin

Last updated About 6 hours ago

Two different things can happen, and which one you get depends on the limit — so the honest answer is not simply you are billed for it.

Allowances that meter into an overage

Storage, agent sessions, and hosted CI. Crossing the included amount produces a charge at the published rate rather than a refusal; nothing stops working. Free includes no CI-minutes at all, so on Free every hosted CI-minute is charged at the published rate from the first one.

Storage

$0.15 per GB-month, on the daily average in decimal GB.

Agent sessions

$0.02 per admitted session. Replay and heartbeat renewal do not create a new billable session.

Hosted CI

$0.004 per minute. Seconds accumulate across the period, are priced per second, and are rounded once at settlement.

Caps that refuse instead

These are not billable overages. They stop the operation:

  • Free storage. Above the included 5 GB, an upload is refused rather than billed.

  • Free private repositories. One. Refused on creating a second, and on flipping a public repository to private.

  • Free policy declarations. Five in the served manifest. A larger manifest is refused before it becomes your active policy.

  • Seats. Personal is one; Business is fifty.

A refusal here is a typed, explicit plan-limit answer with a remediation — not a silent failure, a hang, or a half-written push. The troubleshooting collection covers reading one.

Your organization can set its own ceiling

Each metered allowance also carries two operator controls: an optional safety ceiling above the included amount, and a switch that turns overage off entirely. With overage off, crossing the included amount becomes a plan-limit refusal instead of a charge — the right setting for an organization that would rather a runaway job stop than bill. A ceiling below the included amount is rejected as a configuration error, so a cap can never quietly take away what you already paid for.

The default is overage enabled with no additional ceiling.

What is not priced

The catalog sets no data-egress price — transfer is not metered for charging at all, so exporting everything costs nothing. It also makes no bring-your-own-runner entitlement promise: BYO runners are included only with the Enterprise dedicated add-on.

Both of these are stated as absences on purpose. If your plan depends on either, raise it before committing rather than assuming.

Avoiding surprises

  • Storage — garbage-collect after large imports. The daily average forgives a spike you clean up.

  • Agent sessions — reuse a session rather than reconnecting with a fresh grant per task. This is the difference between one billable session and hundreds.

  • CI — the once-per-period rounding means many short jobs are fine. Long-running jobs are what to watch.

  • Seats — remember the included allowances move with them, so a seat change is an allowance change too.

Seeing it coming

Usage against each limit is on the billing page through the period, not only at the end. Check it before a large migration rather than after.