HyperEnv for GitHub Actions Runner vs RunsOn
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. RunsOn suits teams on GitHub Actions that want ephemeral EC2 runners, caches and networking kept inside their own AWS account under a flat annual licence. 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; RunsOn is a product that runs runners in your own cloud account or on your own hardware for GitHub Actions, priced at €300/yr licence + AWS cost.
Key differences between HyperEnv for GitHub Actions Runner and RunsOn
- Operating systems: Only RunsOn documents Windows.
- Architectures: Only RunsOn documents arm64.
- Published price: $0.002/min fee + AWS cost (HyperEnv for GitHub Actions Runner) versus €300/yr licence + AWS cost (RunsOn).
- Largest runner: 192 vCPU / 768 GB (HyperEnv for GitHub Actions Runner) versus 896 vCPU (RunsOn).
- Company headquarters: widdix GmbH is based in Lichtenwald, Germany; RunsOn is based in Thorigné-Fouillard, France.
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 can be self-hosted.
- Both document GPU runners.
HyperEnv for GitHub Actions Runner vs RunsOn at a glance
| Attribute | HyperEnv for GitHub Actions Runner | RunsOn |
|---|---|---|
| What it is | AWS Marketplace product that runs each GitHub Actions job on an ephemeral EC2 instance, deployed entirely inside your own AWS account. | Self-hosted GitHub Actions runner control plane installed in your own AWS account, launching one fresh EC2 instance per job. |
| 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 | Linux, Windows |
| 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 job runs on an EC2 instance that no other job has used and that is terminated when the job ends |
| Fresh environment per job | Yes | Yes |
| Hardware | A fixed list of EC2 instance families: t3, m5, m6i, m7i, m7i-flex, m7a and g4dn. | Any EC2 instance family selected by label, including Graviton and families with local NVMe; the docs cite 1 to 896 vCPUs. |
| Performance (vendor claim) | Not documented | RunsOn says Rust builds run 2.0x, TypeScript 2.1x and Docker builds 2.6x faster than on GitHub-hosted runners in its own benchmarks (vendor claim) |
| Runner sizes | Up to 192 vCPUs, 768 GiB memory and a 16 TB disk volume; the default instance type is m6i.large | Predefined runners from 1 to 64 vCPU on x64 and arm64; labels can request any EC2 instance type, which the docs describe as 1 to 896 vCPUs |
| 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. | Magic Cache redirects actions/cache and Buildx type=gha to an S3 bucket in your account with no size cap (extras=s3-cache). Docker layers can also be cached in a per-stack ECR registry or on sticky EBS disks, and v3.6.0 added S3-backed remote caches for Bazel, Go, Gradle, sccache and Turborepo. |
| Docker layer caching | Not documented | Yes |
| 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. | GPU images with NVIDIA drivers are published for x64 and Graviton instances (examples use g4dn, g5 and g5g); GPU compute is billed by AWS and no RunsOn GPU price is published. |
| Concurrency | Not documented | No RunsOn concurrency limit is documented; the Flex mode is recommended for up to about 50,000 jobs a day |
| Static IPs | Not documented | Yes |
| 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. | Flat annual licence per legal entity: Starter €300/year (under 50k jobs/month), Growth €900/year (under 200k), Scale €1,800/year (under 500k), Sponsorship €3,600/year (unlimited jobs, source access). EC2, EBS and S3 are billed by AWS with no RunsOn markup; RunsOn says the control plane costs from about $7/month. |
| Free tier | Not documented | Free licence for non-commercial use (open source, non-profit, educational, personal) with a public link back; 15-day trial on Starter, Growth and Scale |
| Open source | No | No |
| 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 | Thorigné-Fouillard, Brittany, France |
| 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 GitHub Actions that want ephemeral EC2 runners, caches and networking kept inside their own AWS account under a flat annual licence |
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 RunsOn
- You want every job on a fresh EC2 instance inside your own AWS account, with code, secrets, caches and logs staying there
- You prefer a flat annual licence by job volume over per-minute fees, with compute billed directly by AWS
- You need Linux x64, arm64, Windows or GPU runners chosen per job through labels
- You need static egress IPs, private subnets, or SSM and SSH access to running jobs
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
- RunsOn: AWS only, and macOS is not supported: macOS jobs stay on GitHub-hosted runners
- RunsOn: The server and agent are proprietary; full source is offered only with the €3,600/year Sponsorship licence
Run your slowest workflow on both before deciding. See the full HyperEnv for GitHub Actions Runner profile and RunsOn profile, or the complete comparison.
More comparisons
- Cirun vs HyperEnv for GitHub Actions Runner
- HyperEnv for GitHub Actions Runner vs Sprinters
- HyperEnv for GitHub Actions Runner vs terraform-aws-github-runner
- Actions Runner Controller (ARC) vs RunsOn
- Actuated vs RunsOn
- AWS CodeBuild-hosted runners vs RunsOn
- Cirun vs RunsOn
- RunsOn vs Sprinters
- RunsOn vs terraform-aws-github-runner
- RunsOn vs WarpBuild
Frequently asked questions
Is HyperEnv for GitHub Actions Runner or RunsOn better?
What is the difference between HyperEnv for GitHub Actions Runner and RunsOn?
Which is open source, HyperEnv for GitHub Actions Runner or RunsOn?
How do HyperEnv for GitHub Actions Runner and RunsOn isolate jobs?
How does HyperEnv for GitHub Actions Runner pricing compare with RunsOn?
Is HyperEnv for GitHub Actions Runner or RunsOn faster?
Do HyperEnv for GitHub Actions Runner and RunsOn cache Docker layers?
Do HyperEnv for GitHub Actions Runner and RunsOn offer GPU runners?
Where do HyperEnv for GitHub Actions Runner and RunsOn 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). HyperEnv for GitHub Actions Runner vs RunsOn. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/compare/hyperenv-vs-runs-on/