CI Runnerscirunners.org
Alternatives

CRACI alternatives

Answer in brief

The 8 alternatives below are grouped by kind of runner, and each says whom it suits. Start from the requirement that matters most to you: price per minute, operating systems, caching, isolation or where the runners have to run.

By the CI Runners editors · Updated

CRACI trade-offs to weigh

A European managed runner service for GitHub Actions that pairs per-job virtual machines with SBOM, provenance and egress-policy features, suited to teams with supply-chain or data-location requirements.

  • Runs Linux jobs only; macOS and Windows jobs stay on other runners (quickstart)
  • GitHub Actions is the only CI system supported today
  • While on free credits, jobs can use 8 vCPUs in total at a time
  • An SBOM may be incomplete when a job restores dependencies from a cache

CRACI alternatives, by kind

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

    Whom it suits: Teams on GitHub Actions that want microVM-isolated runners on bare metal with built-in Docker layer caching and CI observability. A managed GitHub Actions runner service on vendor-owned bare metal with microVM isolation, suited to organizations that want faster hardware plus integrated caching and observability.

  • 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

    Whom it suits: Teams on GitHub Actions that want single-tenant EC2 runners alongside a shared build cache and remote container builds from the same vendor. A managed GitHub Actions runner service built on single-tenant AWS instances, suited to teams that also want Depot’s cache and container build service.

  • 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

    Whom it suits: Teams on GitHub Actions or Buildkite that want VM-isolated Linux, macOS and Windows runners with persistent cache volumes and fine-grained machine shapes. A managed runner platform for GitHub Actions and Buildkite on vendor-operated hardware, suited to teams that want per-job VMs, persistent cache volumes and all three operating systems.

  • RunJob

    EU-based managed runners for GitHub Actions and GitLab CI that run each job in a fresh KVM virtual machine and bill only CPU and memory used.

    • KVM virtual machine
    • Ephemeral
    • GPU

    Whom it suits: Teams on GitLab CI or GitHub Actions that want EU-hosted runners billed by actual CPU and memory use instead of by runner size. An EU-based managed runner service for GitLab CI and GitHub Actions with usage-metered billing and one KVM virtual machine per job, suited to teams whose jobs spend much of their time below peak load.

  • 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

    Whom it suits: Teams on GitHub Actions that want low per-minute Linux runners in European data centers from a vendor whose cloud platform is open source. A low-priced managed Linux runner service for GitHub Actions built on an open-source cloud, suited to teams that want x64 and arm64 runners in Europe.

  • 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

    Whom it suits: Teams on GitHub Actions that want managed runners now with the option to move the same setup into their own AWS, Google Cloud or Azure account. A managed GitHub Actions runner service with a bring-your-own-cloud option, suited to teams that want hosted runners with a path to running them in their own cloud account.

Runners from your CI platform or cloud

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

  • GitHub-hosted runners

    GitHub’s own Actions runners: a new VM per job on Linux, Windows and macOS, with larger, arm64 and GPU sizes billed per minute.

    • Fresh VM
    • Ephemeral
    • arm64
    • macOS
    • Windows
    • GPU

    Whom it suits: Teams on GitHub Actions that want runners with no setup, and public repositories that can use the free standard runners. The default runners for GitHub Actions, suited to teams that prefer zero setup and to public repositories, with larger sizes available per minute on paid plans.

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

    Whom it 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. 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.

CRACI vs alternatives

RunnerCI systemsRuns onDeploymentIsolationPriceLargest runnerDocker layer cacheGPUOpen sourceCompany HQ
CRACIGitHub ActionsLinux, x64, arm64Vendor-hostedPer-job VM€0.004/min32 vCPU / 96 GBNot documentedNot documentedNoFinland
ActuatedGitHub Actions, GitLab CILinux, x64, arm64Your cloud or hardwareFirecracker microVM$150/mo per server + your serversSet by your infrastructureYesYesNoUnited Kingdom
BlacksmithGitHub ActionsLinux, macOS, Windows, x64, arm64Vendor-hostedFirecracker microVM$0.004/min32 vCPU / 128 GBYesNot documentedNoUnited States
Depot GitHub Actions RunnersGitHub ActionsLinux, macOS, Windows, x64, arm64Vendor-hostedSingle-tenant EC2 instance$0.006/min64 vCPU / 256 GBYesYesNoNot documented
GitHub-hosted runnersGitHub ActionsLinux, macOS, Windows, x64, arm64Platform-hostedFresh VM$0.006/min96 vCPU / 384 GBNot documentedYesNoUnited States
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
RunJobGitHub Actions, GitLab CILinux, x64Vendor-hostedKVM virtual machine€0.00002 per vCPU-second used48 vCPU / 96 GBNoYesNoEstonia
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

Head-to-head: Blacksmith vs CRACI

Frequently asked questions

What are the main alternatives to CRACI?
Actuated, Blacksmith, Depot GitHub Actions Runners, GitHub-hosted runners, Namespace, RunJob, Ubicloud Runners, WarpBuild. Which one fits depends on your pipeline; each entry above says whom it suits.
Is there an open-source alternative to CRACI?

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). CRACI alternatives. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/alternatives/craci/