$ ~/cicdcalculator

CI/CD cost for 2,000 build minutes per month, 2026
./tier --monthly-mins=2000 --linux-2-core

Two thousand monthly build minutes is the entry tier for serious CI/CD usage. It is enough to run continuous integration for a small team or a single small product. It is also the exact number that GitHub Actions Free includes per month on private repositories, which makes it a useful benchmark across the industry. This page works through what every major CI/CD platform charges at exactly 2,000 monthly Linux build minutes in 2026, with assumptions explicit and citations to vendor pricing pages.

All numbers below assume Linux 2-core hosted runners (or platform equivalents), a 5-person team where seat fees apply, and 2,000 monthly minutes total across the team. Pricing pulled from vendor sites in May 2026.

Side-by-side at exactly 2,000 minutes

PlatformPlanSeatComputeTotal / mo
GitHub ActionsFree$0$0 (in allowance)$0
GitLab CIFree$0$16 (1,600 over)$16
GitLab PremiumPremium$145 (5 x $29)$0 (in allowance)$145
CircleCIFree$0$0 (6K credits = 600 mins)$8 (extra credits)
Bitbucket PipelinesStandard$15 (5 x $3)$0 (in 3,500 allowance)$15
BuildkiteDeveloper$0 (free up to 5 users)~$30 (one EC2 agent)$30
JenkinsSelf-hosted$0 (MIT)~$60 (controller + agent)$60+ admin time
Drone CISelf-hosted$0 (Apache)~$15 (single VM)$15

# Self-hosted total excludes engineer time, which dominates real cost at this scale. Hosted total includes seat fees for a 5-person team.

The cheapest options

GitHub Actions Free at $0 is the cheapest hosted option, by definition: it ships exactly 2,000 monthly Linux minutes for free on private repositories. Public repositories are unlimited. For a small team or solo developer who fits inside this allowance, no other platform competes on price.

CircleCI Free at around $8 per month is close. The Free plan includes 6,000 monthly credits, which is roughly 600 Linux Medium minutes. The remaining 1,400 minutes cost about 14,000 credits, or $8 in overage. CircleCI Free is the right pick for a team that wants the CircleCI feature set (test splitting, machine-class flexibility, orbs marketplace) without committing to a paid plan yet.

Drone CI self-hosted on a $15 single-VM setup is the cheapest non-managed option for teams comfortable operating their own CI. The dollar cost is small but the time cost is real: even a tiny Drone setup needs an hour or two of monthly attention.

The traps to watch for

GitLab Free's tiny 400-minute monthly allowance is easy to miss. A team migrating from GitHub Actions Free expecting comparable headroom will hit overage immediately. Either plan to upgrade to Premium ($29 per user with 10,000 included minutes, but expensive at small team sizes) or budget for $0.010 per overage minute on the Free plan.

Bitbucket Pipelines Free is even tinier at 50 monthly minutes. The Free plan exists to enable evaluation and tiny hobby projects only. Any production team on Bitbucket Cloud Free will need to upgrade to Standard ($3 per user, 3,500 monthly minutes) almost immediately.

Self-hosted options are not free. The dollar cost is small ($15-60 monthly for the infrastructure) but operator time at a fully loaded engineering rate dwarfs that. A team running self-hosted Jenkins or Drone or GitLab CE at the 2,000-minute scale spends 2-4 hours per month of admin time, which is $300-600 in implicit cost. Below 2,000 monthly minutes, hosted is almost always cheaper than self-hosted on full-cost accounting.

Planning for the next tier

Most teams outgrow 2,000 monthly minutes inside their first year. Triggers include adding integration tests, expanding the team beyond 3-4 developers, adopting matrix builds for cross-platform support, or shipping a second product on the same CI infrastructure. When monthly usage consistently approaches 1,800 minutes, it is time to revisit the cost analysis with the next tier in mind.

The natural next tiers are 25,000 monthly minutes (the typical 20-25 dev team) and 100,000 monthly minutes (where self-hosted starts to be the default answer). The cost ranking changes meaningfully at each tier; assumptions that hold at 2,000 minutes may not hold at 25,000.

Other tiers and platform deep dives

25K minutes / mo100K minutes / mofree CI/CD optionscompare all platformscost optimizationcost calculator

Frequently Asked Questions

# click any question to expand

Is 2,000 build minutes per month a lot or a little?>
Small to moderate. A 5-developer team running 30 daily builds at 6 minutes each consumes about 3,800 minutes per month, almost double 2,000. A 2-3 person early-stage team running CI on PR pushes only consumes 1,000-1,800 minutes typically. So 2,000 minutes is the sweet spot for very small teams or for teams that have been deliberate about caching and conditional jobs.
Does GitHub Actions free tier cover 2,000 minutes?>
Yes exactly: 2,000 Linux minutes per month is the GitHub Actions Free tier private-repo allowance. A team that fits inside this allowance pays $0 for CI/CD on Actions, period. Push past it and you either upgrade to Team ($4 per user, 3,000 included Linux minutes per organisation) or pay overage at $0.010 per minute.
Why does GitLab Free seem worse here?>
GitLab Free includes only 400 minutes per month per group, far less than GitHub. For a 2,000-minute month, GitLab Free covers 20 percent and you would pay $16 in overage at $0.010 per minute. The math has GitLab as roughly 4x as expensive at this volume on the Free tier. GitLab Premium ($29 per user) includes 10,000 minutes per group and is more competitive once you have a few users, but the seat fees are themselves expensive at small scale.
What is the cheapest option at 2,000 minutes?>
GitHub Actions Free is the cheapest at exactly $0. Bitbucket Pipelines Free covers only 50 minutes monthly so you would pay overage of around $20 in extra-minute packs. Self-hosted Drone CI on a $30 EC2 instance is competitive but only if you do not value the operator time at this scale. For teams operating on a strict zero-budget CI/CD constraint, GitHub Actions Free or self-hosted Drone are the two answers.
When should I plan to outgrow this tier?>
Most teams outgrow 2,000 monthly minutes within 6-12 months as the team grows or as the test suite expands. The most common upgrade trigger is adding integration tests or end-to-end browser tests, which can double or triple build minutes overnight. Plan to revisit the cost analysis when monthly minutes consistently exceed 1,800 or when builds start queueing during peak hours.
Is 2,000 minutes enough for a small open-source project?>
Yes if the project is on GitHub. Public-repo Actions usage is unlimited on GitHub Actions Free, so an open-source project on GitHub uses zero of the 2,000-minute private allowance regardless of how many builds run. The same applies to most CI platforms for OSS workloads (GitLab, CircleCI, Drone all have OSS programmes). Move to a paid tier only if private-repo usage is also a part of the workflow.