CI Runnerscirunners.org
Head-to-head

Cirun vs GARM (GitHub Actions Runner Manager)

Answer in brief

Cirun suits teams and open-source projects on GitHub Actions that want on-demand runners, including GPU and ARM machines, across several clouds or on their own hardware. GARM (GitHub Actions Runner Manager) suits teams that want one self-hosted controller for GitHub or Gitea runners spread over several clouds or private infrastructure. Cirun is a product that runs runners in your own cloud account or on your own hardware for GitHub Actions, priced at $29/mo (3 private repos) + cloud cost; GARM (GitHub Actions Runner Manager) is an open-source project you run yourself for GitHub Actions and Forgejo/Gitea Actions.

By the CI Runners editors · Updated

Key differences between Cirun and GARM (GitHub Actions Runner Manager)

  • Type: Cirun is a product that runs runners in your own cloud account or on your own hardware; GARM (GitHub Actions Runner Manager) is an open-source project you run yourself.
  • CI systems: Only GARM (GitHub Actions Runner Manager) documents Forgejo/Gitea Actions.
  • Operating systems: Only Cirun documents macOS.
  • Isolation: Cirun: Cloud VM. GARM (GitHub Actions Runner Manager): Depends on provider.
  • Open source: GARM (GitHub Actions Runner Manager) is open source (Apache-2.0); Cirun is not.
  • Company headquarters: Aktech Labs is based in London, United Kingdom; Cloudbase Solutions is based in Timișoara, Romania.

What they have in common

  • Both run GitHub Actions jobs.
  • Both document Linux and Windows runners.
  • Both document arm64 runners.
  • Both give every job a fresh environment.

Cirun vs GARM (GitHub Actions Runner Manager) at a glance

AttributeCirunGARM (GitHub Actions Runner Manager)
What it isHosted control plane that launches on-demand GitHub Actions runners in your own cloud accounts or on-prem hardware from a .cirun.yml file.Self-hosted runner manager for GitHub and Gitea Actions that creates ephemeral runners across clouds through provider plugins.
TypeRuns in your cloud or on your hardwareOpen-source project
CI systemsGitHub ActionsGitHub Actions, Forgejo/Gitea Actions
Operating systemsLinux, macOS, WindowsLinux, Windows
Architecturesx64, arm64x64, arm64
IsolationEach job runs in a fresh virtual machine created in your cloud account and destroyed after the job; on-prem runners use cloud-hypervisor VMs on Linux, Apple Virtualization VMs on macOS or opt-in Docker containersRunners are instances created by an external provider (cloud VMs, LXD or Incus instances, or Kubernetes pods), so the boundary depends on the provider you choose
Fresh environment per jobYesYes
HardwareAny instance type offered by the connected cloud account, or your own Linux (KVM) and Apple Silicon machines through cirun-agent.Not documented
Performance (vendor claim)Not documentedNot documented
Runner sizesNot documentedNot documented
CachingSetting extra_config.cache: true redirects actions/cache to an S3 bucket in your own AWS account with no Cirun size limit (automatic mode covers Linux runners on AWS); a separate cirunlabs/cache/s3 action works with any S3-compatible store. Docker Buildx type=gha caching through the same proxy is documented.Not documented
Docker layer cachingYesNot documented
GPUGPU runners are included in every plan; the docs show an NVIDIA Tesla T4 attached to a Google Cloud instance and list Vast.ai as a provider, with GPU cost billed by your cloud.Not documented
ConcurrencyNo plan concurrency limit is published; the on-prem agent defaults to 2 concurrent runners on macOS hosts and is unlimited by default on LinuxEach pool or scale set has a maximum number of runners and a minimum number of idle runners
Static IPsNot documentedNot documented
SSH into running jobsNot documentedYes
PricingOpen Source: $0 for unlimited public repositories. Startup: $29 per month for 3 private repositories. Business: $79 per month for 10 private repositories. Enterprise: custom pricing. Compute is billed by your own cloud provider.Free and open source; you pay for the infrastructure it runs on.
Free tierFree for public repositories, with unlimited runners, ARM and GPU runners on all supported cloud providersNot documented
Open sourceNoYes (Apache-2.0)
Self-host / your cloudNot documented / YesYes / Yes
ComplianceNot documentedNot documented
RegionsAny region of the connected cloud account, set per runner in .cirun.ymlNot documented
Company headquartersLondon, England, United KingdomTimișoara, Romania
Good fit forTeams and open-source projects on GitHub Actions that want on-demand runners, including GPU and ARM machines, across several clouds or on their own hardwareTeams that want one self-hosted controller for GitHub or Gitea runners spread over several clouds or private infrastructure

Verified November 22, 2026 from each provider’s documentation. Performance figures are vendor claims, not our measurements.

Which should you choose?

Reasons to choose Cirun

  • You want runners in your own account on AWS, Google Cloud, Azure, DigitalOcean, Oracle Cloud, OpenStack or other listed providers from one configuration file
  • You need GPU or ARM runners, which every plan includes
  • You maintain public repositories, where the Open Source plan is free
  • You want to register your own Linux or Apple Silicon machines as an on-prem runner pool

Reasons to choose GARM (GitHub Actions Runner Manager)

  • You want one controller that manages runners in several clouds and on private infrastructure at once
  • You want a single binary with an embedded SQLite database instead of an external database or message broker
  • You run Gitea or GitHub Enterprise Server as well as github.com
  • You want to choose between webhook-driven pools and GitHub runner scale sets

Trade-offs to check first

  • Cirun: Automatic S3 caching currently covers Linux runners on AWS only
  • Cirun: The AWS setup documents an IAM user access key with EC2 admin permissions entered in the Cirun dashboard
  • GARM (GitHub Actions Runner Manager): Pools rely on workflow_job webhooks, so the forge must be able to reach GARM; the release notes cite lost webhook deliveries as a risk that scale sets avoid
  • GARM (GitHub Actions Runner Manager): Scale set labels can only be set at creation time and cannot be updated afterwards

Run your slowest workflow on both before deciding. See the full Cirun profile and GARM (GitHub Actions Runner Manager) profile, or the complete comparison.

More comparisons

Frequently asked questions

Is Cirun or GARM (GitHub Actions Runner Manager) better?
Neither is better for every pipeline. Cirun suits teams and open-source projects on GitHub Actions that want on-demand runners, including GPU and ARM machines, across several clouds or on their own hardware. GARM (GitHub Actions Runner Manager) suits teams that want one self-hosted controller for GitHub or Gitea runners spread over several clouds or private infrastructure.
What is the difference between Cirun and GARM (GitHub Actions Runner Manager)?
Cirun is a product that runs runners in your own cloud account or on your own hardware; GARM (GitHub Actions Runner Manager) is an open-source project you run yourself. Only GARM (GitHub Actions Runner Manager) documents Forgejo/Gitea Actions. Only Cirun documents macOS. Isolation is Cloud VM on Cirun and Depends on provider on GARM (GitHub Actions Runner Manager). GARM (GitHub Actions Runner Manager) is open source (Apache-2.0); Cirun is not.
Which is open source, Cirun or GARM (GitHub Actions Runner Manager)?
Cirun is not open source; GARM (GitHub Actions Runner Manager) is open source (Apache-2.0).
How do Cirun and GARM (GitHub Actions Runner Manager) isolate jobs?
Cirun: Each job runs in a fresh virtual machine created in your cloud account and destroyed after the job; on-prem runners use cloud-hypervisor VMs on Linux, Apple Virtualization VMs on macOS or opt-in Docker containers. GARM (GitHub Actions Runner Manager): Runners are instances created by an external provider (cloud VMs, LXD or Incus instances, or Kubernetes pods), so the boundary depends on the provider you choose.
How does Cirun pricing compare with GARM (GitHub Actions Runner Manager)?
Cirun: Open Source: $0 for unlimited public repositories. Startup: $29 per month for 3 private repositories. Business: $79 per month for 10 private repositories. Enterprise: custom pricing. Compute is billed by your own cloud provider. GARM (GitHub Actions Runner Manager): Free and open source; you pay for the infrastructure it runs on. Rates change, so check the Cirun and GARM (GitHub Actions Runner Manager) pricing pages before deciding.
Do Cirun and GARM (GitHub Actions Runner Manager) cache Docker layers?
Cirun: Setting extra_config.cache: true redirects actions/cache to an S3 bucket in your own AWS account with no Cirun size limit (automatic mode covers Linux runners on AWS); a separate cirunlabs/cache/s3 action works with any S3-compatible store. Docker Buildx type=gha caching through the same proxy is documented. GARM (GitHub Actions Runner Manager): Docker layer caching is not documented.
Do Cirun and GARM (GitHub Actions Runner Manager) offer GPU runners?
Cirun: GPU runners are included in every plan; the docs show an NVIDIA Tesla T4 attached to a Google Cloud instance and list Vast.ai as a provider, with GPU cost billed by your cloud. GARM (GitHub Actions Runner Manager): Not documented.
Where do Cirun and GARM (GitHub Actions Runner Manager) runners run?
Cirun is a product that runs runners in your own cloud account or on your own hardware (AWS, Google Cloud, Azure, Hetzner, DigitalOcean, Oracle Cloud, OpenStack, Vast.ai and Bare metal). GARM (GitHub Actions Runner Manager) is an open-source project you run yourself (AWS, Azure, Google Cloud, Oracle Cloud, OpenStack, Kubernetes, LXD, Incus, CloudStack and Akamai/Linode).

Sources

  1. cirun.io/
  2. cirun.io/pricing
  3. docs.cirun.io/
  4. docs.cirun.io/quickstart
  5. github.com/cloudbase/garm
  6. github.com/cloudbase/garm/releases
  7. github.com/cloudbase/garm/releases/tag/v0.2.0
  8. github.com/cloudbase/garm/blob/main/doc/pools-and-scaling.md

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). Cirun vs GARM (GitHub Actions Runner Manager). cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/compare/cirun-vs-garm/