Cirun vs Sprinters
Cirun suits teams and open-source projects on GitHub Actions that want on-demand runners, including GPU and ARM machines, across several clouds or on their own hardware. 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. Cirun is a product that runs runners in your own cloud account or on your own hardware for GitHub Actions, priced at $29/mo (3 private repos) + cloud 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 Cirun and Sprinters
- Operating systems: Only Cirun documents macOS and Windows.
- Isolation: Cirun: Cloud VM. Sprinters: EC2 instance.
- Published price: $29/mo (3 private repos) + cloud cost (Cirun) versus $0.01/job + AWS cost (Sprinters).
- Company headquarters: Aktech Labs is based in London, United Kingdom; 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.
Cirun vs Sprinters at a glance
| Attribute | Cirun | Sprinters |
|---|---|---|
| What it is | Hosted control plane that launches on-demand GitHub Actions runners in your own cloud accounts or on-prem hardware from a .cirun.yml file. | 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, macOS, Windows | Linux |
| Architectures | x64, arm64 | x64, arm64 |
| Isolation | Each job runs in a fresh virtual machine created in your cloud account and destroyed after the job; on-prem runners use cloud-hypervisor VMs on Linux, Apple Virtualization VMs on macOS or opt-in Docker containers | 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 instance type offered by the connected cloud account, or your own Linux (KVM) and Apple Silicon machines through cirun-agent. | 612 EC2 instance types across Intel, AMD and Graviton families, with optional local NVMe or zram temp storage. |
| Performance (vendor claim) | Not documented | 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 | Not documented | 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 | Setting extra_config.cache: true redirects actions/cache to an S3 bucket in your own AWS account with no Cirun size limit (automatic mode covers Linux runners on AWS); a separate cirunlabs/cache/s3 action works with any S3-compatible store. Docker Buildx type=gha caching through the same proxy is documented. | Not documented |
| Docker layer caching | Yes | Not documented |
| GPU | GPU runners are included in every plan; the docs show an NVIDIA Tesla T4 attached to a Google Cloud instance and list Vast.ai as a provider, with GPU cost billed by your cloud. | Not documented |
| Concurrency | No plan concurrency limit is published; the on-prem agent defaults to 2 concurrent runners on macOS hosts and is unlimited by default on Linux | The pricing page lists unlimited concurrency |
| Static IPs | Not documented | Not documented |
| SSH into running jobs | Not documented | Not documented |
| Pricing | Open Source: $0 for unlimited public repositories. Startup: $29 per month for 3 private repositories. Business: $79 per month for 10 private repositories. Enterprise: custom pricing. Compute is billed by your own cloud provider. | $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 for public repositories, with unlimited runners, ARM and GPU runners on all supported cloud providers | Free for public repositories; 1,000 free jobs in the first 30 days for private repositories |
| Open source | No | No |
| Self-host / your cloud | Not documented / Yes | No / Yes |
| Compliance | Not documented | Not documented |
| Regions | Any region of the connected cloud account, set per runner in .cirun.yml | 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 | London, England, United Kingdom | Munich, Bavaria, Germany |
| Good fit for | Teams and open-source projects on GitHub Actions that want on-demand runners, including GPU and ARM machines, across several clouds or on their own hardware | 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 Cirun
- You want runners in your own account on AWS, Google Cloud, Azure, DigitalOcean, Oracle Cloud, OpenStack or other listed providers from one configuration file
- You need GPU or ARM runners, which every plan includes
- You maintain public repositories, where the Open Source plan is free
- You want to register your own Linux or Apple Silicon machines as an on-prem runner pool
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
- Cirun: Automatic S3 caching currently covers Linux runners on AWS only
- Cirun: The AWS setup documents an IAM user access key with EC2 admin permissions entered in the Cirun dashboard
- 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 Cirun profile and Sprinters profile, or the complete comparison.
More comparisons
Frequently asked questions
Is Cirun or Sprinters better?
What is the difference between Cirun and Sprinters?
Which is open source, Cirun or Sprinters?
How do Cirun and Sprinters isolate jobs?
How does Cirun pricing compare with Sprinters?
Is Cirun or Sprinters faster?
Do Cirun and Sprinters cache Docker layers?
Do Cirun and Sprinters offer GPU runners?
Where do Cirun 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). Cirun vs Sprinters. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/compare/cirun-vs-sprinters/