Pipeline Cost Calculator
Estimate the total cost of running Jenkins pipelines from agent compute hours, artifact/workspace storage, and network egress.
Inputs
Total agent runtime hours consumed across all pipelines per month.
Compute cost per agent-hour (on-demand VM/container pricing).
Monthly cost of artifact and workspace storage.
Monthly egress/network cost (image pulls, artifact transfers, etc.).
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
Compute cost = agent hours × cost/hr
2000hr × $0.1
= $200.00
Total = compute + storage + network
$200.00 + $25.00 + $10.00
= $235.00/month
How it works
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
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.