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

Actuated

Answer in brief

Managed control plane that runs each CI job in a Firecracker microVM on servers you provide, for GitHub Actions and GitLab CI. Actuated is a managed control plane with a host agent that runs each CI job in a single-use microVM on your own servers, suited to teams that want strong isolation and predictable flat pricing.

By the CI Runners editors · Updated

Overview

Actuated is a commercial service from OpenFaaS Ltd that turns servers you supply into CI runner hosts. You install its agent on a bare-metal machine or a VM with nested virtualisation, and its hosted control plane schedules a Firecracker microVM for each queued job. The VM boots a maintained Ubuntu image, runs one build with full root, Docker and Kubernetes available, and is then destroyed. Linux on x86_64 and 64-bit Arm is supported.

Jobs choose their own vCPU and RAM through labels such as actuated-4cpu-16gb rather than fixed sizes. GitLab CI support was announced in July 2024 alongside GitHub Actions. The pricing page lists a flat monthly rate per server with unlimited minutes and concurrency, and the plan includes SSH debugging and Prometheus metrics. The docs list Hetzner, AWS bare metal, GCP, Azure, DigitalOcean and on-premises machines as host options.

Notable

  • Launched in November 2022, according to the two-year review of 6 August 2024, which also announced the move to actuated.com.
  • GitLab CI support was announced on 26 July 2024.
  • A 31 October 2025 post announced auto enrollment, a transparent cache, fractional CPU sizes and custom billing.
  • A 13 October 2025 post announced a Jenkins plugin for Firecracker builds, offered through SlicerVM.com subscriptions.

Actuated specifications

AttributeDetails
CI systemsGitHub Actions, GitLab CI
Operating systemsLinux
Architecturesx64, arm64
DeploymentRuns in your cloud or on your hardware
Where it can runBare metal, Hetzner, AWS, Google Cloud, Azure, DigitalOcean, OpenStack, VMware
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)
Fresh environment per jobYes
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.
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)
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 2025
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.
Docker layer cachingYes
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.
ConcurrencyThe Self-Service plan lists unlimited concurrency; jobs queue once the RAM and CPU of your servers are allocated
Job limitsNot documented
Static IPsNot documented
SSH into running jobsYes
ObservabilityReports across organisation, repositories and users in the dashboard, Prometheus metrics for servers and jobs through a federation endpoint, and a CLI for agent and VM logs.
SetupRegister your GitHub organisation, provision a server with KVM support, install the Actuated agent, then change runs-on to an actuated-* label.
Example labelactuated-4cpu-16gb
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.
Free tierNot documented
ComplianceNot documented
RegionsWherever your servers are; the FAQ says the control plane is hosted in the United Kingdom
Open sourceNo
Company headquartersPeterborough, England, United Kingdom · More from the United Kingdom

Facts from Actuated’s public documentation, verified November 22, 2026. Performance figures are vendor claims.

Strengths and trade-offs

Reasons to choose it

  • 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
  • You want to SSH into a running job to debug it

Trade-offs

  • Windows and macOS are not supported
  • Servers must be bare metal or support nested virtualisation, and Arm hosts must be bare metal
  • You provision, pay for and maintain the servers, and jobs queue when they are full
  • GitHub Enterprise Server is not supported out of the box

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.

Use cases Actuated fits

  • Docker builds: Docker runs natively inside each microVM, and a transparent cache and registry mirror keep layers on local NVMe.
  • ARM64 builds: Arm jobs run natively on bare-metal Arm hosts such as Ampere Altra or Graviton without QEMU.
  • GPU jobs: GPU passthrough to jobs is documented for hosts switched to Cloud Hypervisor.
  • Your own cloud: Jobs run on servers you supply, from on-premises machines to Hetzner bare metal or cloud VMs with nested virtualisation.
  • GitLab CI runners: GitLab CI is supported for GitLab.com and self-managed GitLab, with jobs opted in through an actuated tag.
  • Security and compliance: Each job gets a single-use Firecracker microVM with no access to the host, and the vendor documents use with public repositories.

How Actuated compares

RunnerCI systemsRuns onDeploymentIsolationPriceLargest runnerDocker layer cacheGPUOpen sourceCompany HQ
ActuatedGitHub Actions, GitLab CILinux, x64, arm64Your cloud or hardwareFirecracker microVM$150/mo per server + your serversSet by your infrastructureYesYesNoUnited Kingdom
FireactionsGitHub ActionsLinux, x64, arm64Self-hostedFirecracker microVMFree software + your infrastructureSet by your infrastructureNot documentedNoYesLithuania
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
Ubicloud RunnersGitHub ActionsLinux, x64, arm64Vendor-hostedKVM VM$0.00125/min30 vCPU / 120 GBYesNot documentedYesUnited States
Actions Runner Controller (ARC)GitHub ActionsLinux, WindowsSelf-hostedKubernetes podFree software + your infrastructureSet by your infrastructureNot documentedNot documentedYesUnited States
GitLab RunnerGitLab CILinux, macOS, Windows, x64, arm64Self-hostedDepends on executorFree software + your infrastructureSet by your infrastructureNot documentedYesYesNot 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
BlacksmithGitHub ActionsLinux, macOS, Windows, x64, arm64Vendor-hostedFirecracker microVM$0.004/min32 vCPU / 128 GBYesNot documentedNoUnited States

Head-to-head: Actions Runner Controller (ARC) vs Actuated · Actuated vs Cirun · Actuated vs Fireactions · Actuated vs RunsOn

See all Actuated alternatives →

Frequently asked questions

What is Actuated?
Managed control plane that runs each CI job in a Firecracker microVM on servers you provide, for GitHub Actions and GitLab CI. Actuated is a managed control plane with a host agent that runs each CI job in a single-use microVM on your own servers, suited to teams that want strong isolation and predictable flat pricing.
Which CI systems does Actuated work with?
Actuated runs jobs for GitHub Actions and GitLab CI, on Linux, x64 and arm64.
How does Actuated isolate jobs?
Actuated documents its isolation as: 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 gets a fresh environment that is discarded afterwards.
Is Actuated open source?
No, Actuated is not open source. It does run in your own cloud account or on your own hardware.
How much does Actuated cost?
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. Check the official pricing page for current rates.
How do you set up Actuated?
Register your GitHub organisation, provision a server with KVM support, install the Actuated agent, then change runs-on to an actuated-* label. An example label is actuated-4cpu-16gb.
How fast is 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). Speed figures are the provider’s own and depend on the workload.
Does Actuated support ARM64 runners?
Yes, Actuated documents arm64 runners (Linux).
Does Actuated cache Docker layers?
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.
Does Actuated offer GPU runners?
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.
How many jobs can run at once on Actuated?
The Self-Service plan lists unlimited concurrency; jobs queue once the RAM and CPU of your servers are allocated.
Where do Actuated runners run?
Wherever your servers are; the FAQ says the control plane is hosted in the United Kingdom.
Where is OpenFaaS Ltd based?
OpenFaaS Ltd, the organisation behind Actuated, is headquartered in Peterborough, England, United Kingdom. That is where the company is based, not where jobs run; for that, see the regions listed for Actuated.
What are the alternatives to Actuated?

Sources

  1. actuated.com/
  2. actuated.com/pricing
  3. actuated.com/gitlab
  4. actuated.com/blog
  5. actuated.com/blog/autoenrollment-caching-custom-billing-fractional-cpu
  6. actuated.com/blog/bringing-firecracker-to-jenkins
  7. docs.actuated.com/
  8. docs.actuated.com/faq/
  9. docs.actuated.com/provision-server/
  10. docs.actuated.com/test-build/
  11. docs.actuated.com/examples/gpu/
  12. docs.actuated.com/tasks/debug-ssh/
  13. docs.actuated.com/tasks/local-github-cache/
  14. docs.actuated.com/tasks/monitoring/
  15. docs.actuated.com/roadmap/
  16. github.com/self-actuated/actuated/blob/master/EULA.md

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. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/runners/actuated/