RunsOn vs Sprinters
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. Sprinters suits teams on GitHub Actions that want Ubuntu runners on EC2 in their own AWS account with a per-job fee and no subscription. 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; Sprinters is a product that runs runners in your own cloud account or on your own hardware for GitHub Actions, priced at $0.01/job + AWS cost.
Key differences between RunsOn and Sprinters
- Operating systems: Only RunsOn documents Windows.
- Published price: €300/yr licence + AWS cost (RunsOn) versus $0.01/job + AWS cost (Sprinters).
- Largest runner: 896 vCPU (RunsOn) versus 384 vCPU / 3072 GB (Sprinters).
- Self-hosting: RunsOn documents a self-hosted option; Sprinters does not.
- Company headquarters: RunsOn is based in Thorigné-Fouillard, France; InfrastructureX GmbH is based in Munich, 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 document arm64 runners.
- Both use a virtual machine per runner.
- Both give every job a fresh environment.
- Neither is open source.
RunsOn vs Sprinters at a glance
| Attribute | RunsOn | Sprinters |
|---|---|---|
| What it is | Self-hosted GitHub Actions runner control plane installed in your own AWS account, launching one fresh EC2 instance per job. | GitHub App that launches one ephemeral EC2 instance per GitHub Actions job in your own AWS account, charged per job rather than per minute. |
| 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, Windows | Linux |
| Architectures | x64, arm64 | x64, arm64 |
| Isolation | Each job runs on an EC2 instance that no other job has used and that is terminated when the job ends | Each job runs on a new EC2 instance in your VPC with a read-only boot volume, encrypted temp and swap volumes and a security group that prohibits ingress; the instance and its volumes are destroyed after the job |
| Fresh environment per job | Yes | Yes |
| Hardware | Any EC2 instance family selected by label, including Graviton and families with local NVMe; the docs cite 1 to 896 vCPUs. | 612 EC2 instance types across Intel, AMD and Graviton families, with optional local NVMe or zram temp storage. |
| 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) | Sprinters says jobs run 30% faster and about 10x cheaper per minute than on GitHub-hosted runners; its own Hugo benchmark shows 20% faster and 12.1x cheaper (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 | 1 to 384 vCPUs, 0.5 to 3,072 GiB RAM and 1 to 65,536 GiB temp disk; defaults are t3.large on x64 and t4g.large on arm64 |
| 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. | Not documented |
| Docker layer caching | Yes | Not documented |
| 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. | Not documented |
| Concurrency | No RunsOn concurrency limit is documented; the Flex mode is recommended for up to about 50,000 jobs a day | The pricing page lists unlimited concurrency |
| Static IPs | Yes | Not documented |
| SSH into running jobs | Yes | Not documented |
| 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. | $0.01 per job on private repositories, counted only when the runner launches successfully; public repositories are free. There is no subscription or per-vCPU-minute fee; AWS bills compute, storage and bandwidth to your account. |
| 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 | Free for public repositories; 1,000 free jobs in the first 30 days for private repositories |
| Open source | No | No |
| Self-host / your cloud | Yes / Yes | No / Yes |
| Compliance | Not documented | Not documented |
| Regions | Not documented | 10 AWS regions: us-east-1, us-west-2, ca-central-1, eu-central-1, eu-west-1, eu-west-2, me-central-1, ap-northeast-1, ap-northeast-2, ap-south-1 |
| Company headquarters | Thorigné-Fouillard, Brittany, France | Munich, Bavaria, Germany |
| 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 | Teams on GitHub Actions that want Ubuntu runners on EC2 in their own AWS account with a per-job fee and no subscription |
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 Sprinters
- You want a flat $0.01 per job fee with no subscription and no per-minute charge beyond your AWS bill
- You need runners inside your own VPC and subnets to reach private AWS resources
- You want to pick any of 612 x64 and arm64 EC2 instance types, up to 384 vCPUs, in the runs-on label
- You maintain public repositories, which are free
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
- Sprinters: Only Ubuntu 22.04 and 24.04 images are documented; Windows and macOS runners are not documented
- Sprinters: Runners can launch only in the 10 AWS regions the docs list
Run your slowest workflow on both before deciding. See the full RunsOn profile and Sprinters profile, or the complete comparison.
More comparisons
Frequently asked questions
Is RunsOn or Sprinters better?
What is the difference between RunsOn and Sprinters?
Which is open source, RunsOn or Sprinters?
How do RunsOn and Sprinters isolate jobs?
How does RunsOn pricing compare with Sprinters?
Is RunsOn or Sprinters faster?
Do RunsOn and Sprinters cache Docker layers?
Do RunsOn and Sprinters offer GPU runners?
Where do RunsOn and Sprinters 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). RunsOn vs Sprinters. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/compare/runs-on-vs-sprinters/