Buildkite review

Buildkite is a CI/CD platform for building, testing, and delivering software through configurable workflows. Teams define pipelines with steps, triggers, conditions, and other controls, then run jobs on agents that can use self-hosted infrastructure or Buildkite-hosted Mac, Linux, and Windows machines.

The product is built around flexibility: teams can run work in parallel, optimize test execution, manage packages, and connect AI workflows to LLM providers. Buildkite also offers an MCP server, according to the published product information. The platform can therefore cover more than build-and-test jobs, but the exact services and usage limits depend on the plan.

The pricing page lists a free plan and a 30-day free trial. Pro is listed at $30 per active user per month; Enterprise pricing is custom. That makes the plan caps worth checking before moving a large or busy CI setup.

Buildkite’s main advantage is flexibility over where jobs run. Teams can use self-hosted agents or hosted Mac, Linux, and Windows machines, rather than being limited to a single execution environment. That can suit workflows with specific infrastructure needs, though the cost depends on how agents are provisioned and used.

Pipeline controls include dynamic pipelines, wait and block steps, triggers, and conditional logic. The product also supports parallel builds and test optimization features for splitting tests, checking performance, and isolating flaky tests in real time. Package registries and programmable AI workflows broaden its scope beyond basic CI jobs.

The plan structure gives smaller teams a way to start without paying: the listed Free Plan allows up to 5 users, 10 concurrent jobs, 2,000 Linux vCPU minutes, 250,000 test executions, and 50GB of artifact storage per month. Pro raises those allowances to 50 users, 250 concurrent agents, 4,000 Linux AMD64 vCPU minutes, 1 million test executions, and 250GB of artifact storage. The pricing page says 10 agents are included on Pro.

The allowances are not unlimited just because Buildkite supports parallel builds. The listed Free Plan stops at 10 concurrent jobs, 2,000 Linux vCPU minutes, and 250,000 test executions per month. Pro has higher caps, but teams can still incur overages: additional self-hosted agents cost $3.50 per agent per month after the 10 included, extra artifact storage is $0.05 per GB-month, and downloads are $0.10 per GB. Test executions beyond 1 million cost $15 per million. Hosted-agent minute rates are not published on the vendor's site.

Pro costs $30 per active user per month, with no annual rate published. Enterprise is custom-priced, has a 30-user minimum, and lists custom usage and rate limits. That makes total cost harder to forecast from the headline price alone.

There is also some confusion in user discussions about free access changing over time. One Reddit thread describes a free Personal plan with 500 hosted-agent minutes, while the pricing snapshot lists a Free Plan with different allowances. Confirm the current offer before budgeting around either.

Buildkite’s Free plan costs $0 and covers up to 5 users, 10 concurrent jobs, 2,000 Linux vCPU minutes and 250,000 test executions per month, plus 50GB of artifact storage. The listed 30-day free trial is separate; the published pricing details don’t say which plan it applies to.

Pro is $30 per active user per month, with no annual rate published. It raises the caps to 50 users, 250 concurrent agents (10 included), 4,000 Linux AMD64 vCPU minutes, 1 million test executions and 250GB of artifact storage. That’s a meaningful step up from Free, but usage charges can add to the bill: extra self-hosted agents cost $3.50 each per month, storage overage is $0.05/GB-month, downloads cost $0.10/GB, and excess test executions cost $15 per million. Hosted-agent minute rates aren’t listed.

Enterprise pricing is custom, with a 30-user minimum; payment can be annual or by invoice. Check caps and overages before switching.

Plan for pipeline work, not just an account change. Buildkite supports dynamic pipelines, wait and block steps, triggers and conditional logic, so teams moving existing CI should map their current workflow logic and agent requirements to those features. The published materials don’t specify migration tooling or the effort involved; expect the amount of pipeline rewriting to depend on your setup.

Buildkite can run agents on self-hosted infrastructure or hosted Mac, Linux and Windows machines. That flexibility may help preserve an existing compute setup, but switching providers can still mean changing agent configuration and validating builds and tests.

Before leaving, check what you need to take with you. Enterprise includes one year of build retention and historical export, with custom artifact retention. The published details don’t state what export options other plans include, or whether that export covers pipeline configuration and artifacts. We also weren’t given Reddit posts or comments, so we can’t reliably summarize user-reported reasons for leaving.