Rex says
Money math without the spreadsheet headache. Plug in your numbers and I'll show you exactly where the dollars land.
Try a scenario
Click to load — tweak from there.Inputs
Result
Monthly CI/CD cost
$552.00
Total runner minutes consumed
72,000
Billable minutes after free tier
69,000
Annualized cost
$6,624.00
Psst — share this and help Rex grow
One click, a permanent link with your numbers baked in.
How to use this
- 1Enter pipeline runs per month.
- 2Enter average minutes per job.
- 3Enter matrix size (parallel job variants).
- 4Enter runner rate ($/minute).
- 5Enter free minutes per month.
- 6Read your monthly ci/cd cost on the right — it updates as you type.
- 7Hit Share to keep the scenario or send it to someone.
About this calculator
Most CI/CD platforms (GitHub Actions, GitLab CI, CircleCI) bill on runner-minutes consumed, with a free tier and then a per-minute rate that varies by runner type — standard Linux runners are cheapest, macOS and larger/GPU runners cost several times more per minute. This calculator takes your pipeline run frequency, average duration, and runner rate to compute monthly minutes consumed and cost after the free tier, and separately handles the common case of a matrix build running the same pipeline across multiple OS/version combinations, since that multiplies minutes consumed by the matrix size even though it's 'one' logical CI run per commit. Parallelizing a pipeline into multiple concurrent jobs reduces wall-clock time but does not reduce total billed minutes — minutes are billed per job, not per pipeline, which is a common point of confusion when a parallelization effort doesn't lower the bill the way people expect.
Worked example
Using the values the calculator loads with:
Inputs
- Pipeline runs per month: 3000
- Average minutes per job: 8
- Matrix size (parallel job variants): 3
- Runner rate: 0.008 $/minute
- Free minutes per month: 3000
Results
- Monthly CI/CD cost: $552.00
- Total runner minutes consumed: 72,000
- Billable minutes after free tier: 69,000
- Annualized cost: $6,624.00
What each field means
Inputs
- Pipeline runs per month
- The pipeline runs per month used in the calculation. Starts at 3000 so you have a working example on load.
- Average minutes per job
- The average minutes per job used in the calculation. Starts at 8 so you have a working example on load.
- Matrix size (parallel job variants)
- The matrix size (parallel job variants) used in the calculation. Starts at 3 so you have a working example on load.
- Runner rate ($/minute)
- The runner rate used in the calculation, measured in $/minute. Starts at 0.008 $/minute so you have a working example on load.
- Free minutes per month
- The free minutes per month used in the calculation. Starts at 3000 so you have a working example on load.
Results
- Monthly CI/CD cost
- Returned as a money amount in US dollars and shown as the headline result. It recalculates instantly whenever you change an input, so you can compare scenarios without reloading.
- Total runner minutes consumed
- Returned as a whole number. It recalculates instantly whenever you change an input, so you can compare scenarios without reloading.
- Billable minutes after free tier
- Returned as a whole number. It recalculates instantly whenever you change an input, so you can compare scenarios without reloading.
- Annualized cost
- Returned as a money amount in US dollars. It recalculates instantly whenever you change an input, so you can compare scenarios without reloading.
FAQ
Why didn't parallelizing my pipeline lower the bill?
Parallel jobs cut wall-clock time (how long you wait for results) but each job still consumes and bills its own minutes, so splitting one 20-minute job into four 5-minute parallel jobs uses roughly the same total minutes, sometimes slightly more due to fixed per-job startup overhead. Parallelization is a speed optimization for developer wait time, not a cost optimization for the CI bill — use it for the build-minute cost calculator's context-switch savings, not this one.
Are self-hosted runners actually cheaper?
Often yes at high volume — self-hosted runners on your own cloud VMs or bare metal avoid the platform's per-minute markup, which is typically priced well above the underlying compute cost, but you take on the operational burden of managing runner infrastructure, security patching, and auto-scaling. The crossover point is usually somewhere in the tens of thousands of billed minutes per month; below that, managed runners' convenience typically wins.
How much does test suite caching actually save on CI minutes?
Dependency and build caching (avoiding re-downloading packages or re-compiling unchanged code every run) commonly cuts job duration 30-60% for typical web and backend projects, directly reducing billed minutes by the same proportion since cost scales linearly with job minutes. It's usually the highest-leverage, lowest-effort CI cost optimization available before considering infrastructure changes.
Accuracy and limitations
- Results are estimates before tax, fees, and inflation unless an input explicitly covers them.
- Rates are treated as fixed for the whole period — variable-rate products will drift from this projection.
- This is educational maths, not financial advice. Check anything contractual with the lender or your accountant.
Related tools
Developer Hourly Cost of a Build Minute Calculator
Translate build/test wait time into real developer salary cost.
Serverless Function Invocation Cost Calculator
Turn invocation count, duration, and memory into a monthly bill.
Cloud VM Monthly Cost Calculator
Estimate the true monthly bill for a running virtual machine.
Cite this calculator
Writing about this topic? Grab a citation — every link helps keep these tools free.
RevenueLab. (2026). CI/CD Minutes Cost Calculator. Retrieved from https://www.revenuelab.fyi/toolbox/cicd-minutes-cost
<p>Source: <a href="https://www.revenuelab.fyi/toolbox/cicd-minutes-cost" target="_blank" rel="noopener">CI/CD Minutes Cost Calculator — RevenueLab</a> (2026).</p>
Source: [CI/CD Minutes Cost Calculator — RevenueLab](https://www.revenuelab.fyi/toolbox/cicd-minutes-cost) (2026).