Cirun vs HyperEnv for GitHub Actions 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. HyperEnv for GitHub Actions Runner suits teams that buy through AWS Marketplace and want GitHub Actions runners that run entirely inside their AWS account for a metered per-minute fee. 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; HyperEnv for GitHub Actions Runner is a product that runs runners in your own cloud account or on your own hardware for GitHub Actions, priced at $0.002/min fee + AWS cost.
Key differences between Cirun and HyperEnv for GitHub Actions Runner
- Operating systems: Only Cirun documents macOS and Windows.
- Architectures: Only Cirun documents arm64.
- Isolation: Cirun: Cloud VM. HyperEnv for GitHub Actions Runner: EC2 instance.
- Published price: $29/mo (3 private repos) + cloud cost (Cirun) versus $0.002/min fee + AWS cost (HyperEnv for GitHub Actions Runner).
- Company headquarters: Aktech Labs is based in London, United Kingdom; widdix GmbH is based in Lichtenwald, Germany.
What they have in common
- Both are products that run runners in your own cloud account or on your own hardware.
- Both run GitHub Actions jobs.
- Both document Linux runners.
- Both use a virtual machine per runner.
- Both give every job a fresh environment.
- Neither is open source.
- Both document GPU runners.
Cirun vs HyperEnv for GitHub Actions Runner at a glance
| Attribute | Cirun | HyperEnv for GitHub Actions 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. | AWS Marketplace product that runs each GitHub Actions job on an ephemeral EC2 instance, deployed entirely inside your own AWS account. |
| Type | Runs in your cloud or on your hardware | Runs in your cloud or on your hardware |
| CI systems | GitHub Actions | GitHub Actions |
| Operating systems | Linux, macOS, Windows | Linux |
| Architectures | x64, arm64 | x64 |
| 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 job gets a new EC2 instance that registers an ephemeral GitHub runner and is terminated after the job completes or times out |
| Fresh environment per job | Yes | Yes |
| Hardware | Any instance type offered by the connected cloud account, or your own Linux (KVM) and Apple Silicon machines through cirun-agent. | A fixed list of EC2 instance families: t3, m5, m6i, m7i, m7i-flex, m7a and g4dn. |
| Performance (vendor claim) | Not documented | Not documented |
| Runner sizes | Not documented | Up to 192 vCPUs, 768 GiB memory and a 16 TB disk volume; the default instance type is m6i.large |
| 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. | An S3-backed cache in your account is enabled by default (S3Cache parameter, 30-day expiration); it is not supported for GitHub Enterprise Server. |
| 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. | g4dn instance types (xlarge to 16xlarge) with an NVIDIA T4 GPU are supported; the HyperEnv fee stays $0.002 per build minute plus the AWS instance cost. |
| 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 | Not documented |
| 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. | $0.002 per build minute, billed through AWS Marketplace and charged only while a job runs. AWS infrastructure such as EC2, EBS and CloudWatch is billed separately to your account. |
| Free tier | Free for public repositories, with unlimited runners, ARM and GPU runners on all supported cloud providers | Not documented |
| Open source | No | No |
| Self-host / your cloud | Not documented / Yes | Yes / Yes |
| Compliance | Not documented | ISO 27001 (widdix GmbH) |
| Regions | Any region of the connected cloud account, set per runner in .cirun.yml | Not documented |
| Company headquarters | London, England, United Kingdom | Lichtenwald, Baden-Württemberg, Germany |
| 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 that buy through AWS Marketplace and want GitHub Actions runners that run entirely inside their AWS account for a metered per-minute fee |
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 HyperEnv for GitHub Actions Runner
- You want the runner control plane and every runner inside your own AWS account with no external dependencies
- You prefer to buy and pay through AWS Marketplace on a metered per-build-minute rate
- You need runners with access to private networks in an existing VPC
- You use GitHub Enterprise Server, which the product supports
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
- HyperEnv for GitHub Actions Runner: Runners are based on Ubuntu 22.04 only, per the FAQ; other operating systems are by request
- HyperEnv for GitHub Actions Runner: Instance types are limited to a fixed list of x64 families plus g4dn
Run your slowest workflow on both before deciding. See the full Cirun profile and HyperEnv for GitHub Actions Runner profile, or the complete comparison.
More comparisons
- Actuated vs Cirun
- Cirun vs GARM (GitHub Actions Runner Manager)
- Cirun vs RunsOn
- Cirun vs Sprinters
- Cirun vs terraform-aws-github-runner
- Cirun vs WarpBuild
- Cirun vs machine.dev
- HyperEnv for GitHub Actions Runner vs RunsOn
- HyperEnv for GitHub Actions Runner vs Sprinters
- HyperEnv for GitHub Actions Runner vs terraform-aws-github-runner
Frequently asked questions
Is Cirun or HyperEnv for GitHub Actions Runner better?
What is the difference between Cirun and HyperEnv for GitHub Actions Runner?
Which is open source, Cirun or HyperEnv for GitHub Actions Runner?
How do Cirun and HyperEnv for GitHub Actions Runner isolate jobs?
How does Cirun pricing compare with HyperEnv for GitHub Actions Runner?
Do Cirun and HyperEnv for GitHub Actions Runner cache Docker layers?
Do Cirun and HyperEnv for GitHub Actions Runner offer GPU runners?
Where do Cirun and HyperEnv for GitHub Actions Runner runners run?
Sources
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 HyperEnv for GitHub Actions Runner. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/compare/cirun-vs-hyperenv/