CI Runnerscirunners.org
Runner profile · Runs in your cloud or on your hardware

Cirun

Answer in brief

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.

By the CI Runners editors · Updated

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

AttributeDetails
CI systemsGitHub Actions
Operating systemsLinux, macOS, Windows
Architecturesx64, arm64
DeploymentRuns in your cloud or on your hardware
Where it can runAWS, Google Cloud, Azure, Hetzner, DigitalOcean, Oracle Cloud, OpenStack, Vast.ai, Bare metal
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 containers
Fresh environment per jobYes
HardwareAny 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 sizesNot documented
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.
Docker layer cachingYes
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.
ConcurrencyNo 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 limitsNot documented
Static IPsNot documented
SSH into running jobsNot documented
ObservabilityNot documented
SetupInstall 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 labelcirun-gpu-runner--${{ github.run_id }}
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.
Free tierFree for public repositories, with unlimited runners, ARM and GPU runners on all supported cloud providers
ComplianceNot documented
RegionsAny region of the connected cloud account, set per runner in .cirun.yml
Open sourceNo
Company headquartersLondon, 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

RunnerCI systemsRuns onDeploymentIsolationPriceLargest runnerDocker layer cacheGPUOpen sourceCompany HQ
CirunGitHub ActionsLinux, macOS, Windows, x64, arm64Your cloud or hardwareCloud VM$29/mo (3 private repos) + cloud costSet by your infrastructureYesYesNoUnited Kingdom
RunsOnGitHub ActionsLinux, Windows, x64, arm64Your cloud or hardwareEC2 instance€300/yr licence + AWS cost896 vCPUYesYesNoFrance
ActuatedGitHub Actions, GitLab CILinux, x64, arm64Your cloud or hardwareFirecracker microVM$150/mo per server + your serversSet by your infrastructureYesYesNoUnited Kingdom
SprintersGitHub ActionsLinux, x64, arm64Your cloud or hardwareEC2 instance$0.01/job + AWS cost384 vCPU / 3072 GBNot documentedNot documentedNoGermany
HyperEnv for GitHub Actions RunnerGitHub ActionsLinux, x64Your cloud or hardwareEC2 instance$0.002/min fee + AWS cost192 vCPU / 768 GBNot documentedYesNoGermany
WarpBuildGitHub ActionsLinux, macOS, Windows, x64, arm64Vendor-hostedEphemeral VM$0.004/min32 vCPU / 128 GBYesNot documentedNoNot documented
GARM (GitHub Actions Runner Manager)GitHub Actions, Forgejo/Gitea ActionsLinux, Windows, x64, arm64Self-hostedDepends on providerFree software + your infrastructureSet by your infrastructureNot documentedNot documentedYesRomania
Actions Runner Controller (ARC)GitHub ActionsLinux, WindowsSelf-hostedKubernetes podFree software + your infrastructureSet by your infrastructureNot documentedNot documentedYesUnited States
terraform-aws-github-runnerGitHub ActionsLinux, Windows, macOS, x64, arm64Self-hostedEC2 instanceFree software + your infrastructureSet by your infrastructureNot documentedYesYesNot 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

See all Cirun alternatives →

Frequently asked questions

What is 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.
Which CI systems does Cirun work with?
Cirun runs jobs for GitHub Actions, on Linux, macOS, Windows, x64 and arm64.
How does Cirun isolate jobs?
Cirun documents its isolation as: 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 gets a fresh environment that is discarded afterwards.
Is Cirun open source?
No, Cirun is not open source. It does run in your own cloud account or on your own hardware.
How much does Cirun cost?
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. Check the official pricing page for current rates.
How do you set up Cirun?
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. An example label is cirun-gpu-runner--${{ github.run_id }}.
Does Cirun have a free tier?
Free for public repositories, with unlimited runners, ARM and GPU runners on all supported cloud providers.
Does Cirun support ARM64 runners?
Yes, Cirun documents arm64 runners (Linux, macOS and Windows).
Does Cirun offer macOS runners?
Yes, Cirun documents macOS runners alongside Linux and Windows.
Does Cirun cache Docker layers?
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.
Does Cirun offer GPU runners?
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.
How many jobs can run at once on Cirun?
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.
Where do Cirun runners run?
Any region of the connected cloud account, set per runner in .cirun.yml.
Where is Aktech Labs based?
Aktech Labs, the organisation behind Cirun, is headquartered in London, England, United Kingdom. That is where the company is based, not where jobs run; for that, see the regions listed for Cirun.
What are the alternatives to Cirun?

Sources

  1. cirun.io/
  2. cirun.io/pricing
  3. docs.cirun.io/
  4. docs.cirun.io/quickstart
  5. docs.cirun.io/reference/yaml
  6. docs.cirun.io/cloud/
  7. docs.cirun.io/cloud/aws
  8. docs.cirun.io/on-prem
  9. docs.cirun.io/caching/
  10. docs.cirun.io/os-platform/windows
  11. docs.cirun.io/reference/idle-runners
  12. docs.cirun.io/security
  13. docs.cirun.io/terms-of-service
  14. github.com/cirunlabs/cirun-agent
  15. 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/