Hosted runner time is measured per second and varies by machine size. Cache storage is measured separately by GB-month and prorated to the second. Skipped jobs, reused steps, unselected tests and cache hits do not use billable runner time. The rates shown are illustrative while pricing is finalized.
Runner time. Billed per second while a job executes. Provisioning before the first step and cleanup after the job are not billed.
Skipped work. A job that is not scheduled holds no machine. A reused step restores its recorded output. An unselected test never starts. None of these use runner time.
Cache hits. Reading from the cache is not billed. Cache storage is billed separately, at the illustrative per GB-month rate.
Verification. Reading a record, verifying a signature and exporting a receipt are included in the run.
The amount you save depends on your commit history. A change to a lockfile can select every test, and the bill reflects the runner time that actually ran.
| Line | Value |
|---|---|
| Runs per month | 2,000 |
| Jobs per run | 14, of which 3 execute |
| Runner size | 4 vCPU |
| Average job length | 4 minutes |
| Runner time billed | 2,000 × 3 × 4 = 24,000 runner-minutes |
| Runner cost | 24,000 × 60 × $0.0004 = $576.00 |
| Cache storage | 40 GB × $0.02 = $0.80 |
| Total | $576.80 per month |
| Same pipeline without skipping | 2,000 × 14 × 4 = 112,000 runner-minutes = $2,688.00 |
Yes, for the runner-seconds it held, under the same rule as a passing job.
Nothing. A skipped job holds no machine, so it uses no runner time.
Share a month of job counts and durations. We can apply the per-second model to your workflow and show how reuse and selection change the bill.