RunsOn
Self-hosted GitHub Actions runner control plane installed in your own AWS account, launching one fresh EC2 instance per job. RunsOn is licensed software that runs ephemeral GitHub Actions runners entirely in your own AWS account, suited to teams that want AWS-native control and a flat annual fee.
Overview
RunsOn is a runner control plane for GitHub Actions that you install in your own AWS account with a CloudFormation stack or a Terraform/OpenTofu module. The control plane runs on Fargate, and every job gets a new EC2 instance that is terminated when the job ends. Linux (x64 and arm64) and Windows images are provided; macOS jobs stay on GitHub-hosted runners. Spot instances are used by default, with on-demand fallback.
Two modes share one licence. Flex lets each workflow choose CPU, RAM, instance family, image and disk in its runs-on label; Fleet, added in June 2026, uses a Terraform-managed catalogue built on GitHub runner scale sets. The CloudFormation templates are MIT-licensed, while the server and agent are proprietary with source access on the top tier. Pricing is a flat annual licence by job volume, and compute is billed by AWS.
Notable
- RunsOn launched in 2023, according to its about page, which describes it as funded by customer licences rather than investors.
- v3.1.0 (2 June 2026) introduced Fleet, a pool-based mode built on GitHub Actions runner scale sets.
- v3.6.0 (4 November 2026) added remote caches for Bazel, Go, Gradle, sccache and Turborepo served from your own S3 bucket.
- GitHub Enterprise Server support arrived in v2.7.2 (3 April 2025).
RunsOn specifications
| Attribute | Details |
|---|---|
| CI systems | GitHub Actions |
| Operating systems | Linux, Windows |
| Architectures | x64, arm64 |
| Deployment | Runs in your cloud or on your hardware · Self-hostable |
| Where it can run | AWS |
| Isolation | 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 |
| Hardware | Any EC2 instance family selected by label, including Graviton and families with local NVMe; the docs cite 1 to 896 vCPUs. |
| 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) |
| Runner sizes | 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 | 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 | Yes |
| GPU | 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 | No RunsOn concurrency limit is documented; the Flex mode is recommended for up to about 50,000 jobs a day |
| Job limits | Flex terminates runners after 12 hours by default (RunnerMaxRuntime, configurable, minimum 30 minutes) |
| Static IPs | Yes |
| SSH into running jobs | Yes |
| Observability | Per-job cost estimates and runner metrics, an automatic CloudWatch dashboard, OpenTelemetry export of logs, metrics and traces, and a daily budget alarm; email cost reports on Flex. |
| Setup | Deploy the CloudFormation stack (or the Terraform/OpenTofu module) in your AWS account, register the private GitHub App from the stack output, then change runs-on in each workflow. |
| Example label | runs-on=${{ github.run_id }}/runner=2cpu-linux-x64 |
| Pricing | 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 | 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 |
| Compliance | Not documented |
| Regions | Not documented |
| Open source | No |
| Company headquarters | Thorigné-Fouillard, Brittany, France · More from France |
Facts from RunsOn’s public documentation, verified November 22, 2026. Performance figures are vendor claims.
Strengths and trade-offs
Reasons to choose it
- 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
- You want S3-backed Actions, Docker layer and build-tool caches without a size cap
Trade-offs
- AWS only, and macOS is not supported: macOS jobs stay on GitHub-hosted runners
- The server and agent are proprietary; full source is offered only with the €3,600/year Sponsorship licence
- You run the stack yourself and pay AWS for the control plane, any NAT gateway and all compute
- A licence check and one event per job are sent to runs-on.com, and the job event cannot be turned off
Good fit for: Teams on GitHub Actions that want ephemeral EC2 runners, caches and networking kept inside their own AWS account under a flat annual licence.
Use cases RunsOn fits
- Lower CI cost: RunsOn charges a flat annual licence and compute is billed by AWS at spot or on-demand rates with no markup.
- Docker builds: Docker layers can be cached through S3-backed Buildx caching, a per-stack ECR registry or sticky EBS disks.
- ARM64 builds: Ubuntu arm64 images run on Graviton instance families selected by label.
- Windows builds: Windows Server 2025 images are provided for x64 runners.
- GPU jobs: GPU images with NVIDIA drivers and CUDA are published for x64 and Graviton GPU instances.
- Your own cloud: The control plane and every runner run in your own AWS account, installed by CloudFormation or Terraform.
- Security and compliance: Runners can be confined to private subnets with static egress IPs, and each job gets a single-use instance.
How RunsOn compares
| Runner | CI systems | Runs on | Deployment | Isolation | Price | Largest runner | Docker layer cache | GPU | Open source | Company HQ |
|---|---|---|---|---|---|---|---|---|---|---|
| RunsOn | GitHub Actions | Linux, Windows, x64, arm64 | Your cloud or hardware | EC2 instance | €300/yr licence + AWS cost | 896 vCPU | Yes | Yes | No | France |
| Sprinters | GitHub Actions | Linux, x64, arm64 | Your cloud or hardware | EC2 instance | $0.01/job + AWS cost | 384 vCPU / 3072 GB | Not documented | Not documented | No | Germany |
| HyperEnv for GitHub Actions Runner | GitHub Actions | Linux, x64 | Your cloud or hardware | EC2 instance | $0.002/min fee + AWS cost | 192 vCPU / 768 GB | Not documented | Yes | No | Germany |
| Cirun | GitHub Actions | Linux, macOS, Windows, x64, arm64 | Your cloud or hardware | Cloud VM | $29/mo (3 private repos) + cloud cost | Set by your infrastructure | Yes | Yes | No | United Kingdom |
| terraform-aws-github-runner | GitHub Actions | Linux, Windows, macOS, x64, arm64 | Self-hosted | EC2 instance | Free software + your infrastructure | Set by your infrastructure | Not documented | Yes | Yes | Not documented |
| AWS CodeBuild-hosted runners | GitHub Actions, GitLab CI, Buildkite | Linux, Windows, x64, arm64 | Your cloud account | Fresh build environment | $0.005/min | 72 vCPU / 144 GB | Yes | Yes | No | United States |
| Actions Runner Controller (ARC) | GitHub Actions | Linux, Windows | Self-hosted | Kubernetes pod | Free software + your infrastructure | Set by your infrastructure | Not documented | Not documented | Yes | United States |
| WarpBuild | GitHub Actions | Linux, macOS, Windows, x64, arm64 | Vendor-hosted | Ephemeral VM | $0.004/min | 32 vCPU / 128 GB | Yes | Not documented | No | Not documented |
| Actuated | GitHub Actions, GitLab CI | Linux, x64, arm64 | Your cloud or hardware | Firecracker microVM | $150/mo per server + your servers | Set by your infrastructure | Yes | Yes | No | United Kingdom |
Head-to-head: Actions Runner Controller (ARC) vs RunsOn · Actuated vs RunsOn · AWS CodeBuild-hosted runners vs RunsOn · Cirun vs RunsOn · HyperEnv for GitHub Actions Runner vs RunsOn · RunsOn vs Sprinters · RunsOn vs terraform-aws-github-runner · RunsOn vs WarpBuild
Frequently asked questions
What is RunsOn?
Which CI systems does RunsOn work with?
How does RunsOn isolate jobs?
Is RunsOn open source?
How much does RunsOn cost?
How do you set up RunsOn?
runs-on=${{ github.run_id }}/runner=2cpu-linux-x64.How fast is RunsOn?
Does RunsOn have a free tier?
Does RunsOn support ARM64 runners?
Does RunsOn cache Docker layers?
Does RunsOn offer GPU runners?
How many jobs can run at once on RunsOn?
Where is RunsOn based?
What are the alternatives to RunsOn?
Sources
- runs-on.com/
- runs-on.com/pricing/
- runs-on.com/docs/
- runs-on.com/docs/flex-vs-fleet/
- runs-on.com/security/
- runs-on.com/docs/runners/platforms/linux/
- runs-on.com/docs/runners/platforms/windows/
- runs-on.com/runners/gpu/
- runs-on.com/docs/runners/labels/
- runs-on.com/docs/runners/capabilities/static-ips/
- runs-on.com/docs/runners/capabilities/remote-access/
- runs-on.com/docs/performance/caching/docker/
- runs-on.com/docs/observability/
- runs-on.com/docs/control-plane/housekeeping/
- runs-on.com/changelog/
- runs-on.com/about/
- runs-on.com/legal/privacy/
- github.com/runs-on/runs-on
- github.com/runs-on/runs-on/blob/main/SPONSORSHIP.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. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/runners/runs-on/