company
Which CI vendors have shut down, and what it tells you
BuildJet and Cirrus CI both exited. A look at what the category consolidation actually signals for buyers.
Jess Okonkwo · Co-founder · 2026-06-30 · 7 min read
Two managed CI services wound down inside a year. If you are evaluating this category, that is a fact worth sitting with rather than skipping past.
What happened
- BuildJet announced its shutdown in February 2026 and stopped running jobs on 31 March 2026
- Cirrus CI wound down its hosted offering over a comparable period
- In both cases the migration advice pointed users back to first-party CI
The pattern
Both were priced primarily on being a faster machine. GitHub then shipped larger runners and native arm64, and the gap that justified the product narrowed. A vendor whose only differentiator is instance size is exposed to the platform's roadmap.
What to ask a vendor now
- What is your differentiator that the platform cannot simply ship? Caching architecture, data residency and BYOC are harder to copy than vCPU count.
- What does leaving cost me? If the answer is more than a line of YAML, you are buying a dependency.
- Who operates the service, and under which legal system?
Your next build could be twice as fast, at half the price
Start free. Migrating away is the same one line, and we publish that diff too.
Related
CI when your teammates are agentsAI coding agents push far more often than humans. Here is how that changes pipeline design and cost control.Why we publish instructions for leavingEvery migration page on this site includes the diff to migrate back off us. Here is the reasoning.What we learned running a million CI jobsQueue time, cache behaviour, right-sizing and the failure modes that only appear at scale.Stop retrying flaky testsAutomatic retries convert a real bug into an intermittent one, and train your team to distrust every failure.