Softwr

Developer Tools · head to head

Buildkite vs Split

Buildkite logo

Buildkite

Developer Tools

CI/CD pipelines that run on your own compute

From
Free
Free plan
Yes
Split logo

Split

Testing

Feature flags tied to a metrics pipeline that attributes production impact to each release, now Harness FME

From
On request
Free plan
No

The short version

  • Buildkite is a CI/CD platform for build, test and deploy pipelines.
  • Buildkite starts at $30/mo; Split prices on request.
  • Where Buildkite falls short: free plan caps at 5 users and 10 concurrent jobs, with 2,000 Linux vCPU minutes per month and 30 day build retention.
  • Prices and features on this page were last checked on 20 November 2026.

How do Buildkite and Split differ?

Buildkite and Split differ on starting price (Free against On request), pricing model (Subscription against Quote) and free tier (Yes against No). Only the attributes on which Buildkite and Split actually diverge.

Attributes where Buildkite and Split differ
AttributeBuildkiteSplit
Starting priceFreeOn request
Pricing modelSubscriptionQuote
Free tierYesNo
PlatformsWebWeb, API, iOS, Android, Windows
CategoryDeveloper ToolsTesting

Not yet recorded: founded for Split.

Which features does each one have?

They share no listed features; 8 only for Split. Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Buildkite

Nothing recorded that Split does not also cover.

Only in Split

  • Feature flags with targeting
  • Metrics impact engine
  • Guardrail metrics
  • Statistical significance testing
  • Event ingestion
  • SDKs and streaming updates
  • Audit and approvals
  • Harness platform integration

What is each one used for?

Buildkite is most often brought in for CI/CD pipeline automation. The jobs each tool is most often brought in to do.

Buildkite

  • CI/CD pipeline automationnot Split
  • Test execution at scalenot Split
  • Deployment automationnot Split

Split

  • A product organisation that wants every release measured against conversion and latency by default, not only deliberate experimentsnot Buildkite
  • Running A/B tests with real statistical significance rather than comparing two dashboard linesnot Buildkite
  • Catching a regression at five per cent rollout because a guardrail metric fires before the change reaches everyonenot Buildkite
  • A team already committed to Harness for CI and CD that wants flags in the same platform and contractnot Buildkite

Where do Buildkite and Split fall short?

Buildkite's most cited limit: free plan caps at 5 users and 10 concurrent jobs, with 2,000 Linux vCPU minutes per month and 30 day build retention. Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Buildkite

  • Free plan caps at 5 users and 10 concurrent jobs, with 2,000 Linux vCPU minutes per month and 30 day build retention
  • Pro plan is $30 per active user per month, capped at 50 users, with only 10 of the up to 250 concurrent agents included before extra usage
  • Enterprise plan enforces a 30 user minimum even though pricing itself is custom
  • Hosted compute beyond included minutes is metered at $0.004 per vCPU minute on Linux and $0.02 per vCPU minute on Mac

Split

  • Split is now a module of the Harness platform and split.io redirects to harness.io, so buying it means entering a Harness commercial relationship rather than a standalone flag vendor contract
  • Harness no longer publishes per-module prices, so an organisation that wants only feature management cannot get a list price and must negotiate a module out of a platform bundle
  • The measurement engine needs traffic volume to reach significance, so a product with modest usage gets flags with an experimentation layer it will rarely be able to conclude anything from
  • Metric attribution depends on correctly instrumented events flowing into Split, which is an integration project in its own right; without it you have paid for an experimentation platform and are using it as a flag switch
  • As part of a larger DevOps suite the roadmap now competes with CI, CD, security and cloud cost modules for attention, so feature management is no longer the company’s single focus the way it was as an independent product

How much do Buildkite and Split cost?

Buildkite has a free plan, with paid plans from $30/mo; Split is priced on request. Plan by plan below, from each vendor's own pricing page.

Buildkite

Free
  • FreeFree
    • Up to 5 users
    • 10 concurrent jobs
    • 2000 Linux vCPU minutes monthly
  • Pro$30/mo
    • Up to 50 users
    • 250 concurrent agents (10 included)
    • 4000 Linux vCPU minutes monthly
  • EnterpriseOn request
    • Unlimited users (30 minimum)
    • Custom usage limits
    • Full platform access

Split

On request
  • Harness FreeFree
    • Harness Open Source and community support
    • Intended for individuals and small teams
    • Feature management capability limited at this tier
  • Harness EssentialsOn request
    • Bundled DevOps modules including CI, CD, IaC and security testing
    • Standard support
    • Pricing requires contacting sales
  • Harness EnterpriseOn request
    • Mix and match from 15 or more modules including Feature Management and Experimentation
    • Premier support with a dedicated account manager
    • Higher pipeline concurrency and organisation limits

Which should you pick?

Choose Buildkite if

  • You want to start without paying.

Choose Split if

  • You need feature flags with targeting.
  • You work on Web, API, iOS, Android, Windows.
  • You also want metrics impact engine.

Questions people ask

Is Buildkite or Split better?
Neither clearly leads. Buildkite starts at Free and Split at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Buildkite or Split?
Buildkite has a free tier; the other does not. Paid plans start at Free for Buildkite and On request for Split.
Does Buildkite or Split run on more platforms?
Buildkite runs on Web. Split runs on Web, API, iOS, Android, Windows.
Can I use Buildkite for free?
Yes. Buildkite has a free tier, so you can try it without paying. Split starts at On request.
What is Buildkite best used for?
Buildkite is most often used for ci/cd pipeline automation, test execution at scale, deployment automation. Of those, ci/cd pipeline automation and test execution at scale are not what Split is typically brought in for.
What can Buildkite do that Split cannot?
Split covers Feature flags with targeting, Metrics impact engine, Guardrail metrics, Statistical significance testing.

Answered from the vendors’ own pages

Buildkite: Can I use Buildkite without paying?

Yes, Buildkite offers a free plan that includes up to 5 users, 10 concurrent jobs, 2000 Linux vCPU minutes monthly, and 250k test executions per month at no cost.

Source
Split: Is Split still called Split?

It is now sold as Harness Feature Management and Experimentation after the Harness acquisition, and split.io redirects to harness.io.

Buildkite: What happens if I exceed my included compute minutes on Buildkite?

Hosted agent compute is charged separately at $0.004 per Linux vCPU minute and $0.02 per Mac vCPU minute, billed to the second with no minimums.

Source
Split: Can I buy just feature flags?

Not from a price list. Harness publishes bundle tiers and directs single-module buyers to sales.

Buildkite: Do I need an annual commitment for Buildkite's Pro plan?

No, Buildkite's Pro plan is billed monthly at $30 per active user with no long-term contract required. All tiers include a 30-day all-access trial.

Source
Split: What does it do that a plain flag service does not?

It attributes changes in your product metrics to specific flags with statistical significance testing and alerts on guardrail metrics.

Buildkite: What user limits apply to each Buildkite plan?

Free plan supports up to 5 users, Pro plan supports up to 50 users, and Enterprise plan provides unlimited users with a 30-user minimum.

Source
Split: Do we need a lot of traffic?

Yes. Statistical tests need volume to conclude, so low-traffic products get limited value from the measurement layer.

Share

Related pages

Other head to heads