Understand your usage

Four things are metered. Each is measured in a specific way, and the specifics matter more than the headline numbers.

Storage

The daily average across the organization, in decimal GB — not the peak, and not binary gibibytes. One GB is 1,000,000,000 bytes. A temporary spike that you garbage-collect within a day barely registers.

Agent sessions

One session is one admitted session grant, counted once against its own identity. Replay and heartbeat renewal do not create a new billable session, so a long-running agent that keeps its session alive is one session, not one per hour. An agent that reconnects repeatedly with fresh grants is many.

There is no cap on how many agents run at once. No plan states one. An organization that wants to spend its month's sessions in a single afternoon is not costing more, it is arriving sooner — so the meter counts sessions admitted, and nothing throttles simultaneity.

Sessions are the number to watch if you run agents at any scale, and it is the reason the plans quote them in the hundreds and thousands rather than the tens.

Hosted CI-minutes

CI seconds accumulate across the whole billing period. Billable seconds are then priced directly, at one-sixtieth of the per-minute rate per second, with exactly one rounding step: a single rounding up to whole currency units at settlement.

That is worth stating precisely, because the obvious alternative is worse. Rounding each job up to a whole minute, or rounding twice, charges for time nobody consumed — at the published rate a single extra rounding step can bill more than two unconsumed minutes. Many short jobs are therefore not penalised here.

On Business and Enterprise the allowance is granted per seat and clamped between a floor and a ceiling for the organization. Free includes none: hosted CI on the Free plan is pay as you go.

History retention

How far back hosted history is kept: 90 days on Free, 180 on Personal, one year on Business, two years on Enterprise. Enterprise additionally keeps audit records for five years, which is a different guarantee about a different thing — history retention is a recovery window for discarded work; audit retention is a compliance floor over the record of what happened.

Retention limits what the hosted service keeps. Your local clone keeps whatever you have cloned.

What is metered but not priced

Data transfer and repository-months exist as meters, but the launch catalog sets no price for either, so they are left unmetered rather than assigned an invented rate. There is no data-egress charge. Pulling everything out costs nothing.

Where to see it

Current usage against each limit is on your organization's billing page, updated through the period rather than only at the end. Owners, Admins, Billing and Auditor roles can all see it.