CI Runnerscirunners.org
Alternatives

Cirrus Runners alternatives

Answer in brief

This page carries a status notice for Cirrus Runners; see below. The 8 alternatives below are grouped by kind of runner, and each says whom it suits. Start from the requirement that matters most to you: price per minute, operating systems, caching, isolation or where the runners have to run.

By the CI Runners editors · Updated

Cirrus Runners status

On April 7, 2026 Cirrus Labs announced it had entered into an agreement to join OpenAI as part of the Agent Infrastructure team. The announcement says Cirrus Labs is no longer accepting new customers for Cirrus Runners but will continue supporting the service for existing customers through their existing contract periods.

  • Closed to new customers since the April 7, 2026 announcement
  • Support is committed only through existing customers’ current contract periods
  • Linux images are not fully compatible with GitHub-hosted runner images (setup page)
  • Cache storage is 10 GB per subscribed runner, with files deleted after 100 days

Cirrus Runners alternatives, by kind

Managed runners for GitHub Actions

Third-party runners you switch to by changing the runs-on label in a workflow.

  • Blacksmith

    Managed GitHub Actions runners in Firecracker microVMs on the vendor’s own bare-metal fleet, with caches kept next to the runners.

    • Firecracker microVM
    • Ephemeral
    • arm64
    • macOS
    • Windows
    • Docker layer cache

    Whom it suits: Teams on GitHub Actions that want microVM-isolated runners on bare metal with built-in Docker layer caching and CI observability. A managed GitHub Actions runner service on vendor-owned bare metal with microVM isolation, suited to organizations that want faster hardware plus integrated caching and observability.

  • Depot GitHub Actions Runners

    Managed GitHub Actions runners on single-tenant AWS EC2 instances, connected to Depot’s cache and container build service.

    • Single-tenant EC2 instance
    • Ephemeral
    • arm64
    • macOS
    • Windows
    • Docker layer cache
    • GPU
    • BYOC

    Whom it suits: Teams on GitHub Actions that want single-tenant EC2 runners alongside a shared build cache and remote container builds from the same vendor. A managed GitHub Actions runner service built on single-tenant AWS instances, suited to teams that also want Depot’s cache and container build service.

  • Namespace

    Managed runners for GitHub Actions and Buildkite on the vendor’s own hardware, configured through profiles with persistent cache volumes.

    • Virtual machine
    • Ephemeral
    • arm64
    • macOS
    • Windows
    • Docker layer cache

    Whom it suits: Teams on GitHub Actions or Buildkite that want VM-isolated Linux, macOS and Windows runners with persistent cache volumes and fine-grained machine shapes. A managed runner platform for GitHub Actions and Buildkite on vendor-operated hardware, suited to teams that want per-job VMs, persistent cache volumes and all three operating systems.

  • WarpBuild

    Managed GitHub Actions runners in ephemeral VMs, also offered as a deployment in your own AWS, Google Cloud or Azure account.

    • Ephemeral VM
    • Ephemeral
    • arm64
    • macOS
    • Windows
    • Docker layer cache
    • BYOC

    Whom it suits: Teams on GitHub Actions that want managed runners now with the option to move the same setup into their own AWS, Google Cloud or Azure account. A managed GitHub Actions runner service with a bring-your-own-cloud option, suited to teams that want hosted runners with a path to running them in their own cloud account.

Runners from your CI platform or cloud

The first-party hosted runners of GitHub, GitLab, Buildkite and Azure, plus cloud-native runner services.

  • GitHub-hosted runners

    GitHub’s own Actions runners: a new VM per job on Linux, Windows and macOS, with larger, arm64 and GPU sizes billed per minute.

    • Fresh VM
    • Ephemeral
    • arm64
    • macOS
    • Windows
    • GPU

    Whom it suits: Teams on GitHub Actions that want runners with no setup, and public repositories that can use the free standard runners. The default runners for GitHub Actions, suited to teams that prefer zero setup and to public repositories, with larger sizes available per minute on paid plans.

macOS runners for iOS and Mac builds

Apple-silicon runners and virtualization tools for building and testing iOS and macOS apps.

  • GetMac

    Managed macOS runners on vendor-owned Apple silicon M4 hardware in Lithuania, sold as monthly plans of included compute minutes.

    • macOS VM
    • Ephemeral
    • arm64
    • macOS

    Whom it suits: Small and mid-sized teams that want low-cost Apple silicon runners for GitHub Actions, GitLab CI or Buildkite and can run in an EU data centre. GetMac is a plan-based managed macOS runner service on M4 hardware in Lithuania, suited to teams that want inexpensive ephemeral runners for GitHub Actions, GitLab CI or Buildkite.

  • Orka

    Kubernetes-based orchestration of macOS VMs on Apple silicon, run in MacStadium data centers, on AWS EC2 Mac or on your own Macs.

    • macOS VM
    • arm64
    • macOS
    • BYOC
    • Self-hostable

    Whom it suits: Teams that want a dedicated, orchestrated fleet of Macs for ephemeral macOS CI across several CI systems. Orka is commercial macOS VM orchestration for teams that want a dedicated Mac fleet, hosted by MacStadium or self-run, wired into the CI system they already use.

  • Tart

    Virtualization toolset for macOS and Linux VMs on Apple silicon, with OCI-registry images and the Orchard orchestrator for clusters of Macs.

    • Apple Virtualization VM
    • Ephemeral
    • arm64
    • macOS
    • BYOC
    • Self-hostable

    Whom it suits: Teams that run their own Apple silicon Macs and want scriptable, image-based macOS VMs for GitLab CI or Buildkite jobs. Tart is a source-available VM toolset, now maintained by OpenAI, for teams that operate their own Apple silicon Macs and want image-based ephemeral macOS VMs for CI.

Cirrus Runners vs alternatives

RunnerCI systemsRuns onDeploymentIsolationPriceLargest runnerDocker layer cacheGPUOpen sourceCompany HQ
Cirrus RunnersGitHub ActionsLinux, macOS, x64, arm64Vendor-hostedSingle-use VM$150/month per concurrent runner32 vCPU / 96 GBYesYesNoNot documented
BlacksmithGitHub ActionsLinux, macOS, Windows, x64, arm64Vendor-hostedFirecracker microVM$0.004/min32 vCPU / 128 GBYesNot documentedNoUnited States
Depot GitHub Actions RunnersGitHub ActionsLinux, macOS, Windows, x64, arm64Vendor-hostedSingle-tenant EC2 instance$0.006/min64 vCPU / 256 GBYesYesNoNot documented
GetMacGitHub Actions, GitLab CI, BuildkitemacOS, arm64Vendor-hostedmacOS VM$0.012/min (macOS M4, Developer plan)Not documentedNot documentedNot documentedNoLithuania
GitHub-hosted runnersGitHub ActionsLinux, macOS, Windows, x64, arm64Platform-hostedFresh VM$0.006/min96 vCPU / 384 GBNot documentedYesNoUnited States
NamespaceGitHub Actions, BuildkiteLinux, macOS, Windows, x64, arm64Vendor-hostedVirtual machine$0.002/min prepaid, $0.003/min overage (2 vCPU / 4 GB)64 vCPU / 512 GBYesNot documentedNoNot documented
OrkaGitHub Actions, GitLab CI, Buildkite, Jenkins, Azure Pipelines, TeamCitymacOS, arm64Your cloud or hardwaremacOS VMFrom $109/mo per hosted Mac mini (Orka by quote)Set by your infrastructureNot documentedNot documentedNoUnited States
TartGitLab CI, Buildkite, GitHub ActionsmacOS, Linux, arm64Your cloud or hardwareApple Virtualization VMNot documentedSet by your infrastructureNot documentedNot documentedNoUnited States
WarpBuildGitHub ActionsLinux, macOS, Windows, x64, arm64Vendor-hostedEphemeral VM$0.004/min32 vCPU / 128 GBYesNot documentedNoNot documented

Frequently asked questions

What are the main alternatives to Cirrus Runners?
Blacksmith, Depot GitHub Actions Runners, GetMac, GitHub-hosted runners, Namespace, Orka, Tart, WarpBuild. Which one fits depends on your pipeline; each entry above says whom it suits.
Is there an open-source alternative to Cirrus Runners?
None of the alternatives listed here is recorded as open source; see open-source and self-hosted runners.

Check before you rely on it. Products change quickly, and this page reflects public documentation as of November 22, 2026. Confirm anything that matters in the provider’s own documentation.

Cite this page

CI Runners. (2026). Cirrus Runners alternatives. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/alternatives/cirrus-runners/