| Migrating from Cirrus Runners to Blaze

Cirrus Labs announced on 7 April 2026 that the team is joining OpenAI. Cirrus CI stopped running jobs on 1 June 2026. Cirrus Runners no longer accepts new customers and supports existing customers through their existing contract periods.

Blaze works the way Cirrus Runners does: a fixed price per concurrent runner, unlimited minutes, and a one-line change in your workflow. It also runs macOS and Linux VMs on Tart with Orchard, the VM tooling Cirrus Labs built and open-sourced.

What maps

Cirrus sizes its runners in fractions of a $150 monthly runner. Blaze sizes them in units: macOS starts at €125 per unit per month; Linux costs €29 for the first unit and €28 each for units 2–5.

Cirrus Runners
Blaze
Blaze units
ghcr.io/cirruslabs/macos-runner:tahoe M4 Pro, 4 vCPU, 16 GB, 3 latest Xcodes, counts as 1.00 runner
blaze/macos-26 4 vCPU, 12 GB VM on Apple M2, macOS 26.3 Tahoe, Xcode 26.2
1
ghcr.io/cirruslabs/macos-runner:tahoe-xl 8 vCPU, 32 GB, counts as 2.00 runners
blaze/macos-26:lg 8 vCPU, 24 GB
2
ghcr.io/cirruslabs/ubuntu-runner-arm64:24.04-sm 2 vCPU, 6 GB, counts as 0.25 runner
blaze/ubuntu-24.04 2 vCPU, 6 GB
1
ghcr.io/cirruslabs/ubuntu-runner-arm64:24.04-md 4 vCPU, 12 GB, counts as 0.50 runner
blaze/ubuntu-24.04:lg 4 vCPU, 12 GB
2
ghcr.io/cirruslabs/ubuntu-runner-arm64:24.04 8 vCPU, 24 GB, counts as 1.00 runner
blaze/compute/ubuntu-24.04:lg 8 vCPU, 24 GB
4
Cirrus amd64 runners (any size) xs/sm/md/default/xl: 2/4/8/16/32 vCPU, counts as 0.125/0.25/0.50/1.00/2.00 runners
x86_64 on request
–
ghcr.io/cirruslabs/ubuntu-runner-amd64-gpu:24.04 Nvidia RTX 4000, counts as 2.00 runners
Not offered yet
–

Worked out per month: a Cirrus macOS runner is $150; Blaze is €125 with 4 GB less memory and an Apple M2 instead of an M4 Pro. A Cirrus default ARM64 Linux runner is $150; the matching Blaze size is four units, €113. A Cirrus medium ARM64 Linux runner is half a runner, $75; the matching Blaze size is two units, €57. Prices checked on 27 October 2026 against cirrus-runners.app and runblaze.dev/pricing.

How to switch

  1. Install the Blaze GitHub App on your organisation.

  2. Replace the runs-on line.

    before:
runs-on: ghcr.io/cirruslabs/macos-runner:tahoe
after:
runs-on: blaze/macos-26
  3. If a job used xcodes to select a version, drop that step and choose the image with that Xcode instead.
  4. Keep actions/cache and your secrets as they are; both live in GitHub.
  5. Run the workflow, then let the Cirrus contract lapse.

What you keep

  • * A fixed price per concurrent runner and unlimited minutes.
  • * The same concurrency trade-off: jobs beyond the runners you pay for wait their turn, as they did on Cirrus. Add a runner when the wait matters.
  • * GitHub Actions as it is. One runs-on line changes; workflows, secrets and actions/cache stay where they are.
  • * A fresh VM for every job, on Tart and Orchard, the stack Cirrus Labs built.
  • * Linux runners on the same model from €29 per unit, and 300 free macOS minutes plus 1000 free Linux minutes to try it before you move anything.
  • * Support by email from the Blaze team.

What you give up

  • * The M4 Pro and 16 GB per 4 vCPU. Blaze macOS jobs run in 4-core, 12 GB VMs on Apple M2 Macs.
  • * Three Xcodes per image and the xcodes tool. Blaze ships one Xcode per macOS image; pick the image that carries the version you build with.
  • * The Omni Cache sidecar. On Blaze, actions/cache talks to GitHub directly.
  • * GPU runners, x86_64 as a standard option (on request only at support@runblaze.dev), low-priority jobs, concurrency groups and the 10 GB of per-runner storage.

Cirrus has announced no shutdown date for Runners; existing customers are supported through their existing contract periods. If something in your workflow only worked on Cirrus, write to us and we will tell you plainly whether Blaze covers it.

Start with 300 free macOS minutes + 1000 Linux minutes