Cirun vs machine.dev
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. machine.dev suits teams on GitHub Actions that run GPU workloads such as model tests or fine-tuning in CI, or want spot-priced x64 and arm64 runners on AWS. 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; machine.dev is a managed service hosted by the vendor for GitHub Actions, priced at $0.00297/min on-demand.
Key differences between Cirun and machine.dev
- Type: Cirun is a product that runs runners in your own cloud account or on your own hardware; machine.dev is a managed service hosted by the vendor.
- Operating systems: Only Cirun documents macOS and Windows.
- Isolation: Cirun: Cloud VM. machine.dev: Dedicated AWS instance.
- Published price: $29/mo (3 private repos) + cloud cost (Cirun) versus $0.00297/min on-demand (machine.dev).
- Company headquarters: Aktech Labs is based in London, United Kingdom; MACHINE DOT DEV TRADING PTY LTD is based in Australia.
What they have in common
- 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.
- Both document GPU runners.
Cirun vs machine.dev at a glance
| Attribute | Cirun | machine.dev |
|---|---|---|
| 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. | GPU, x64 and arm64 runners for GitHub Actions on dedicated AWS instances, with spot or on-demand tenancy chosen in the runs-on label. |
| Type | Runs in your cloud or on your hardware | Managed runner service |
| 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 dedicated AWS instance that registers as an ephemeral self-hosted runner and shuts down when the job finishes |
| 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. | AWS instances: x64 (Intel/AMD) and arm64 (Graviton) CPU runners, each with a default 100 GB gp3 EBS volume (6,000 IOPS, 250 MB/s) that can be raised to 16 TB. |
| Performance (vendor claim) | Not documented | machine.dev says a runner goes from push to running job in under 60 seconds without pre-warming (vendor claim) |
| Runner sizes | Not documented | CPU runners from 2 vCPU / 4 GB to 64 vCPU / 128 GB on x64 and arm64; GPU runners from 4 vCPU / 8 GB (T4G) to 192 vCPU / 2,048 GB with 8 RTX 6000 |
| 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. | An Actions cache served from the same AWS region as the runner is in closed beta, available by request: 25 GiB per repository per region with least-recently-used eviction, not billed during the beta. It works with actions/cache v4+ and BuildKit type=gha without workflow changes. |
| 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. | NVIDIA T4G, T4, L4, A10G, L40S and RTX 6000 (up to 8 per runner) plus AWS Trainium and Inferentia2; a 4-vCPU T4G runner is listed from $0.00358/min on spot and $0.01400/min on-demand. |
| 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 | Pay-as-you-go: 1 concurrent runner before a purchase and 5 after; Builder 10, Developer 25, Growth 30, Pro 40, Business 50. Jobs above the cap wait in arrival order for up to six hours |
| 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. | Per-minute USD “from” rates that vary by region. x64 2 vCPU / 4 GB: from $0.00076 spot or $0.00297 on-demand; arm64 2 vCPU / 4 GB: from $0.00040 spot or $0.00241 on-demand; x64 64 vCPU: from $0.01320 spot or $0.09520 on-demand. EBS storage is billed separately at $0.08 per GB-month, prorated to runtime; optional monthly plans from $25 to $300 add bonus credit and higher concurrency. |
| Free tier | Free for public repositories, with unlimited runners, ARM and GPU runners on all supported cloud providers | $10 of free compute on signup; before any purchase, one job at a time and 30 minutes per job |
| Open source | No | No |
| Self-host / your cloud | Not documented / Yes | No / Not documented |
| Compliance | Not documented | Not documented |
| Regions | Any region of the connected cloud account, set per runner in .cirun.yml | Six AWS regions: us-east-1, us-east-2, us-west-2, ca-central-1, eu-south-2 and ap-southeast-2, selectable with a regions= option in the label; GPU availability varies by type |
| Company headquarters | London, England, United Kingdom | Queensland, Australia |
| 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 run GPU workloads such as model tests or fine-tuning in CI, or want spot-priced x64 and arm64 runners on AWS |
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 machine.dev
- You need NVIDIA GPUs in GitHub Actions jobs, from a T4G up to 8 RTX 6000 on one runner
- You want to choose spot or on-demand tenancy per job in the runs-on label
- You need to pin jobs to specific AWS regions, such as eu-south-2 for EU data residency
- You want x64 or Graviton arm64 CPU runners up to 64 vCPU with a configurable EBS volume
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
- machine.dev: A spot job interrupted while running is not re-run or resumed automatically
- machine.dev: Runners share outbound IP addresses with other jobs (FAQ)
Run your slowest workflow on both before deciding. See the full Cirun profile and machine.dev profile, or the complete comparison.
More comparisons
Frequently asked questions
Is Cirun or machine.dev better?
What is the difference between Cirun and machine.dev?
Which is open source, Cirun or machine.dev?
How do Cirun and machine.dev isolate jobs?
How does Cirun pricing compare with machine.dev?
Is Cirun or machine.dev faster?
Do Cirun and machine.dev cache Docker layers?
Do Cirun and machine.dev offer GPU runners?
Where do Cirun and machine.dev 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 machine.dev. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/compare/cirun-vs-machine/