Pipeline Cost Calculator
Estimate compute cost of running a CI/CD pipeline based on runtime and agent pricing.
About Pipeline Cost Calculator
Total CI/CD pipeline cost is rarely just compute — it's the sum of agent compute hours (the dominant driver for most fleets), storage for artifacts and workspaces, and network egress for pulling images, dependencies, and transferring artifacts. Breaking the total into these three components makes clear where cost-optimization effort pays off most; compute usually dominates, so reducing build time or agent idle time typically yields more savings than storage or network tuning alone.
Formula
totalCost = (agentHours × costPerHour) + storageCost + networkCost
- A
- Agent compute hours per month
- c_h
- Cost per agent-hour
- S
- Storage cost per month
- N
- Network cost per month
- C
- Total monthly pipeline cost
Worked example
With the default values below, Pipeline Cost Calculator returns Total Monthly Pipeline Cost of $235.00. Change any input above and every figure here is recalculated in your browser.
Inputs used
- Agent Compute Hours per Monthaccepts 0–10,000,000 hr
- 2,000 hr
- Cost per Agent Houraccepts 0–1,000
- 0.1
- Storage Cost per Monthaccepts 0–1,000,000
- 25
- Network Cost per Monthaccepts 0–1,000,000
- 10
Results
- Total Monthly Pipeline Cost
- $235.00
- Projected Annual Cost
- $2,820.00
- Compute Cost
- $200.00
- Compute Share of Total Cost
- 85.1%
Step by step
- 1Compute cost = agent hours × cost/hr= $200.00
- 2Total = compute + storage + network= $235.00/month
Assumptions and limits
- The result is derived only from the 4 inputs listed above. Anything not among them is not part of the calculation.
- In particular, this calculator does not take inflation, tax or compounding frequency into account.
- Figures are rounded for display to 2 decimal places, so totals built from several rounded parts can differ slightly from the unrounded arithmetic.
How these calculators are built and tested is described on the Methodology page. If a figure looks wrong, please report it.
Frequently Asked Questions
Why does compute usually dominate total pipeline cost?
Agent-hours scale with build frequency and duration across potentially hundreds of daily builds, while storage and network costs tend to grow much more slowly and are easier to cap with retention policies, so compute is both the largest and most variable cost component.
How can I reduce agent compute cost without adding hardware?
Use spot/preemptible instances for non-critical builds, right-size agent instance types to actual CPU/memory needs, enable agent auto-scaling to avoid paying for idle agents, and reduce build duration through caching and parallelism.
Should self-hosted agent costs be modeled differently?
Yes — for self-hosted (non-cloud-billed) agents, 'cost per agent hour' should be derived from amortized hardware/depreciation and power costs divided by available agent-hours, rather than an on-demand cloud rate, since idle self-hosted capacity is a sunk cost either way.