CI/CD
Each provider is profiled from its own documentation, with the source recorded against every figure. Job duration limits and whether the pipeline can run against your own hardware decide more choices here than the marketing feature list does.
| Provider | Entry paid plan | Max job duration | Self-hosted runners |
|---|---|---|---|
| Buildkite | Pro plan: $30 per active user/month. | Not documented | Self-hosted agents are the default model, not an add-on. Free plan includes up to 10 concurrent jobs; Pro plan includes 10 self-hosted agents. |
| CircleCI | Performance plan: starting at $15/month, including 30,000 free credits plus additional paid credits. | Not documented | Supported on every tier: 5 concurrent self-hosted tasks on Free, 20 on Performance, unlimited on Scale. No per-minute charge for self-hosted runner builds. |
| GitHub Actions | Not documented | Up to 6 hours of execution time per job on GitHub-hosted runners. A job that exceeds this is terminated and fails. | Free for self-hosted runners — no usage charges beyond the runner's own infrastructure cost. |
Which to consider
Buildkite
Teams that already run their own compute and want a CI product built around that from the start, rather than one that treats self-hosting as an escape hatch from a hosted-minutes model.
CircleCI
Teams running mostly on self-hosted runners, where build-minute cost disappears entirely and the credits system only meters users and premium features.
GitHub Actions
Repos already on GitHub — no separate CI product to wire up, and self-hosted runners cost nothing to use beyond the hardware itself.
CI/CD
BuildkiteCI/CD built around self-hosted agents by default, with hosted agents available billed per vCPU-minute.CircleCIDedicated CI/CD platform billed on a credits system, with unmetered self-hosted runner build time.GitHub ActionsCI/CD built into GitHub, billed per minute on hosted runners and free on self-hosted ones.