Actuated vs Cirun
Actuated suits teams that want microVM isolation for GitHub Actions or GitLab CI jobs on their own bare-metal or nested-virtualisation servers at a flat monthly rate. 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. Actuated is a product that runs runners in your own cloud account or on your own hardware for GitHub Actions and GitLab CI, priced at $150/mo per server + your servers; 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.
Key differences between Actuated and Cirun
- CI systems: Only Actuated documents GitLab CI.
- Operating systems: Only Cirun documents macOS and Windows.
- Isolation: Actuated: Firecracker microVM. Cirun: Cloud VM.
- Published price: $150/mo per server + your servers (Actuated) versus $29/mo (3 private repos) + cloud cost (Cirun).
What they have in common
- Both companies are based in the United Kingdom.
- 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 give every job a fresh environment.
- Neither is open source.
- Both document Docker layer caching.
- Both document GPU runners.
Actuated vs Cirun at a glance
| Attribute | Actuated | Cirun |
|---|---|---|
| What it is | Managed control plane that runs each CI job in a Firecracker microVM on servers you provide, for GitHub Actions and GitLab CI. | Hosted control plane that launches on-demand GitHub Actions runners in your own cloud accounts or on-prem hardware from a .cirun.yml file. |
| Type | Runs in your cloud or on your hardware | Runs in your cloud or on your hardware |
| CI systems | GitHub Actions, GitLab CI | GitHub Actions |
| Operating systems | Linux | Linux, macOS, Windows |
| Architectures | x64, arm64 | x64, arm64 |
| Isolation | Each job runs in its own Firecracker microVM on your server, created for one build and destroyed afterwards (Cloud Hypervisor is used on GPU hosts) | 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 | Yes |
| Hardware | Your own bare-metal servers or VMs with nested virtualisation; the docs recommend NVMe storage and list Ampere, Graviton and Apple Silicon (Asahi Linux) hosts for Arm. | Any instance type offered by the connected cloud account, or your own Linux (KVM) and Apple Silicon machines through cirun-agent. |
| Performance (vendor claim) | Actuated says builds are often 2-3x faster, and cites a customer Arm build cut from about 6 hours under QEMU to 20 minutes (vendor claim) | Not documented |
| Runner sizes | No fixed sizes: vCPU and RAM are set per job in the label (for example actuated-4cpu-16gb) within the capacity of your server; fractional 0.25 and 0.5 vCPU sizes were announced in October 2025 | Not documented |
| Caching | A transparent cache announced in October 2025 redirects actions/cache, BuildKit and setup-* action caches to local NVMe on your server without workflow changes. The docs also cover a registry mirror and a self-hosted S3 cache (SeaweedFS or MinIO) on the host. | 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 | Yes |
| GPU | GPUs on the host are passed through whole to one job at a time via VFIO, which requires switching the server from Firecracker to Cloud Hypervisor; jobs add a gpu label. | 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 | The Self-Service plan lists unlimited concurrency; jobs queue once the RAM and CPU of your servers are allocated | 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 |
| Static IPs | Not documented | Not documented |
| SSH into running jobs | Yes | Not documented |
| Pricing | Self-Service Plan: flat rate per server, $150 per month for the first and $125 for each additional, with unlimited build minutes, RAM/CPUs and concurrency. Servers are paid for separately. An October 2025 post says custom billing is available to customers needing more than 50 concurrent builds. | 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 | Not documented | Free for public repositories, with unlimited runners, ARM and GPU runners on all supported cloud providers |
| Open source | No | No |
| Self-host / your cloud | No / Yes | Not documented / Yes |
| Compliance | Not documented | Not documented |
| Regions | Wherever your servers are; the FAQ says the control plane is hosted in the United Kingdom | Any region of the connected cloud account, set per runner in .cirun.yml |
| Company headquarters | Peterborough, England, United Kingdom | London, England, United Kingdom |
| Good fit for | Teams that want microVM isolation for GitHub Actions or GitLab CI jobs on their own bare-metal or nested-virtualisation servers at a flat monthly rate | 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 |
Verified November 22, 2026 from each provider’s documentation. Performance figures are vendor claims, not our measurements.
Which should you choose?
Reasons to choose Actuated
- You want each job isolated in its own Firecracker microVM without privileged containers or Docker-in-Docker
- You already have, or want to rent, bare-metal or nested-virtualisation servers and prefer a flat monthly rate per server
- You need native 64-bit Arm builds on hardware such as Ampere or Graviton hosts
- You run GitLab CI as well as GitHub Actions and want the same runner model for both
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
Trade-offs to check first
- Actuated: Windows and macOS are not supported
- Actuated: Servers must be bare metal or support nested virtualisation, and Arm hosts must be bare metal
- 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
Run your slowest workflow on both before deciding. See the full Actuated profile and Cirun profile, or the complete comparison.
More comparisons
Frequently asked questions
Is Actuated or Cirun better?
What is the difference between Actuated and Cirun?
Which is open source, Actuated or Cirun?
How do Actuated and Cirun isolate jobs?
How does Actuated pricing compare with Cirun?
Is Actuated or Cirun faster?
Do Actuated and Cirun cache Docker layers?
Do Actuated and Cirun offer GPU runners?
Where do Actuated and Cirun 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). Actuated vs Cirun. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/compare/actuated-vs-cirun/