Cirun vs terraform-aws-github-runner
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. terraform-aws-github-runner suits teams on AWS that manage infrastructure with Terraform and want GitHub Actions runners on EC2 that scale to zero. 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; terraform-aws-github-runner is an open-source project you run yourself for GitHub Actions.
Key differences between Cirun and terraform-aws-github-runner
- Type: Cirun is a product that runs runners in your own cloud account or on your own hardware; terraform-aws-github-runner is an open-source project you run yourself.
- Isolation: Cirun: Cloud VM. terraform-aws-github-runner: EC2 instance.
- Open source: terraform-aws-github-runner is open source (MIT); Cirun is not.
What they have in common
- Both run GitHub Actions jobs.
- Both document Linux, macOS and Windows runners.
- Both document arm64 runners.
- Both use a virtual machine per runner.
- Both document GPU runners.
Cirun vs terraform-aws-github-runner at a glance
| Attribute | Cirun | terraform-aws-github-runner |
|---|---|---|
| What it is | Hosted control plane that launches on-demand GitHub Actions runners in your own cloud accounts or on-prem hardware from a .cirun.yml file. | Terraform module that runs GitHub Actions runners on EC2 spot or on-demand instances, scaled by Lambda functions. |
| Type | Runs in your cloud or on your hardware | Open-source project |
| CI systems | GitHub Actions | GitHub Actions |
| Operating systems | Linux, macOS, Windows | Linux, Windows, macOS |
| Architectures | x64, arm64 | x64, arm64 |
| Isolation | 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 | Each runner is an EC2 instance in your AWS account; by default runners are reused until they are idle, and in ephemeral mode each instance takes one job with a just-in-time configuration and is then terminated |
| Fresh environment per job | Yes | Not documented |
| Hardware | Any instance type offered by the connected cloud account, or your own Linux (KVM) and Apple Silicon machines through cirun-agent. | EC2 instance types that you list, spot or on-demand, launched through the EC2 CreateFleet API; Graviton types for arm64 and EC2 Mac dedicated hosts for the experimental macOS support |
| Performance (vendor claim) | Not documented | Not documented |
| Runner sizes | Not documented | Not documented |
| Caching | 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. | Not documented |
| Docker layer caching | Yes | Not documented |
| GPU | 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. | With dynamic labels enabled, ghr-ec2 override labels can request EC2 instance requirements that include GPU accelerator types. |
| Concurrency | No plan concurrency limit is published; the on-prem agent defaults to 2 concurrent runners on macOS hosts and is unlimited by default on Linux | The scale-up Lambda stops creating instances once the configured maximum number of runners is reached; an optional pool keeps a scheduled minimum of ephemeral org-level runners |
| Static IPs | Not documented | Not documented |
| SSH into running jobs | Not documented | Yes |
| Pricing | 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. | Free and open source; you pay for the infrastructure it runs on. |
| Free tier | Free for public repositories, with unlimited runners, ARM and GPU runners on all supported cloud providers | Not documented |
| Open source | No | Yes (MIT) |
| Self-host / your cloud | Not documented / Yes | Yes / Yes |
| Compliance | Not documented | Not documented |
| Regions | Any region of the connected cloud account, set per runner in .cirun.yml | Not documented |
| Company headquarters | London, England, United Kingdom | Not documented |
| Good fit for | 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 | Teams on AWS that manage infrastructure with Terraform and want GitHub Actions runners on EC2 that scale to zero |
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 terraform-aws-github-runner
- You want runners on EC2 spot instances that scale down to zero when no workflows are active
- You manage AWS with Terraform and want the whole runner stack defined as a module
- You need Linux x64, Linux arm64 and Windows runners from one deployment through the multi-runner module
- You want to bring your own AMI, instance types and subnets
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
- terraform-aws-github-runner: Enterprise-level runners are not supported; runners are registered at organization or repository level
- terraform-aws-github-runner: The maintainers describe the project as maintained on a best-effort basis
Run your slowest workflow on both before deciding. See the full Cirun profile and terraform-aws-github-runner profile, or the complete comparison.
More comparisons
- Actuated vs Cirun
- Cirun vs GARM (GitHub Actions Runner Manager)
- Cirun vs HyperEnv for GitHub Actions Runner
- Cirun vs RunsOn
- Cirun vs Sprinters
- Cirun vs WarpBuild
- Cirun vs machine.dev
- Actions Runner Controller (ARC) vs terraform-aws-github-runner
- AWS CodeBuild-hosted runners vs terraform-aws-github-runner
- GARM (GitHub Actions Runner Manager) vs terraform-aws-github-runner
- HyperEnv for GitHub Actions Runner vs terraform-aws-github-runner
- RunsOn vs terraform-aws-github-runner
- terraform-aws-github-runner vs TestFlows GitHub Hetzner Runners
- ec2-github-runner vs terraform-aws-github-runner
Frequently asked questions
Is Cirun or terraform-aws-github-runner better?
What is the difference between Cirun and terraform-aws-github-runner?
Which is open source, Cirun or terraform-aws-github-runner?
How do Cirun and terraform-aws-github-runner isolate jobs?
How does Cirun pricing compare with terraform-aws-github-runner?
Do Cirun and terraform-aws-github-runner cache Docker layers?
Do Cirun and terraform-aws-github-runner offer GPU runners?
Where do Cirun and terraform-aws-github-runner runners run?
Sources
- cirun.io/
- cirun.io/pricing
- docs.cirun.io/
- docs.cirun.io/quickstart
- github.com/github-aws-runners/terraform-aws-github-runner
- github.com/github-aws-runners/terraform-aws-github-runner/releases
- github.com/github-aws-runners/terraform-aws-github-runner/blob/main/CHANGELOG.md
- github.com/github-aws-runners/terraform-aws-github-runner/blob/main/LICENSE.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 terraform-aws-github-runner. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/compare/cirun-vs-terraform-aws-github-runner/