Cirrus CI stops running jobs on June 1, 2026. Cirrus Labs announced they're joining OpenAI's Agent Infrastructure team, and there's no official migration path. If you have .cirrus.yml files in your repos, you've got eight weeks to move.
The best place to move them is Bitrise Build Hub:
- 54% faster Mac builds. 14 cores, 54 GB RAM M4 Pro industry leading machine specs.
- 31% faster Android builds. Best price performance with the biggest selection of x86 Linux machine types.
- Same-day Xcode. Beta and GA within 24 hours of Apple's release.
- 99.9% uptime SLA. We own the hardware.
- 100GB co-located cache. Same rack as your runners. Up to 90% build time reduction.
- Vertically integrated DevOps platform: with Xcode, Bazel, Gradle cache solutions along with mobile Release Management automation supporting CodePush.
- One-line migration. runs-on: bitrise-m4-pro. Done.
Start your free trial within minutes.
Nathan Hillyer, Director of Engineering at ForeFlight:
"We'd gotten used to the reliability with Bitrise and its 54 GB of RAM. Once you have that, it's very hard to go back. CI isn't just a convenience or a quality check. It's critical to how we ship."
How much faster is Bitrise Build Hub? Here's the data
macOS 54% faster:
Compiled using XcodeBenchmark with Xcode 26.3
54% faster. 54GB of unified memory means Xcode compilation doesn't hit the memory wall that causes hard-to-reproduce crashes on GitHub's 14GB runners.
Linux 31% faster:
Compiled using Thunderbird Android, Gradle assemble
31% faster with fewer cores. For the best cost-to-performance ratio, Bitrise is the only provider offering non-standard, granular Linux machine sizing: 4, 6, 8, 14, 16, 24, 32, and 48 vCPU on AMD EPYC Zen5/Zen4 servers, up to 192 vCPU for teams that genuinely need it. Usage-based vCPU pricing means your Android builds on 6 vCPU don't pay for 8.
Why not just use GitHub's runners?
As the ForeFlight quote on top indicated they tried running lighter iOS jobs on GitHub-hosted runners alongside Build Hub. On a 2 million-line codebase, they hit memory crashes almost immediately and shut it down after a week.
Before choosing Build Hub, ForeFlight evaluated AWS, MacStadium, DIY infrastructure, and other CI providers. Build Hub won on reliability and pricing. That's the difference between a runner alternative and a vertically integrated platform: we control the full stack, from the custom rack chassis to the Xcode update pipeline. When something goes wrong at 9am on release day, there's one team to call, not three vendors pointing at each other.
And with Cirrus Labs heading to OpenAI to build agent infrastructure, it's worth noting: whether your builds come from human developers or AI coding agents, our infrastructure can handle both. Build Hub already runs AI-generated code at production scale.
Beyond runners: Bitrise is the complete mobile DevOps platform
Build Hub isn't just faster runners. It's the entry point to the Bitrise Mobile DevOps Platform:
- Build Cache. Co-located in the same rack as your runners. 100GB KV storage (vs GitHub's 10GB). Xcode, Gradle, and Bazel build caching. Teams combining KV and build caching cut total build time by up to 90%.
- Release Management. Automated TestFlight delivery, phased Google Play releases, configurable approval stages, and Bitrise CodePush for React Native OTA updates. Your build passes, it ships. No manual uploads.
- Bitrise Insights. Visibility into build performance, cache hit rates, and pipeline health across your org.
No other GitHub Actions runner alternative offers this. You're not stitching three vendors together.
For OSS maintainers
Cirrus CI's free tier was home to a lot of open-source projects. Build Hub's 14-day trial is a starting point, but if you need something longer-term for an OSS project, get in touch.
Moving to Build Hub: step by step
Cirrus CI was genuinely good. Early to Apple Silicon through Tart, per-second billing, generous OSS tiers. Tart, Vetu, and Orchard are being relicensed under more permissive terms, so the community keeps those tools. But your CI workflows need a new home.
Step 1:
Start a Build Hub trial by creating a Bitrise organization and integrating to your Github account with GitHub App, see guide.
Step 2: move to GitHub Actions. For teams not already there, here's how Cirrus CI concepts map:
Not a trivial conversion for complex configs, but it's a translation, not a rearchitecture. Plan a day or two. GitHub's workflow syntax docs are solid.
Step 3: point your builds at Build Hub. Once you're in GitHub Actions, this takes minutes:
# Before (GitHub-hosted)
runs-on: macos-latest
# After (Build Hub)
runs-on: bitrise-m4-pro
Your workflow files, triggers, secrets, matrix builds: all unchanged. The Build Hub docs walk through on how to setup machine pools with the needed machine type and build environment image.
