CI/CD Tools Comparison 2026: GitHub Actions vs GitLab CI vs CircleCI vs Jenkins vs Buildkite

As of August 2026, most teams no longer operate without a pipeline that automates everything from the moment code is committed through to deployment. The problem is that “which CI/CD tool should we use” is still a decision whose right answer shifts every year. This CI/CD tools comparison isn’t built on brand recognition or GitHub star counts — every claim here is checked directly against each vendor’s official pricing pages, release notes, and security advisories. A lot has genuinely changed in the last six months: GitHub Actions announced (and then walked back) charging for self-hosted runners, GitLab’s AI agent went GA, and Jenkins racked up one security advisory after another.

The five platforms under comparison are the two that effectively split the market — GitHub Actions and GitLab CI/CD — plus CircleCI, the original open-source automation server Jenkins, and Buildkite, which has been steadily gaining ground as a GitHub Actions alternative. The right answer here depends heavily on where your repository lives, whether you can run self-hosted runners, and how big your team is — so “just use this one” advice is genuinely risky in this space.

There are three points this CI/CD tools comparison wants to drive home in particular. The three axes buyers actually keep coming back to in searches and reviews are: (1) the free tier and build minutes (cost), (2) the cost structure of self-hosted runners (whether they’re billed per minute), and (3) security (keyless OIDC authentication, secrets management). Pull these five tools apart along those three axes and you’ll find real, practical differences that the word “free” alone completely hides.

Below, we start with a full comparison table, then dive into feature-by-feature deep dives, a concurrency and security benchmark, a complete pricing breakdown, recommendations by user type, practical tips and common mistakes, and an FAQ. Wherever a figure couldn’t be verified, we’ve marked it “unconfirmed” instead of guessing — so feel free to use this as a working reference when you’re setting budgets and architecture.

1. Executive Summary: The CI/CD Tools Comparison at a Glance

For developers and team leads short on time, here’s the essence of the five leading CI/CD tools as of August 2026, compressed into one table.

📊 The Complete August 2026 Comparison Table for the Top 5 CI/CD Tools

The line in this table most worth lingering on is “self-hosted runner cost.” All five tools charge effectively nothing for self-hosting itself, but the reasons and conditions behind that differ sharply. GitLab is built from the ground up so that self-hosted runners never consume plan minutes on any tier, whereas GitHub Actions once announced — then rescinded — a plan to start charging for it, leaving it tagged with an implicit “free for now, but could come back” caveat. Set your budget without knowing this distinction and you could end up in an awkward spot later.

2. Feature Deep Dive: The Top 5 CI/CD Tools

⚙️ 1) GitHub Actions — the default that’s already built into your GitHub repo

• A built-in feature with no version number of its own: GitHub Actions is a workflow engine baked into GitHub.com rather than a standalone product with its own version numbering. Its notable 2026 GA features include OIDC Custom Property Claims, which shipped generally available in April (letting you fold a repository’s custom properties into OIDC claims for more granular trust policies), and the Runner Scale Set Client, which entered public preview in February.
• The 2026-01-01 price cut: Public repositories run completely free on every runner type, and private repositories get monthly minutes included — 2,000 on GitHub Free, 3,000 on Pro/Team, and 50,000 on Enterprise Cloud. Overage billing dropped by as much as 39% effective January 1, 2026: Linux 1-core (x64) is now $0.002/minute, Linux 2-core (x64) is $0.006/minute (down from $0.008), Windows 2-core (x64) is $0.010/minute (down from $0.016), and macOS 3–4-core is $0.062/minute (down from $0.080).
• The self-hosted-runner-fee announcement and reversal: On December 16, 2025, GitHub announced it would start charging a $0.002-per-minute “platform fee” on self-hosted runners too, effective March 1, 2026. Community backlash followed almost immediately, and GitHub indefinitely postponed the plan, calling it something to “re-evaluate.” As of June 2026 it still hadn’t gone into effect, with no confirmed date for reintroduction. The bottom line: as of August 2026, self-hosted runners are still completely free, but it’s worth noting that GitHub’s official position — that it may revisit this “in the future” — was never actually withdrawn.
• Keyless OIDC deployment and the security roadmap: OIDC, which authenticates with short-lived tokens instead of storing static secrets with a cloud provider, is now the standard, and the Custom Property Claims feature above takes that a step further. That said, GitHub’s own security roadmap notes that stolen secrets (token theft) have been a leading vector in some of the largest supply-chain attacks over the past year, and additional defenses like workflow dependency locking are planned. Caching is handled through the actions/cache action, lockfile-hash-based cache keys, and the built-in caching options in official actions like setup-node.
• Thinking past deployment: If the endpoint of your pipeline is container orchestration, our Docker, Kubernetes, and other container tools comparison covers the next decision; if it’s a PaaS, see our Vercel, Netlify, and web hosting comparison.

🦊 2) GitLab CI/CD — the platform where an AI agent has moved inside the pipeline itself

• GitLab 19.2 (released 2026-07-16): In January 2026, GitLab 18.8 brought the “GitLab Duo Agent Platform” to general availability, and in July 2026’s 19.2 release, CI Expert Agent — an AI agent that helps build, debug, and optimize CI/CD pipelines — went GA. This is a clear example of the AI coding agent trend (Cursor, GitHub Copilot, and peers) expanding beyond writing code and into the CI/CD pipeline itself.
• The standout advantage: self-hosted runners deduct zero minutes: The Free plan costs $0/user, caps groups at 5 seats, and includes 400 CI/CD compute minutes/month plus 10GiB of storage. The key detail here is that on every single plan, attaching a self-managed (self-hosted) runner consumes zero compute minutes. In other words, once you have self-hosted runner infrastructure in place, you can run CI essentially unlimited and free.
• Premium and Ultimate pricing: Premium runs $29/user/month (billed annually) and includes 10,000 compute minutes/month, 500GiB of storage, and $12/month of GitLab Duo credits per user. Ultimate is quote-based (pricing isn’t published) and bundles 50,000 compute minutes/month plus $24/month of Duo credits, while Ultimate Plus (formerly GitLab Dedicated) is also a custom sales quote. Exceeding your shared-runner minutes costs an extra $10 per 1,000 minutes ($0.01/minute). There’s also a program offering free Ultimate licenses and 50,000 minutes/month to open-source projects, educational institutions, and startups.
• 19.2’s “AI paradox” response theme: Dependency Scanning Auto-Remediation, Security Review Flow, Duo CLI, and Custom Flows all either graduated from beta or entered public beta in 19.2. The core theme of this release is agentic automation aimed at the problem of “security and review processes struggling to keep pace with the speed at which AI generates changes.”
• What’s unconfirmed on OIDC: GitLab CI has long supported OIDC via the id_tokens: keyword, but this research couldn’t confirm whether that feature saw any changes in 2026. With no solid basis for a definitive claim, we’re treating this simply as “the existing feature, unchanged.”

🔵 3) CircleCI — cloud-only CI with clearly published concurrency specs

• A credit-based free plan: Free costs $0/month and includes 30,000 credits/month (the official page describes this as equivalent to “up to 6,000 build minutes”), with up to 5 active users, concurrency of 30x in most environments (1x on macOS), and no credit card required.
• One of the few tools that publishes hard concurrency numbers: The Performance plan (from $15/month) includes 30,000 credits, adds $15/month per additional user (which adds 25,000 credits each), and bumps concurrency up to 80x in standard environments and 15x on macOS. Additional credits can be purchased at $15 per 25,000 ($0.0006/credit). The Scale plan is a custom, annually billed quote with concurrency, seat count, and 24/7 support all configured to order.
• Miss the credit expiration window and you lose out: Free credits expire every month and don’t roll over. Purchased paid credits, by contrast, stay valid for 12 months. Miss that distinction and it’s easy to assume “the free credits I didn’t use this month will carry over to next month” — they won’t.
• Self-hosted runners and network limits: CircleCI Runner doesn’t deduct credits, but the exact rate of the “small per-minute orchestration fee” referenced in some third-party sources couldn’t be re-verified on the official pricing page, so we’re leaving it unconfirmed. Network transfer is capped at 1GB on Free, 5GB on Performance, and 50GB on Scale; storage is 2GB on Free/Performance and 200GB on Scale.
• Enhanced OIDC: You can authenticate to AWS, Azure, Vault, and similar services without static credentials by supplying OIDC tokens via the $CIRCLE_OIDC_TOKEN/$CIRCLE_OIDC_TOKEN_V2 environment variables, and these tokens recently gained three new claims — organization ID, pipeline ID, and pipeline-definition ID (enhanced OIDC tokens).

🐘 4) Jenkins — fully open source, but the operational security burden is real

• Jenkins 2.568.1 LTS (released 2026-07-08): The regular release stream picks an LTS (stable) build every 12 weeks, then ships security, bug-fix, and select feature backports every 4 weeks after that. Starting with the 2.555.x line, Java 17 support has ended, making Java 21 or 25 mandatory — a requirement that still applies to the current LTS, 2.568.1, released 2026-07-08.
• License cost: $0. Total cost of ownership: a different story entirely: Jenkins is fully open source with zero license fees. Instead, 100% of the cost comes from infrastructure (servers, agents) and the people needed to run it. If you need commercial support, you’ll need a separate paid support or enterprise-plugin contract with a third-party vendor like CloudBees — and CloudBees’ specific 2026 pricing isn’t published, since it’s a private-quote policy.
• A steady stream of security advisories over the last six months: Between March and June 2026 alone, at least five official security advisories were published, covering a core vulnerability (arbitrary file creation), a stored XSS in the GitHub Plugin, a missing symlink restriction in the Pipeline: Groovy Libraries Plugin (allowing arbitrary file reads), arbitrary-type deserialization via config.xml submission, and a missing permission check in the Gitee Plugin (allowing credential theft).
• A wide plugin ecosystem means a wide attack surface: The cases above are concrete, quantitative support for Jenkins’ structural trait: more plugins mean more convenience, but also a proportionally larger attack surface. That said, we couldn’t confirm an up-to-date total plugin count (as of August 2026), so rather than trusting the commonly cited “1,800+ plugins” figure at face value, it’s safer to check the official plugin index directly.
• Built around a self-hosted premise from day one: Since Jenkins was designed as a fully self-hosted tool from the start, where you put your controller and agents — on-prem, VM, or container — is entirely up to you. That’s exactly why it’s still the pick for air-gapped environments and heavily regulated organizations.

🚦 5) Buildkite — a hybrid architecture absorbing teams migrating off GitHub Actions

• SaaS orchestration + 100% self-hosted agents: Buildkite’s core design is a hybrid: the control plane is Buildkite’s SaaS, while actual build execution happens on agents running inside your own infrastructure. As of the 2026 release, agent version v3.127.2 or later is recommended.
• A Personal plan that’s free forever: No credit card required, free forever, with no expiration. That said, it’s limited to 1 user, 3 concurrent jobs, and 90-day build retention. Pro runs $30/month per active user, unlocking unlimited users and concurrent jobs and including 10 self-hosted agents (additional agents cost $3.50/month each), with build retention extended to 1 year. Enterprise is a custom quote starting at a 30-user minimum.
• A new product: hosted agents: Buildkite now also offers hosted compute, where Buildkite provides the compute itself instead of you supplying your own infrastructure. Linux runs $0.004 per vCPU-minute (billed by the second), and Mac M4 runs $0.02 per vCPU-minute. Self-hosted agents themselves still carry no per-minute charge — actual cost is simply your subscription fee plus whatever EC2, GCP, or bare-metal infrastructure you attach.
• Changes explicitly targeting teams moving off GitHub Actions: A recent changelog entry expanded GitHub webhook trigger coverage beyond push/PR events to a broader range of event types, and Buildkite explicitly states this is “intended to help teams migrate gradually from GitHub Actions.” On top of that, the metaData field capacity for builds/jobs jumped dramatically from 64KB to 1MB, job annotations can now be queried via the GraphQL API, and per-user rate limits were added to the REST and GraphQL APIs, so a single runaway script can no longer exhaust an entire organization’s quota.
• Updates for macOS build teams: The cluster queues page gained case-insensitive name search, and macOS support now covers Xcode 26 (Sequoia 15.6.1, Tahoe 26). One thing that remains unconfirmed: exact customer counts or market share, since Buildkite is privately held and doesn’t publish those figures.

3. Concurrency Specs & Security Benchmark Showdown

This is the section where this CI/CD tools comparison needs to be the most honest. We could not find an independent third-party quantitative benchmark that ran the same workload across all five tools under identical conditions to compare build times. Qualitative claims like “CircleCI delivers top-tier build performance” do turn up in searches, but the quantitative figures behind them — how many seconds shaved off, what percentage faster — could not be verified. So this article won’t make any “tool X is definitively the fastest” ranking claims.

The one piece of quantitative data we can cite with confidence is each tool’s concurrency spec.

[Officially documented concurrency specs as of August 2026]
CircleCI Performance   : 80x (standard environments) / 15x (macOS)
CircleCI Free          : 30x (most environments) / 1x (macOS)
Buildkite Pro          : unlimited concurrent jobs (includes 10 self-hosted agents)
Buildkite Personal     : capped at 3 concurrent jobs
GitHub Actions / GitLab CI / Jenkins : varies by plan/runner setup — no fixed number confirmed

Looking purely at concurrency specs, CircleCI Performance and Buildkite Pro have the edge simply because they publish hard numbers. GitHub Actions, GitLab CI, and Jenkins, by contrast, can scale concurrency to virtually unlimited or cap it at a single runner depending on how many runners you attach and at what spec — so the very concept of a “fixed number” doesn’t really apply to them. If your bottleneck is mobile apps with heavy matrix builds or multi-platform testing, these hard numbers make CircleCI and Buildkite worth evaluating first.

On the security front, Jenkins’ security-advisory history over the past six months is backed by concrete data.

Over six months, at least five official security advisories were issued spanning RCE-class flaws, XSS, deserialization, and credential-theft issues across the core and plugin ecosystem alike. That’s concrete data backing Jenkins’ structural trait: more plugins mean more convenience, but also a bigger attack surface. That said, jumping straight from this number to “Jenkins is less secure than the other four” needs caution — this research simply didn’t turn up this level of granular, publicly tracked advisory history for the other four tools, which doesn’t mean they have no vulnerabilities. If anything, Jenkins’ open-source nature means its public CVE tracking is unusually thorough, which arguably makes it more transparent, not less secure.

On keyless OIDC authentication, the confirmed recent changes belong to three tools: GitHub Actions (Custom Property Claims GA), GitLab (the existing id_tokens feature), and CircleCI (enhanced OIDC tokens with three new claims). No 2026 OIDC-related changes for Jenkins or Buildkite could be confirmed in this research, so we’re not making any assumptions about them in the body of this article.

4. Complete Pricing Comparison

[Minimum entry price for a paid tier — lowest to highest]
CircleCI Performance    : from $15/month (+ $15/month per additional user)
GitLab Premium          : $29/user/month (billed annually)
Buildkite Pro           : $30/month per active user
GitHub Actions          : no separate paid plan — pay-per-minute overage (from $0.006/min for Linux 2-core)
Jenkins                 : no paid plan at all (entirely free; commercial support via CloudBees etc., quoted separately)

💰 Detailed Pricing Comparison Table

There are three hidden-cost points worth flagging. First, GitHub Actions’ “free” self-hosted runners are, in a sense, conditionally free. The $0.002-per-minute platform fee announced in December 2025 was withdrawn following community backlash, but GitHub only ever described this as a “re-evaluation,” never a full retraction. Rather than pencilling this in as “permanently free” in your budget model, it’s worth building a habit of periodically checking GitHub’s official blog.

Second, GitLab’s self-hosted runners are unconditionally free, full stop. Once you hit the 400-minute/month limit on the Free plan, attaching a self-hosted runner is overwhelmingly a better deal than buying additional cloud shared-runner minutes ($10 per 1,000 minutes). All you need is a single server to attach as a runner, and you can effectively run your pipelines without limit.

Third, CircleCI’s free credits expire monthly instead of rolling over. Since you can’t carry unused credits from this month into the next, it’s safer to anticipate months with heavier build volume and buy paid credits (valid 12 months) ahead of time. It’s tempting to look at Jenkins’ $0 license fee and call it “the cheapest option,” but don’t lose sight of the fact that most of its actual total cost of ownership comes from server/agent infrastructure and the operational staff needed to keep up with security patches.

5. Final Recommendation Guide by User Type

🎯 1) Teams and open-source projects already on GitHub who want to start without adopting a separate CI tool

• Best pick: GitHub Actions
• Why: Public repositories run completely free on every runner, and private repositories also get 2,000 (Free) to 50,000 (Enterprise Cloud) minutes included every month. Your repo and your CI live in the same place, so there’s no separate integration to set up.

🎯 2) Teams already using GitLab as their SCM who also want AI-driven pipeline automation

• Best pick: GitLab CI/CD
• Why: The CI Expert Agent, which went GA in July 2026, helps build, debug, and optimize pipelines, and self-hosted runners don’t consume compute minutes on any plan, so there’s effectively no compute-budget pressure.

🎯 3) Teams bottlenecked on concurrent execution — mobile apps, multi-platform matrix builds, and the like

• Best pick: CircleCI
• Why: Performance’s 80x concurrency (15x on macOS) is the clearest concurrency number documented across all five tools. If your build queue is the bottleneck, this hard, published spec is a solid basis for a decision.

🎯 4) Large enterprises or legacy systems requiring on-prem, air-gapped environments and full customization

• Best pick: Jenkins
• Why: You get full control with zero license cost and a vast plugin ecosystem that lets you assemble virtually any workflow. That said, given five security advisories in the last six months, you need dedicated staff who can keep up with the patch cadence (12-week LTS cycle plus 4-week security backports).

🎯 5) Teams looking to move off GitHub Actions and directly control their self-hosting cost structure

• Best pick: Buildkite
• Why: The hybrid design — SaaS handles orchestration only, while actual code and build execution happens inside your own infrastructure — means source code never leaves your premises. The recent expansion of GitHub webhook triggers is also explicitly meant to smooth migration away from GitHub Actions.

🎯 6) Developers with a $0 budget who want to start a personal project right now, with no credit card

• Best pick: GitHub Actions (public repo) or Buildkite Personal
• Why: GitHub Actions is completely free on public repos with no card required, and Buildkite Personal is free forever with no expiration (limited to 1 user, 3 concurrent jobs). CircleCI Free, by contrast, caps you at 5 users and its credits expire monthly — so for a solo side project, the first two options are the smoother path.

6. Practical Tips & Common Mistakes

✅ Tip 1) Don’t assume free self-hosted GitHub Actions runners are “permanently locked in”

The $0.002-per-minute platform fee announced in December 2025 was indefinitely postponed after community backlash, but GitHub has never declared it fully cancelled. If you’re running self-hosted runners at scale, it’s safer to leave “possible reintroduction” as a variable in your budget model and build a habit of checking GitHub’s official changelog every quarter.

✅ Tip 2) If GitLab Free’s 400 minutes aren’t enough, attach a self-hosted runner right away

Buying additional shared-runner minutes costs $10 per 1,000 minutes ($0.01/minute), but self-hosted runners consume zero compute minutes on any plan. Even a single small VM gets you off the 400-minute limit and lets you run pipelines effectively without limit — so check self-hosting before you try to solve a minutes shortage with money.

✅ Tip 3) Put a note on your calendar that CircleCI’s free credits don’t roll over

The 30,000 free credits expire every month and don’t carry into the next. Purchased paid credits, on the other hand, stay valid for 12 months. If you expect a particular month to have a heavy build load, buying paid credits the month before to time your consumption is the best way to avoid waste.

✅ Tip 4) Check your Java version before upgrading Jenkins

Starting with the 2.555.x line, Java 17 support has ended and Java 21 or 25 is now required (the current LTS as of August 2026 is 2.568.1). Upgrade to the new LTS without first checking your controller’s and agents’ JDK versions, and your builds can break outright; conversely, put the upgrade off too long and you’ll miss the security patches that come after the 12-week LTS cycle.

✅ Tip 5) Start cleaning up Jenkins by removing plugins you don’t actually use

Over the last six months, individual security advisories have hit not just the core but multiple plugins — the GitHub Plugin, Pipeline: Groovy Libraries Plugin, and Gitee Plugin among them. Regularly remove plugins that are installed but not actually in use, and subscribe to the security advisories page at jenkins.io so you can react the moment a CVE is published.

✅ Tip 6) If you’re migrating to Buildkite, start with the GitHub webhook expansion changelog

Buildkite has expanded GitHub webhook trigger coverage beyond push/PR events to a broader range of event types — a change explicitly meant to help teams moving over from GitHub Actions. The metaData field capacity also grew from 64KB to 1MB, which is worth a second look if you’re designing pipelines that pass large payloads — like full test-result summaries — between stages.

7. Frequently Asked Questions (FAQ)

Q. What’s the first thing I should check in a CI/CD tools comparison?

We’d recommend starting with the three axes that come up consistently across search and review sites: (1) the free tier and build minutes (cost), (2) the cost structure of self-hosted runners (whether they’re billed per minute), and (3) security (keyless OIDC authentication, secrets management). Sort out just these three, and your candidate list among the five tools usually narrows to one or two very quickly.

Q. Is GitHub Actions going to start charging for self-hosted runners?

In December 2025, GitHub announced it would charge a $0.002-per-minute platform fee starting March 2026, but it was indefinitely postponed right after community backlash. As of August 2026 it still hasn’t taken effect and there’s no confirmed reintroduction date, so it remains free — but the official position that it “may be revisited in the future” hasn’t gone away.

Q. How much can I actually do on GitLab CI’s free plan?

The Free plan includes up to 5 seats per group, 400 CI/CD compute minutes/month, and 10GiB of storage. That 400-minute figure applies to shared runners specifically, though — attach a self-hosted runner and compute minutes aren’t deducted on any plan, so you can effectively scale without limit.

Q. How many build minutes does CircleCI’s free credit allowance cover?

Per the official page, the Free plan provides 30,000 credits/month, described as being equivalent to “up to 6,000 build minutes.” You get up to 5 active users and can start right away with no credit card required.

Q. Is Jenkins really completely free?

The license cost is genuinely $0. But that’s just the software cost — actual expenses come 100% from server/agent infrastructure and the staff needed to run and patch it. If you need commercial support, you’ll need a separate contract with a third-party vendor like CloudBees, and specific 2026 pricing isn’t public since it’s quoted privately.

Q. What’s the difference between Buildkite and GitHub Actions?

The biggest difference is execution architecture. Buildkite’s SaaS handles orchestration only (scheduling, UI, API), while actual build execution runs on self-hosted agents inside your own infrastructure, so source code never leaves your premises. The Personal plan is free forever with no card required, and recent changelogs explicitly add features aimed at helping teams migrate gradually from GitHub Actions.

Q. What’s the market share breakdown across these CI/CD tools?

According to JetBrains’ “State of Developer Ecosystem 2025” survey (published October 2025, as cited in a March 2026 TeamCity blog post), organizational adoption stood at 33% for GitHub Actions, 28% for Jenkins, and 19% for GitLab CI, with CircleCI and Buildkite figures not disclosed in that survey. For personal projects, the figures were 39% for GitHub Actions, 13% for Jenkins, and 10% for GitLab CI. Keep in mind this is 2025 survey data — no independent 2026 re-survey figures have been confirmed.

Q. Which of the five CI/CD tools is fastest?

This research couldn’t find an independent quantitative benchmark that ran the same workload across all five tools under identical conditions. The only verifiable quantitative data available is concurrency specs (CircleCI Performance at 80x, Buildkite Pro unlimited), so it’s safer not to take vendor marketing claims about being “the fastest” at face value.

8. Conclusion: The Practical Takeaway from This 2026 CI/CD Tools Comparison

As of August 2026, the conclusion of this CI/CD tools comparison is that there’s no single right answer — it comes down to where your repository lives and whether self-hosting is viable for you. If your code is already on GitHub, there’s little reason to look elsewhere; if your team is on GitLab, the benefit of getting the CI Expert Agent bundled into a single platform is substantial. That said, two facts need to factor into your budget and security planning: GitHub Actions’ free self-hosted runners came with a fee announcement that was later walked back (not cancelled outright), and Jenkins has racked up five security advisories in the last six months.

In practice, this framework holds up well: CircleCI if you need hard concurrency numbers, GitLab CI or Buildkite if you want firm control over self-hosting costs, Jenkins if you need full customization and on-prem deployment, and GitHub Actions if you want to start right now with zero setup. If you’re also weighing where your CI/CD pipeline ultimately deploys to, our Docker, Kubernetes, and other container tools comparison and Vercel, Netlify, and web hosting PaaS comparison articles are worth reading alongside this one.

[Summary: the final recommendation for your situation]

GitHub-based teams, open-source projects
  → GitHub Actions (Public fully free, Private Free 2,000 min/month)

Already on GitLab, want AI pipeline automation too
  → GitLab CI/CD (self-hosted runners deduct 0 minutes, CI Expert Agent GA)

Bottlenecked on concurrent execution, like mobile/matrix builds
  → CircleCI (Performance concurrency 80x / macOS 15x)

On-prem, air-gapped, need full customization
  → Jenkins (license $0, but requires staff for security patching)

Migrating off GitHub Actions, want direct control of self-hosting costs
  → Buildkite (Personal free forever, Pro $30/month/user)

Every number in this CI/CD tools comparison was compiled from official pricing pages and release notes, but pricing is an area that can change again at any time. The safest habit before signing any contract is always to double-check each vendor’s current official pricing page one more time.