CI Runnerscirunners.org
Use case · ARM64 builds

Choosing a runner for native ARM64 builds

Answer in brief

If you ship to AWS Graviton, Ampere, Apple silicon or other arm64 targets, build on native arm64 runners. Emulating arm64 on x64 with QEMU works but is many times slower. Arm64 runners are widely available and are usually priced below x64 runners of the same size. Check the sizes offered, whether your toolchain has arm64 binaries, and how multi-platform Docker images are assembled.

By the CI Runners editors · Updated

What ARM64 builds need from a runner

  • Native hardware: an arm64 runner compiles and tests arm64 code directly, with no emulation.
  • Sizes: arm64 ranges are sometimes narrower than x64 ranges. Check the largest size if you build large projects.
  • Toolchain coverage: confirm that the actions and tools you use publish arm64 builds.
  • Multi-platform images: build each architecture natively in its own job and merge the manifests, rather than emulating one inside the other.
  • Price: arm64 minutes are typically cheaper per core than x64.

Runners that fit, by kind

24 runners document what this workload needs. They are grouped by kind and listed alphabetically; the order is not a ranking. Shortlist two or three, then try them with your own workflows.

Managed runners for GitHub Actions

Third-party runners you switch to by changing the runs-on label in a workflow.

  • Blacksmith

    Managed GitHub Actions runners in Firecracker microVMs on the vendor’s own bare-metal fleet, with caches kept next to the runners.

    • Firecracker microVM
    • Ephemeral
    • arm64
    • macOS
    • Windows
    • Docker layer cache

    Why it fits: Native arm64 Linux runners from 2 to 32 vCPU are listed at $0.0025/min.

  • BuildPulse Runners

    Managed Linux runners for GitHub Actions, CircleCI and Semaphore with included cache storage and flaky-test detection on every run.

    • Fresh per-job runner
    • Ephemeral
    • arm64
    • Docker layer cache

    Why it fits: arm64 runners on Graviton are offered in the same vCPU sizes as x64, from $0.0025 per minute at 2 vCPU.

  • CRACI

    Managed Linux runners for GitHub Actions on European bare metal that record a build-time SBOM and apply an egress policy to each job.

    • Per-job VM
    • arm64

    Why it fits: A full Ubuntu 24.04 image is available for native ARM64 builds at the same per-vCPU rate as x86-64.

  • Depot GitHub Actions Runners

    Managed GitHub Actions runners on single-tenant AWS EC2 instances, connected to Depot’s cache and container build service.

    • Single-tenant EC2 instance
    • Ephemeral
    • arm64
    • macOS
    • Windows
    • Docker layer cache
    • GPU
    • BYOC

    Why it fits: Graviton4 arm64 runners from 2 to 64 vCPU are priced the same as x64.

  • machine.dev

    GPU, x64 and arm64 runners for GitHub Actions on dedicated AWS instances, with spot or on-demand tenancy chosen in the runs-on label.

    • Dedicated AWS instance
    • Ephemeral
    • arm64
    • GPU

    Why it fits: Graviton arm64 CPU runners from 2 to 64 vCPU are selected with an architecture=arm64 option.

  • Namespace

    Managed runners for GitHub Actions and Buildkite on the vendor’s own hardware, configured through profiles with persistent cache volumes.

    • Virtual machine
    • Ephemeral
    • arm64
    • macOS
    • Windows
    • Docker layer cache

    Why it fits: Linux arm64 runners use AmpereOne processors, with Linux on Apple Silicon in early access.

  • Ubicloud Runners

    Managed Linux runners for GitHub Actions from an open-source cloud platform that runs on leased bare metal.

    • KVM VM
    • Ephemeral
    • arm64
    • Docker layer cache
    • Open source
    • Self-hostable

    Why it fits: Ampere Altra arm64 runners from 2 to 30 vCPU are priced the same as standard x64 runners.

  • WarpBuild

    Managed GitHub Actions runners in ephemeral VMs, also offered as a deployment in your own AWS, Google Cloud or Azure account.

    • Ephemeral VM
    • Ephemeral
    • arm64
    • macOS
    • Windows
    • Docker layer cache
    • BYOC

    Why it fits: Linux arm64 runners from 2 to 32 vCPU start at $0.003/min, with Apple Silicon “xfast” variants.

Runners from your CI platform or cloud

The first-party hosted runners of GitHub, GitLab, Buildkite and Azure, plus cloud-native runner services.

Runners in your own cloud or on your hardware

Commercial products that launch runners inside your cloud account or on servers you own.

  • Actuated

    Managed control plane that runs each CI job in a Firecracker microVM on servers you provide, for GitHub Actions and GitLab CI.

    • Firecracker microVM
    • Ephemeral
    • arm64
    • Docker layer cache
    • GPU
    • BYOC

    Why it fits: Arm jobs run natively on bare-metal Arm hosts such as Ampere Altra or Graviton without QEMU.

  • Aspect Workflows

    Bazel-focused platform whose auto-scaling CI runners register with your existing CI and can run in your own AWS account or GCP project.

    • Persistent VM
    • arm64
    • GPU
    • BYOC
    • Self-hostable

    Why it fits: Runner groups can use Arm instance types alongside x86 groups.

  • 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.

    • Cloud VM
    • Ephemeral
    • arm64
    • macOS
    • Windows
    • Docker layer cache
    • GPU
    • BYOC

    Why it fits: ARM-based runners are included in every plan and the on-prem Docker runner image is multi-arch.

  • enomem

    Self-hosted GitHub Actions runners on Azure: an Azure Functions handler in your subscription starts one Spot VM per job.

    • Azure VM
    • Ephemeral
    • arm64
    • Docker layer cache
    • BYOC
    • Self-hostable

    Why it fits: ARM64 aliases run on Azure Cobalt D-series sizes from 2 to 16 vCPU.

  • RunsOn

    Self-hosted GitHub Actions runner control plane installed in your own AWS account, launching one fresh EC2 instance per job.

    • EC2 instance
    • Ephemeral
    • arm64
    • Windows
    • Docker layer cache
    • GPU
    • BYOC
    • Self-hostable

    Why it fits: Ubuntu arm64 images run on Graviton instance families selected by label.

  • Sprinters

    GitHub App that launches one ephemeral EC2 instance per GitHub Actions job in your own AWS account, charged per job rather than per minute.

    • EC2 instance
    • Ephemeral
    • arm64
    • BYOC

    Why it fits: Ubuntu arm64 images run on Graviton instance types such as t4g and m8gd.

Open-source autoscalers for self-hosted runners

Software you deploy to run and scale self-hosted runners on Kubernetes, cloud VMs or bare metal.

macOS runners for iOS and Mac builds

Apple-silicon runners and virtualization tools for building and testing iOS and macOS apps.

  • Tart

    Virtualization toolset for macOS and Linux VMs on Apple silicon, with OCI-registry images and the Orchard orchestrator for clusters of Macs.

    • Apple Virtualization VM
    • Ephemeral
    • arm64
    • macOS
    • BYOC
    • Self-hostable

    Why it fits: Tart also runs arm64 Linux VMs (Ubuntu, Debian, Fedora images) on Apple silicon hosts.

Side by side

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
Aspect WorkflowsGitHub Actions, Buildkite, GitLab CI, CircleCILinux, x64, arm64Your cloud or hardwarePersistent VMAnnual platform fee (quote) + cloud costSet by your infrastructureNot documentedYesNoNot documented
AWS CodeBuild-hosted runnersGitHub Actions, GitLab CI, BuildkiteLinux, Windows, x64, arm64Your cloud accountFresh build environment$0.005/min72 vCPU / 144 GBYesYesNoUnited States
BlacksmithGitHub ActionsLinux, macOS, Windows, x64, arm64Vendor-hostedFirecracker microVM$0.004/min32 vCPU / 128 GBYesNot documentedNoUnited States
Buildkite hosted agentsBuildkiteLinux, macOS, Windows, x64, arm64Platform-hostedEphemeral virtualized environment$0.008/min64 vCPU / 256 GBYesNot documentedNoNot documented
BuildPulse RunnersGitHub Actions, CircleCI, SemaphoreLinux, x64, arm64Vendor-hostedFresh per-job runner$0.004/min64 vCPU / 256 GBYesNot documentedNoNot documented
CirunGitHub ActionsLinux, macOS, Windows, x64, arm64Your cloud or hardwareCloud VM$29/mo (3 private repos) + cloud costSet by your infrastructureYesYesNoUnited Kingdom
CRACIGitHub ActionsLinux, x64, arm64Vendor-hostedPer-job VM€0.004/min32 vCPU / 96 GBNot documentedNot documentedNoFinland
Depot GitHub Actions RunnersGitHub ActionsLinux, macOS, Windows, x64, arm64Vendor-hostedSingle-tenant EC2 instance$0.006/min64 vCPU / 256 GBYesYesNoNot documented
Elastic CI Stack for AWSBuildkiteLinux, Windows, x64, arm64Self-hostedEC2 instanceFree software + your infrastructureSet by your infrastructureNot documentedNot documentedYesAustralia
enomemGitHub ActionsLinux, x64, arm64Your cloud or hardwareAzure VM$25/mo licence + Azure cost96 vCPU / 384 GBYesNot documentedNot documentedNot documented
FireactionsGitHub ActionsLinux, x64, arm64Self-hostedFirecracker microVMFree software + your infrastructureSet by your infrastructureNot documentedNoYesLithuania
GARM (GitHub Actions Runner Manager)GitHub Actions, Forgejo/Gitea ActionsLinux, Windows, x64, arm64Self-hostedDepends on providerFree software + your infrastructureSet by your infrastructureNot documentedNot documentedYesRomania
GitHub-hosted runnersGitHub ActionsLinux, macOS, Windows, x64, arm64Platform-hostedFresh VM$0.006/min96 vCPU / 384 GBNot documentedYesNoUnited States
GitLab-hosted runnersGitLab CILinux, macOS, Windows, x64, arm64Platform-hostedEphemeral VM$10 per 1,000 compute minutes32 vCPU / 128 GBNot documentedYesNoNot documented
machine.devGitHub ActionsLinux, x64, arm64Vendor-hostedDedicated AWS instance$0.00297/min on-demand64 vCPU / 128 GBNot documentedYesNoAustralia
NamespaceGitHub Actions, BuildkiteLinux, macOS, Windows, x64, arm64Vendor-hostedVirtual machine$0.002/min prepaid, $0.003/min overage (2 vCPU / 4 GB)64 vCPU / 512 GBYesNot documentedNoNot documented
RunsOnGitHub ActionsLinux, Windows, x64, arm64Your cloud or hardwareEC2 instance€300/yr licence + AWS cost896 vCPUYesYesNoFrance
SprintersGitHub ActionsLinux, x64, arm64Your cloud or hardwareEC2 instance$0.01/job + AWS cost384 vCPU / 3072 GBNot documentedNot documentedNoGermany
TartGitLab CI, Buildkite, GitHub ActionsmacOS, Linux, arm64Your cloud or hardwareApple Virtualization VMNot documentedSet by your infrastructureNot documentedNot documentedNoUnited States
terraform-aws-github-runnerGitHub ActionsLinux, Windows, macOS, x64, arm64Self-hostedEC2 instanceFree software + your infrastructureSet by your infrastructureNot documentedYesYesNot documented
TestFlows GitHub Hetzner RunnersGitHub ActionsLinux, x64, arm64Self-hostedHetzner Cloud VMFree software + your infrastructureSet by your infrastructureYesNot documentedYesNot documented
Ubicloud RunnersGitHub ActionsLinux, x64, arm64Vendor-hostedKVM VM$0.00125/min30 vCPU / 120 GBYesNot documentedYesUnited States
WarpBuildGitHub ActionsLinux, macOS, Windows, x64, arm64Vendor-hostedEphemeral VM$0.004/min32 vCPU / 128 GBYesNot documentedNoNot documented

Frequently asked questions

Should I build ARM64 images with QEMU or native runners?
Native runners. QEMU emulation lets an x64 runner build arm64 images, but compilation under emulation is many times slower. With arm64 runners you build each architecture natively and combine the results into one multi-platform image.

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). Choosing a runner for native ARM64 builds. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/use-cases/arm64/