CI Runnerscirunners.org
Use case · Security and compliance

Choosing a runner for untrusted code and compliance

Answer in brief

A CI runner executes code from your repository with access to your secrets, so treat it as part of your supply chain. Look for a fresh, single-use VM for every job, an isolation boundary you can name (a microVM or VM rather than a shared container host), network controls such as static egress IPs or private networking, and compliance reports that cover the runner fleet. Never attach persistent self-hosted runners to public repositories.

By the CI Runners editors · Updated

What security-sensitive pipelines need from a runner

  • Ephemeral runners: each job gets a new machine that is destroyed afterwards, so nothing leaks between jobs or pull requests.
  • Isolation boundary: a hardware-virtualised VM or microVM per job is a stronger boundary than containers sharing a kernel.
  • Public repositories: a pull request from a fork can run arbitrary code on your runner. GitHub says self-hosted runners should almost never be used for public repositories for this reason.
  • Network control: static egress IPs for allow-lists, private connectivity to your network, and ideally egress filtering or monitoring.
  • Cache isolation: caches shared across branches or repositories are a poisoning path.
  • Compliance and data location: SOC 2 or ISO 27001 reports, the regions jobs run in, and a data processing agreement.

See the runner security guide.

Runners that fit, by kind

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

  • Avrea

    Managed GitHub Actions runners for Linux, macOS and Windows on dedicated hardware, with colocated caches and SSH into running jobs.

    • Per-job VM
    • Ephemeral
    • arm64
    • macOS
    • Windows
    • Docker layer cache

    Why it fits: Per-job VMs, repository-scoped caches, an egress firewall, ISO/IEC 27001:2022 certification and a SOC 2 Type II attestation are documented.

  • 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: Each job gets an isolated VM, a recorded SBOM and network trace, and an egress policy checked before it starts; CRACI states ISO/IEC 27001 certification.

  • 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: Each job gets a never-reused single-tenant EC2 instance, with egress filtering on all plans and SOC 2 Type 2 compliance stated.

  • 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: Each job runs in its own discarded VM, and egress policies can restrict outbound traffic per runner profile; SOC 2 Type II is stated.

  • 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

    Why it fits: Each job runs in its own KVM virtual machine with an ephemeral filesystem, and Puzl states SOC 2 Type II and GDPR compliance.

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: Each job gets a single-use Firecracker microVM with no access to the host, and the vendor documents use with public repositories.

  • HyperEnv for GitHub Actions Runner

    AWS Marketplace product that runs each GitHub Actions job on an ephemeral EC2 instance, deployed entirely inside your own AWS account.

    • EC2 instance
    • Ephemeral
    • GPU
    • BYOC
    • Self-hostable

    Why it fits: Each job runs on a single-use instance inside your VPC, and the vendor states ISO 27001 certification.

  • 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: Runners can be confined to private subnets with static egress IPs, and each job gets a single-use instance.

  • 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: Each job gets a new instance with no ingress, and Sprinters documents having no access to repository contents, secrets or instance logins.

Open-source autoscalers for self-hosted runners

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

  • Fireactions

    Orchestrator that runs self-hosted GitHub Actions runners in ephemeral Firecracker microVMs on your own Linux hosts.

    • Firecracker microVM
    • Ephemeral
    • arm64
    • Open source
    • BYOC
    • Self-hostable

    Why it fits: Each job runs in its own Firecracker microVM, which the docs recommend for untrusted workloads such as CI jobs.

macOS runners for iOS and Mac builds

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

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
AvreaGitHub ActionsLinux, macOS, Windows, x64, arm64Vendor-hostedPer-job VM$0.004/min32 vCPU / 128 GBYesNot documentedNoFinland
AWS CodeBuild-hosted runnersGitHub Actions, GitLab CI, BuildkiteLinux, Windows, x64, arm64Your cloud accountFresh build environment$0.005/min72 vCPU / 144 GBYesYesNoUnited States
Bitrise Build HubGitHub ActionsmacOS, Linux, arm64, x64Vendor-hostedVirtual machine$0.00625/min16 vCPU / 64 GBNot documentedNot documentedNoNot documented
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
FireactionsGitHub ActionsLinux, x64, arm64Self-hostedFirecracker microVMFree software + your infrastructureSet by your infrastructureNot documentedNoYesLithuania
GitHub-hosted runnersGitHub ActionsLinux, macOS, Windows, x64, arm64Platform-hostedFresh VM$0.006/min96 vCPU / 384 GBNot documentedYesNoUnited States
HyperEnv for GitHub Actions RunnerGitHub ActionsLinux, x64Your cloud or hardwareEC2 instance$0.002/min fee + AWS cost192 vCPU / 768 GBNot documentedYesNoGermany
Managed DevOps PoolsAzure PipelinesLinux, Windows, x64Platform-hostedAzure VM$15/month per parallel job + Azure VM costNot documentedNot documentedNot documentedNoUnited States
Microsoft-hosted agentsAzure PipelinesLinux, macOS, Windows, x64Platform-hostedFresh VM$40/month per parallel job2 vCPU / 7 GBNot documentedNot documentedNoUnited 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
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

Frequently asked questions

Are self-hosted runners safe for public repositories?
Not persistent ones. Anyone who can open a pull request can run code on the runner, and a persistent machine keeps whatever that code leaves behind. GitHub’s documentation says self-hosted runners should almost never be used for public repositories. If you must, use ephemeral runners that give every job a fresh VM and require approval for workflows from outside contributors. See the runner security guide.
What should I check before sending my code to a third-party runner?
How jobs are isolated from other customers (ideally a dedicated VM or microVM per job), whether runners are single-use, where the machines are located, which compliance reports the vendor can share, how caches are scoped, and what the GitHub App’s permissions allow.

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 untrusted code and compliance. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/use-cases/security/