CI Runnerscirunners.org
Head-to-head

RunsOn vs terraform-aws-github-runner

Answer in brief

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. terraform-aws-github-runner suits teams on AWS that manage infrastructure with Terraform and want GitHub Actions runners on EC2 that scale to zero. 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; terraform-aws-github-runner is an open-source project you run yourself for GitHub Actions.

By the CI Runners editors · Updated

Key differences between RunsOn and terraform-aws-github-runner

  • Type: RunsOn 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 macOS.
  • Open source: terraform-aws-github-runner is open source (MIT); RunsOn is not.

What they have in common

  • Both run GitHub Actions jobs.
  • Both document Linux and Windows runners.
  • Both document arm64 runners.
  • Both use a virtual machine per runner.
  • Both can be self-hosted.
  • Both document GPU runners.

RunsOn vs terraform-aws-github-runner at a glance

AttributeRunsOnterraform-aws-github-runner
What it isSelf-hosted GitHub Actions runner control plane installed in your own AWS account, launching one fresh EC2 instance per job.Terraform module that runs GitHub Actions runners on EC2 spot or on-demand instances, scaled by Lambda functions.
TypeRuns in your cloud or on your hardwareOpen-source project
CI systemsGitHub ActionsGitHub Actions
Operating systemsLinux, WindowsLinux, Windows, macOS
Architecturesx64, arm64x64, arm64
IsolationEach job runs on an EC2 instance that no other job has used and that is terminated when the job endsEach 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 jobYesNot documented
HardwareAny EC2 instance family selected by label, including Graviton and families with local NVMe; the docs cite 1 to 896 vCPUs.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)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)Not documented
Runner sizesPredefined 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 vCPUsNot documented
CachingMagic 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.Not documented
Docker layer cachingYesNot documented
GPUGPU 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.With dynamic labels enabled, ghr-ec2 override labels can request EC2 instance requirements that include GPU accelerator types.
ConcurrencyNo RunsOn concurrency limit is documented; the Flex mode is recommended for up to about 50,000 jobs a dayThe 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 IPsYesNot documented
SSH into running jobsYesYes
PricingFlat 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 and open source; you pay for the infrastructure it runs on.
Free tierFree licence for non-commercial use (open source, non-profit, educational, personal) with a public link back; 15-day trial on Starter, Growth and ScaleNot documented
Open sourceNoYes (MIT)
Self-host / your cloudYes / YesYes / Yes
ComplianceNot documentedNot documented
RegionsNot documentedNot documented
Company headquartersThorigné-Fouillard, Brittany, FranceNot documented
Good fit forTeams on GitHub Actions that want ephemeral EC2 runners, caches and networking kept inside their own AWS account under a flat annual licenceTeams 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 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

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

  • 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
  • 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 RunsOn profile and terraform-aws-github-runner profile, or the complete comparison.

More comparisons

Frequently asked questions

Is RunsOn or terraform-aws-github-runner better?
Neither is better for every pipeline. 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. terraform-aws-github-runner suits teams on AWS that manage infrastructure with Terraform and want GitHub Actions runners on EC2 that scale to zero.
What is the difference between RunsOn and terraform-aws-github-runner?
RunsOn 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. Only terraform-aws-github-runner documents macOS. terraform-aws-github-runner is open source (MIT); RunsOn is not.
Which is open source, RunsOn or terraform-aws-github-runner?
RunsOn is not open source; terraform-aws-github-runner is open source (MIT).
How do RunsOn and terraform-aws-github-runner isolate jobs?
RunsOn: Each job runs on an EC2 instance that no other job has used and that is terminated when the job ends. terraform-aws-github-runner: 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.
How does RunsOn pricing compare with terraform-aws-github-runner?
RunsOn: 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. terraform-aws-github-runner: Free and open source; you pay for the infrastructure it runs on. Rates change, so check the RunsOn and terraform-aws-github-runner pricing pages before deciding.
Is RunsOn or terraform-aws-github-runner faster?
We have not benchmarked them, and speed depends on the workload. What each provider says: RunsOn: 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). terraform-aws-github-runner: Not documented.
Do RunsOn and terraform-aws-github-runner cache Docker layers?
RunsOn: 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. terraform-aws-github-runner: Docker layer caching is not documented.
Do RunsOn and terraform-aws-github-runner offer GPU runners?
RunsOn: 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. terraform-aws-github-runner: With dynamic labels enabled, ghr-ec2 override labels can request EC2 instance requirements that include GPU accelerator types.
Where do RunsOn and terraform-aws-github-runner runners run?
RunsOn is a product that runs runners in your own cloud account or on your own hardware (AWS). terraform-aws-github-runner is an open-source project you run yourself (AWS).

Sources

  1. runs-on.com/
  2. runs-on.com/pricing/
  3. runs-on.com/docs/
  4. runs-on.com/docs/flex-vs-fleet/
  5. github.com/github-aws-runners/terraform-aws-github-runner
  6. github.com/github-aws-runners/terraform-aws-github-runner/releases
  7. github.com/github-aws-runners/terraform-aws-github-runner/blob/main/CHANGELOG.md
  8. 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). RunsOn vs terraform-aws-github-runner. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/compare/runs-on-vs-terraform-aws-github-runner/