CI/CD platforms
CI/CD platforms build, test, and ship your code automatically every time you push a change. The real decision is whether to use the pipeline built into the place where your code already lives, or an independent service, and how you want to pay: per user, per build minute, or with your own servers.
Last updated
How to choose
Start with where your code lives. GitHub, GitLab, and Bitbucket each include a pipeline tool that works with their own repositories with almost no setup; switching hosts just for CI rarely pays off.
Check the free allowance against your real usage
- Count how many minutes a typical build takes and how many builds your team runs in a month. Free allowances are small and measured differently (plain minutes, credits, or vCPU minutes).
- Check whether private repositories and your operating systems (Linux, Windows, macOS) are included.
Work out the full cost
- Some plans charge per user, others charge for compute used. A small team with long builds and a large team with short builds can reach opposite conclusions.
- Ask what extra minutes, storage, and bigger machines cost.
Decide how much you want to run yourself
- Self-hosted runners let you use your own machines and avoid per-minute charges, but you maintain them.
- Jenkins and the self-managed editions of GitHub, GitLab, and Bitbucket keep everything on your servers, which suits strict compliance needs but takes ongoing work.
Before you commit
Run one real project through your shortlist for a week and compare build times and monthly cost, rather than trusting list prices.
Answer
Browse the table. Filter to what matters.
Use the filters below, then sign in if you want to shortlist and decide with friends.
Sign in to vote, hide services and features, and reorder.
Verified: hover a cell and click its green dot for the source Estimate: no cited source
| Feature | ⠿ | ⠿ | ⠿ | ⠿ | ⠿ | ⠿ | ⠿ |
|---|---|---|---|---|---|---|---|
|
⠿
Free plan build minutes
|
Doesn't apply
|
||||||
|
⠿
Entry paid plan price
|
Doesn't apply
|
||||||
|
⠿
Free plan users
|
Doesn't apply
|
||||||
|
⠿
Self hosted runners
|
|
||||||
|
⠿
Whole platform self hostable
|
|
||||||
|
⠿
Open source offer
|
Why these features matter
-
Free plan build minutes (min)
Shows how far you can get before paying. Minutes are not equal across tools, so check the qualifier.
-
Entry paid plan price ($/month)
Per-user and usage-based prices scale differently, so the basis matters as much as the number.
-
Free plan users
A free plan capped at five users is a trial for most teams.
-
Self hosted runners
Your own runners can cut per-minute costs and give access to special hardware or private networks.
-
Whole platform self hostable
Needed for strict data-residency or air-gapped environments.
-
Open source offer
Open source projects can often build free, but the amount differs a lot.
About the services
-
Azure Pipelines · Microsoft
Azure DevOps pipeline service with Microsoft-hosted or self-hosted build agents; free grants include one concurrent job.
-
GitHub Actions · GitHub
Built into GitHub, so it is the lowest-friction choice for teams already hosting code there. Free minutes are generous for public repositories; private-repo minutes are small on the free plan.
-
GitLab CI/CD · GitLab
Part of GitLab's all-in-one DevSecOps platform, with the most included minutes on paid plans. The free tier is capped at a small number of users and minutes.
-
CircleCI · CircleCI
A standalone CI/CD service that works with GitHub, GitLab, and Bitbucket. Usage-based credits and a large free allowance suit teams that want powerful machines and fast parallel builds.
-
Bitbucket Pipelines · Atlassian
Built into Bitbucket and tied closely to Jira. The cheapest per-user entry price here, but the free build allowance is the smallest.
-
Buildkite · Buildkite
Hosted control plane with agents you run yourself or Buildkite-hosted ones. Built for large, fast-growing pipelines and monorepos; costs more per user.
-
Jenkins
The long-standing free, open source automation server you host yourself. Maximum flexibility through thousands of plugins, but you run, secure, and update it.
Suggest a change
Related comparisons
-
Translation management softwareTranslation management systems (TMS) keep a team's UI strings, documents and translations in one place, with translation memory, glossaries, machine and human translation, and integrations with code and design tools. The decision is how you are charged (words, strings or keys), what a free plan covers, and how much automation and security you need.
-
Feature flag toolsFeature flag tools let engineers switch features on or off, roll them out to a slice of users, and roll them back without redeploying. This grid compares ten hosted and self-hosted tools, from open source servers to full experimentation platforms. The real trade-offs are how each one bills (per seat, per request, per user), whether you can run it yourself, and whether approvals, SSO, and A/B testing sit behind an enterprise plan.
-
Incident management softwareIncident management software wakes the right person when something breaks, gives the team one place to run the response, and records what happened so it doesn't happen again. This grid compares eight tools on what most buyers decide on: what the first paid plan really costs, whether on-call paging is included or sold separately, how well incidents run inside Slack or Teams, and how far AI goes.
-
Status page softwareStatus page software gives your customers one trusted place to see whether your service is up, read incident updates, and subscribe to alerts. Some tools are stand-alone status pages, while others bundle uptime monitoring, on-call paging, or full incident response. The trade-offs are price model (flat plan, per user, or per component), how many subscribers and team members each plan allows, and whether monitoring and paging come with it.
-
API management platformsAPI management platforms sit in front of your APIs to handle authentication, rate limits, analytics, a developer portal, and increasingly AI and MCP traffic. This grid compares seven well-known options on what you can see before talking to sales: entry price, free access, how pricing works, where it can run, and which capabilities come built in.
-
Low-code platformsLow-code platforms let teams build business apps, internal tools and workflows with visual builders and a little code instead of full software projects. The real decision is between developer-friendly tools you can self-host and enterprise platforms sold on custom quotes.