CI Runnerscirunners.org
Head-to-head

Cirun vs RunsOn

Answer in brief

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. 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. 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; 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.

By the CI Runners editors · Updated

Key differences between Cirun and RunsOn

  • Operating systems: Only Cirun documents macOS.
  • Isolation: Cirun: Cloud VM. RunsOn: EC2 instance.
  • Published price: $29/mo (3 private repos) + cloud cost (Cirun) versus €300/yr licence + AWS cost (RunsOn).
  • Company headquarters: Aktech Labs is based in London, United Kingdom; 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 and Windows runners.
  • Both document arm64 runners.
  • Both use a virtual machine per runner.
  • Both give every job a fresh environment.
  • Neither is open source.
  • Both document Docker layer caching.
  • Both document GPU runners.

Cirun vs RunsOn at a glance

AttributeCirunRunsOn
What it isHosted control plane that launches on-demand GitHub Actions runners in your own cloud accounts or on-prem hardware from a .cirun.yml file.Self-hosted GitHub Actions runner control plane installed in your own AWS account, launching one fresh EC2 instance per job.
TypeRuns in your cloud or on your hardwareRuns in your cloud or on your hardware
CI systemsGitHub ActionsGitHub Actions
Operating systemsLinux, macOS, WindowsLinux, Windows
Architecturesx64, arm64x64, arm64
IsolationEach 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 containersEach job runs on an EC2 instance that no other job has used and that is terminated when the job ends
Fresh environment per jobYesYes
HardwareAny instance type offered by the connected cloud account, or your own Linux (KVM) and Apple Silicon machines through cirun-agent.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 documentedRunsOn 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 sizesNot documentedPredefined 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
CachingSetting 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.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 cachingYesYes
GPUGPU 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.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.
ConcurrencyNo plan concurrency limit is published; the on-prem agent defaults to 2 concurrent runners on macOS hosts and is unlimited by default on LinuxNo RunsOn concurrency limit is documented; the Flex mode is recommended for up to about 50,000 jobs a day
Static IPsNot documentedYes
SSH into running jobsNot documentedYes
PricingOpen 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.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 tierFree for public repositories, with unlimited runners, ARM and GPU runners on all supported cloud providersFree 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 sourceNoNo
Self-host / your cloudNot documented / YesYes / Yes
ComplianceNot documentedNot documented
RegionsAny region of the connected cloud account, set per runner in .cirun.ymlNot documented
Company headquartersLondon, England, United KingdomThorigné-Fouillard, Brittany, France
Good fit forTeams and open-source projects on GitHub Actions that want on-demand runners, including GPU and ARM machines, across several clouds or on their own hardwareTeams 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 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 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

  • 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
  • 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 Cirun profile and RunsOn profile, or the complete comparison.

More comparisons

Frequently asked questions

Is Cirun or RunsOn better?
Neither is better for every pipeline. 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. 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.
What is the difference between Cirun and RunsOn?
Only Cirun documents macOS. Isolation is Cloud VM on Cirun and EC2 instance on RunsOn. Published price: $29/mo (3 private repos) + cloud cost (Cirun) versus €300/yr licence + AWS cost (RunsOn). Aktech Labs is based in London, United Kingdom; RunsOn is based in Thorigné-Fouillard, France.
Which is open source, Cirun or RunsOn?
Neither is open source.
How do Cirun and RunsOn isolate jobs?
Cirun: 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. RunsOn: Each job runs on an EC2 instance that no other job has used and that is terminated when the job ends.
How does Cirun pricing compare with RunsOn?
Cirun: 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. 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. Rates change, so check the Cirun and RunsOn pricing pages before deciding.
Is Cirun or RunsOn faster?
We have not benchmarked them, and speed depends on the workload. What each provider says: Cirun: Not documented. 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).
Do Cirun and RunsOn cache Docker layers?
Cirun: 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. 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.
Do Cirun and RunsOn offer GPU runners?
Cirun: 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. 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.
Where do Cirun and RunsOn runners run?
Cirun is a product that runs runners in your own cloud account or on your own hardware (AWS, Google Cloud, Azure, Hetzner, DigitalOcean, Oracle Cloud, OpenStack, Vast.ai and Bare metal). RunsOn is a product that runs runners in your own cloud account or on your own hardware (AWS).

Sources

  1. cirun.io/
  2. cirun.io/pricing
  3. docs.cirun.io/
  4. docs.cirun.io/quickstart
  5. runs-on.com/
  6. runs-on.com/pricing/
  7. runs-on.com/docs/
  8. runs-on.com/docs/flex-vs-fleet/

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 RunsOn. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/compare/cirun-vs-runs-on/