HyperEnv for GitHub Actions Runner vs terraform-aws-github-runner
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. terraform-aws-github-runner suits teams on AWS that manage infrastructure with Terraform and want GitHub Actions runners on EC2 that scale to zero. 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; terraform-aws-github-runner is an open-source project you run yourself for GitHub Actions.
Key differences between HyperEnv for GitHub Actions Runner and terraform-aws-github-runner
- Type: HyperEnv for GitHub Actions Runner 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.
- Operating systems: Only terraform-aws-github-runner documents Windows and macOS.
- Architectures: Only terraform-aws-github-runner documents arm64.
- Open source: terraform-aws-github-runner is open source (MIT); HyperEnv for GitHub Actions Runner is not.
What they have in common
- Both run GitHub Actions jobs.
- Both document Linux runners.
- Both use a virtual machine per runner.
- Both can be self-hosted.
- Both document GPU runners.
HyperEnv for GitHub Actions Runner vs terraform-aws-github-runner at a glance
| Attribute | HyperEnv for GitHub Actions Runner | terraform-aws-github-runner |
|---|---|---|
| What it is | AWS Marketplace product that runs each GitHub Actions job on an ephemeral EC2 instance, deployed entirely inside your own AWS account. | 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 | Linux, Windows, macOS |
| Architectures | x64 | x64, arm64 |
| Isolation | Each job gets a new EC2 instance that registers an ephemeral GitHub runner and is terminated after the job completes or times out | 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 | A fixed list of EC2 instance families: t3, m5, m6i, m7i, m7i-flex, m7a and g4dn. | 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 | Up to 192 vCPUs, 768 GiB memory and a 16 TB disk volume; the default instance type is m6i.large | Not documented |
| Caching | An S3-backed cache in your account is enabled by default (S3Cache parameter, 30-day expiration); it is not supported for GitHub Enterprise Server. | Not documented |
| Docker layer caching | Not documented | Not documented |
| GPU | 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. | With dynamic labels enabled, ghr-ec2 override labels can request EC2 instance requirements that include GPU accelerator types. |
| Concurrency | Not documented | 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 | Yes | Yes |
| Pricing | $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 and open source; you pay for the infrastructure it runs on. |
| Free tier | Not documented | Not documented |
| Open source | No | Yes (MIT) |
| Self-host / your cloud | Yes / Yes | Yes / Yes |
| Compliance | ISO 27001 (widdix GmbH) | Not documented |
| Regions | Not documented | Not documented |
| Company headquarters | Lichtenwald, Baden-Württemberg, Germany | Not documented |
| Good fit for | Teams that buy through AWS Marketplace and want GitHub Actions runners that run entirely inside their AWS account for a metered per-minute fee | 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 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
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
- 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
- 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 HyperEnv for GitHub Actions Runner profile and terraform-aws-github-runner profile, or the complete comparison.
More comparisons
- Cirun vs HyperEnv for GitHub Actions Runner
- HyperEnv for GitHub Actions Runner vs RunsOn
- HyperEnv for GitHub Actions Runner vs Sprinters
- Actions Runner Controller (ARC) vs terraform-aws-github-runner
- AWS CodeBuild-hosted runners vs terraform-aws-github-runner
- Cirun vs terraform-aws-github-runner
- GARM (GitHub Actions Runner Manager) 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 HyperEnv for GitHub Actions Runner or terraform-aws-github-runner better?
What is the difference between HyperEnv for GitHub Actions Runner and terraform-aws-github-runner?
Which is open source, HyperEnv for GitHub Actions Runner or terraform-aws-github-runner?
How do HyperEnv for GitHub Actions Runner and terraform-aws-github-runner isolate jobs?
How does HyperEnv for GitHub Actions Runner pricing compare with terraform-aws-github-runner?
Do HyperEnv for GitHub Actions Runner and terraform-aws-github-runner offer GPU runners?
Where do HyperEnv for GitHub Actions Runner and terraform-aws-github-runner runners run?
Sources
- hyperenv.com/
- hyperenv.com/pricing/
- aws.amazon.com/marketplace/pp/prodview-7bzr422ymm2hw
- hyperenv.com/help/
- 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). HyperEnv for GitHub Actions Runner vs terraform-aws-github-runner. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/compare/hyperenv-vs-terraform-aws-github-runner/