CircleCI pricing in 2026, and how credits turn into a bill
CircleCI's Performance plan starts at $15 a month, but almost nobody pays $15. The real bill comes from credits, which every build minute, cache and gigabyte of storage burns, plus a charge for each user over five. This post explains how credits work, what each plan includes, and how to estimate your own bill.
All prices below were checked on CircleCI's pricing page on 18 November 2026. Prices exclude applicable taxes.
CircleCI's plans
| Plan | Price | Credits | Users | Concurrency |
|---|---|---|---|---|
| Free | $0 | 30,000 a month | 5 active users | 30 jobs |
| Performance | From $15 a month | 30,000 a month, then pay as you go | 5 included, then $15 each a month | 80 jobs |
| Scale | Custom, billed annually | Custom | Custom | Unlimited |
The page's comparison table describes Performance's included credits in a garbled way, so confirm with CircleCI whether the $15 base covers the first 30,000 credits.
How credits work
Everything on CircleCI is priced in credits:
| Item | Price |
|---|---|
| Extra credits on Performance | $15 per 25,000 |
| Prepaid bulk credits | From 1 million for $600 |
| Linux Medium machine | 10 credits per minute |
| Docker layer caching | 200 credits per job run, which the page says equals $0.12 |
| Network and storage above plan limits | 420 credits per GB |
| IP ranges | 450 credits per GB of data used |
At $15 per 25,000, a credit costs $0.0006. The page says bulk discounts start at 5 million credits for $3,000, which is the same per-credit rate, so ask what discount applies at your volume.
CircleCI's own example: 30,000 credits on Linux Medium buys 3,000 build minutes. Bigger machines burn credits faster, and free credits expire monthly rather than rolling over.
What each plan adds
Free ($0):
- 30,000 credits a month, which the page says is up to 6,000 build minutes on a small Docker machine
- 5 active users and 30 concurrent jobs
- 1 GB of network and 2 GB of storage
- Docker layer caching and private orbs
- Community support only
Open-source projects get up to 400,000 credits a month on Linux, Arm and Docker.
Performance (from $15):
- 80 concurrent jobs, plus larger machines including X-large and macOS M4 Pro Large
- 5 GB of network and 2 GB of storage
- IP ranges and unlimited flaky test detection
- Ticket-based support, with 8x5 SLAs available
Scale (custom):
- Unlimited concurrency and the largest machine classes, including GPU
- SSO and config policies
- 50 GB of network and 200 GB of storage
- 8x5 and 24x7 support SLAs available
SSO is only on Scale. If your security policy requires SSO, Performance isn't an option, so get a Scale quote early.
A worked example
Here's an estimate for a 15-person team that runs 30,000 Linux Medium build minutes a month on Performance:
| Item | Calculation | Monthly cost |
|---|---|---|
| Plan base | Starting price | $15 |
| Extra users | 10 users over the 5 included, at $15 | $150 |
| Credits | 300,000 used, minus 30,000 included, at $0.0006 | $162 |
| Estimated total | $327 |
That's about $3,900 a year, before caching, storage or bigger machines. Note that users cost almost as much as compute here. For a larger team that builds less, seats can be most of the bill.
This is an estimate from published rates. The page doesn't say whether credits are sold in whole 25,000 blocks, so your invoice may round up.
How to cut the bill
- Count active users. Users beyond five cost $15 a month each on Performance. Check who actually triggers builds.
- Right-size machines. Larger resource classes burn credits faster. Move jobs that don't need the extra power to smaller machines.
- Use caching where it saves time. Docker layer caching costs 200 credits per job, so it only pays off when it saves more than that in build minutes.
- Stop redundant builds. Skip builds on documentation changes, and cancel superseded builds on the same branch.
- Buy credits in bulk once usage is steady. Ask what discount applies at your monthly volume before prepaying.
- Compare with what you already pay for. If your code is on GitHub, compare against built-in CI minutes. Our guide to negotiating a SaaS renewal covers using a competing quote.
What to do with this
Estimate your monthly build minutes by machine size and your active user count. Those two numbers decide the bill on Performance. If you need SSO or unlimited concurrency, go straight to a Scale quote.
See how CircleCI compares with GitHub Actions and other CI tools, or post an RFP with your build minutes, user count and current spend, and let CI vendors bid. Our software RFP template shows what to include. It's free, and you can post anonymously.
Paying too much for a tool?
Post what you pay and the features you use. Sellers bid to replace it for less. Free, and you can post anonymously.