Cirun
Hosted control plane that launches on-demand GitHub Actions runners in your own cloud accounts or on-prem hardware from a .cirun.yml file. Cirun is a hosted orchestrator that starts single-use GitHub Actions runners in your own cloud accounts or on your own machines, suited to teams that need several clouds, GPUs or ARM under a flat fee.
Overview
Cirun is a hosted service that creates GitHub Actions runners in cloud accounts you own. You install its GitHub App, store cloud credentials in the dashboard and describe runners in a .cirun.yml file: cloud, instance type, machine image, region and labels. When a job with a matching label is queued, Cirun starts a virtual machine in your account and, according to its security page, destroys it immediately after the job completes.
The docs name AWS, GCP, Azure, Hetzner, DigitalOcean, Oracle, OpenStack and Vast.ai as providers, and an MIT-licensed cirun-agent registers your own Linux or Apple Silicon machines as an on-prem runner pool. Options include spot or preemptible instances, custom images, Windows runners on AWS and Azure, scheduled idle runners and an S3-backed Actions cache. Pricing is a flat monthly fee by number of private repositories, and public repositories are free.
Notable
- The site footer carries a 2021-2026 copyright for Cirun.io, Aktech Labs.
- The homepage describes the company as profitable and bootstrapped (checked 2026-11-22).
- The caching docs list other clouds and Windows/macOS for automatic S3 caching as roadmap items (checked 2026-11-22).
Cirun specifications
| Attribute | Details |
|---|---|
| CI systems | GitHub Actions |
| Operating systems | Linux, macOS, Windows |
| Architectures | x64, arm64 |
| Deployment | Runs in your cloud or on your hardware |
| Where it can run | AWS, Google Cloud, Azure, Hetzner, DigitalOcean, Oracle Cloud, OpenStack, Vast.ai, Bare metal |
| 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 |
| Fresh environment per job | Yes |
| Hardware | Any instance type offered by the connected cloud account, or your own Linux (KVM) and Apple Silicon machines through cirun-agent. |
| Performance (vendor claim) | Not documented |
| Runner sizes | Not documented |
| 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. |
| Docker layer caching | Yes |
| 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. |
| 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 |
| Job limits | Not documented |
| Static IPs | Not documented |
| SSH into running jobs | Not documented |
| Observability | Not documented |
| Setup | Install the Cirun GitHub App, add cloud credentials in the dashboard, commit a .cirun.yml that defines runners, then point runs-on at the runner label. |
| Example label | cirun-gpu-runner--${{ github.run_id }} |
| 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. |
| Free tier | Free for public repositories, with unlimited runners, ARM and GPU runners on all supported cloud providers |
| Compliance | Not documented |
| Regions | Any region of the connected cloud account, set per runner in .cirun.yml |
| Open source | No |
| Company headquarters | London, England, United Kingdom · More from the United Kingdom |
Facts from Cirun’s public documentation, verified November 22, 2026. Performance figures are vendor claims.
Strengths and trade-offs
Reasons to choose it
- 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
- You prefer a flat monthly price by private repository count instead of per-minute billing
Trade-offs
- Automatic S3 caching currently covers Linux runners on AWS only
- The AWS setup documents an IAM user access key with EC2 admin permissions entered in the Cirun dashboard
- Startup and Business plans are limited to 3 and 10 private repositories
- Windows runners are documented on AWS and Azure only and require a Windows licence with multi-tenant rights
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.
Use cases Cirun fits
- ARM64 builds: ARM-based runners are included in every plan and the on-prem Docker runner image is multi-arch.
- macOS and iOS builds: The on-prem agent can run macOS VMs on Apple Silicon hosts through the lume executor.
- Windows builds: Windows runners are documented on AWS and Azure, including ARM64 on Azure.
- GPU jobs: GPU runners are included in every plan and the docs show GPU instances on Google Cloud and Vast.ai as a provider.
- Your own cloud: Runners are created in cloud accounts you connect, or on your own hardware through cirun-agent.
How Cirun compares
| Runner | CI systems | Runs on | Deployment | Isolation | Price | Largest runner | Docker layer cache | GPU | Open source | Company HQ |
|---|---|---|---|---|---|---|---|---|---|---|
| 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 |
| RunsOn | GitHub Actions | Linux, Windows, x64, arm64 | Your cloud or hardware | EC2 instance | €300/yr licence + AWS cost | 896 vCPU | Yes | Yes | No | France |
| 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 |
| 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 |
| 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 |
| GARM (GitHub Actions Runner Manager) | GitHub Actions, Forgejo/Gitea Actions | Linux, Windows, x64, arm64 | Self-hosted | Depends on provider | Free software + your infrastructure | Set by your infrastructure | Not documented | Not documented | Yes | Romania |
| 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 |
| 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 |
Head-to-head: Actuated vs Cirun · Cirun vs GARM (GitHub Actions Runner Manager) · Cirun vs HyperEnv for GitHub Actions Runner · Cirun vs RunsOn · Cirun vs Sprinters · Cirun vs terraform-aws-github-runner · Cirun vs WarpBuild · Cirun vs machine.dev
Frequently asked questions
What is Cirun?
Which CI systems does Cirun work with?
How does Cirun isolate jobs?
Is Cirun open source?
How much does Cirun cost?
How do you set up Cirun?
cirun-gpu-runner--${{ github.run_id }}.Does Cirun have a free tier?
Does Cirun support ARM64 runners?
Does Cirun offer macOS runners?
Does Cirun cache Docker layers?
Does Cirun offer GPU runners?
How many jobs can run at once on Cirun?
Where do Cirun runners run?
Where is Aktech Labs based?
What are the alternatives to Cirun?
Sources
- cirun.io/
- cirun.io/pricing
- docs.cirun.io/
- docs.cirun.io/quickstart
- docs.cirun.io/reference/yaml
- docs.cirun.io/cloud/
- docs.cirun.io/cloud/aws
- docs.cirun.io/on-prem
- docs.cirun.io/caching/
- docs.cirun.io/os-platform/windows
- docs.cirun.io/reference/idle-runners
- docs.cirun.io/security
- docs.cirun.io/terms-of-service
- github.com/cirunlabs/cirun-agent
- aktechlabs.com/about/
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. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/runners/cirun/