CI Runnerscirunners.org
Head-to-head

Actuated vs RunsOn

Answer in brief

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. 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. 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; 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 Actuated and RunsOn

  • CI systems: Only Actuated documents GitLab CI.
  • Operating systems: Only RunsOn documents Windows.
  • Isolation: Actuated: Firecracker microVM. RunsOn: EC2 instance.
  • Published price: $150/mo per server + your servers (Actuated) versus €300/yr licence + AWS cost (RunsOn).
  • Self-hosting: RunsOn documents a self-hosted option; Actuated does not.
  • Company headquarters: OpenFaaS Ltd is based in Peterborough, 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 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 RunsOn at a glance

AttributeActuatedRunsOn
What it isManaged control plane that runs each CI job in a Firecracker microVM on servers you provide, for GitHub Actions and GitLab CI.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 Actions, GitLab CIGitHub Actions
Operating systemsLinuxLinux, Windows
Architecturesx64, arm64x64, arm64
IsolationEach 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 on an EC2 instance that no other job has used and that is terminated when the job ends
Fresh environment per jobYesYes
HardwareYour 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 EC2 instance family selected by label, including Graviton and families with local NVMe; the docs cite 1 to 896 vCPUs.
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)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)
Runner sizesNo 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 2025Predefined 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
CachingA 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.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
GPUGPUs 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 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.
ConcurrencyThe Self-Service plan lists unlimited concurrency; jobs queue once the RAM and CPU of your servers are allocatedNo 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 jobsYesYes
PricingSelf-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.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 tierNot documentedFree 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 cloudNo / YesYes / Yes
ComplianceNot documentedNot documented
RegionsWherever your servers are; the FAQ says the control plane is hosted in the United KingdomNot documented
Company headquartersPeterborough, England, United KingdomThorigné-Fouillard, Brittany, France
Good fit forTeams that want microVM isolation for GitHub Actions or GitLab CI jobs on their own bare-metal or nested-virtualisation servers at a flat monthly rateTeams 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 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 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

  • Actuated: Windows and macOS are not supported
  • Actuated: Servers must be bare metal or support nested virtualisation, and Arm hosts must be bare metal
  • 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 Actuated profile and RunsOn profile, or the complete comparison.

More comparisons

Frequently asked questions

Is Actuated or RunsOn better?
Neither is better for every pipeline. 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. 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 Actuated and RunsOn?
Only Actuated documents GitLab CI. Only RunsOn documents Windows. Isolation is Firecracker microVM on Actuated and EC2 instance on RunsOn. Published price: $150/mo per server + your servers (Actuated) versus €300/yr licence + AWS cost (RunsOn). RunsOn documents a self-hosted option; Actuated does not.
Which is open source, Actuated or RunsOn?
Neither is open source.
How do Actuated and RunsOn isolate jobs?
Actuated: 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). RunsOn: Each job runs on an EC2 instance that no other job has used and that is terminated when the job ends.
How does Actuated pricing compare with RunsOn?
Actuated: 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. 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 Actuated and RunsOn pricing pages before deciding.
Is Actuated or RunsOn faster?
We have not benchmarked them, and speed depends on the workload. What each provider says: Actuated: 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). 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 Actuated and RunsOn cache Docker layers?
Actuated: 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. 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 Actuated and RunsOn offer GPU runners?
Actuated: 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. 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 Actuated and RunsOn runners run?
Actuated is a product that runs runners in your own cloud account or on your own hardware (Bare metal, Hetzner, AWS, Google Cloud, Azure, DigitalOcean, OpenStack and VMware). RunsOn is a product that runs runners in your own cloud account or on your own hardware (AWS).

Sources

  1. actuated.com/
  2. actuated.com/pricing
  3. actuated.com/gitlab
  4. actuated.com/blog
  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). Actuated vs RunsOn. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/compare/actuated-vs-runs-on/