Operate

Usage and billing

Understand when runner usage starts, minute rounding, and workspace totals.

Runner usage is recorded in whole minutes using the rate for the selected runner family, size, and architecture. Check the rate applicable to your workspace before changing labels.

For the current managed runner setup, the usage clock begins when Sprintbox delivers the runner's configuration and marks it ready. It ends when Sprintbox finalizes that runner's usage as cleanup begins. This can include a short interval before the job starts and after GitHub reports that it has completed. It is not the sum of your workflow step durations.

Time spent waiting before the runner is ready does not add Sprintbox runner minutes. A runner that never becomes ready, or never takes a job, does not receive a runner-minute charge. A job that starts and subsequently fails or is cancelled still uses runner time.

Each runner's measured duration is rounded up to the next whole minute. For example:

At a rate of R per minute, a measured interval of 3 minutes 20 seconds costs 4 × R. This example describes rounding, not a quoted price.

Read the dashboard

Allocated capacity describes capacity assigned to active runners. Requested capacity includes active runner requests. Neither value is a count of billable minutes.

Today's usage and Last 30 days show recorded charges for the whole workspace. These totals can include other connected accounts, and active jobs may not appear in recorded charges until their usage is finalized.

GitHub's workflow elapsed time can include queueing and multiple jobs. A job's step time can omit runner setup and finalization. Those durations serve different purposes and can differ from the rounded usage recorded by Sprintbox.