Choosing a runner for untrusted code and compliance
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.
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.
Full profile →Depot GitHub Actions Runners alternativesWebsite ↗
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.
AWS CodeBuild-hosted runners
AWS CodeBuild projects that start a single-use runner in your AWS account for each GitHub Actions, GitLab or Buildkite job.
- Fresh build environment
- Ephemeral
- arm64
- Windows
- Docker layer cache
- GPU
- BYOC
Why it fits: Each job runs in a fresh build environment that AWS says is isolated from other users and discarded on completion.
Full profile →AWS CodeBuild-hosted runners alternativesWebsite ↗
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
Why it fits: GitHub documents its hosted runners as clean, ephemeral virtual machines and says self-hosted runners should almost never be used for public repositories.
Managed DevOps Pools
Azure service that runs autoscaled Azure Pipelines agents on VM sizes and images you choose, billed at standard Azure rates.
- Azure VM
- Windows
Why it fits: Stateless pools give every job a new agent, and Microsoft recommends them as a defense against supply chain attacks.
Microsoft-hosted agents
Azure Pipelines’ built-in agents: a fresh 2-core VM per job on Windows, Linux or macOS, sold per parallel job rather than per minute.
- Fresh VM
- Ephemeral
- macOS
- Windows
Why it fits: Microsoft documents that each VM is reimaged after each run and says hosted agents are safer than self-hosted agents for untrusted code such as fork contributions.
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.
Full profile →HyperEnv for GitHub Actions Runner alternativesWebsite ↗
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.
Bitrise Build Hub
Bitrise-managed macOS and Linux runners for GitHub Actions on Bitrise-owned Apple silicon and AMD EPYC machines, sold as monthly compute budgets.
- Virtual machine
- Ephemeral
- arm64
- macOS
Why it fits: Bitrise states SOC 2 Type II and PCI DSS compliance and offers US and EU data centre locations.
Side by side
| Runner | CI systems | Runs on | Deployment | Isolation | Price | Largest runner | Docker layer cache | GPU | Open source | Company HQ |
|---|---|---|---|---|---|---|---|---|---|---|
| Actuated | GitHub Actions, GitLab CI | Linux, x64, arm64 | Your cloud or hardware | Firecracker microVM | $150/mo per server + your servers | Set by your infrastructure | Yes | Yes | No | United Kingdom |
| Avrea | GitHub Actions | Linux, macOS, Windows, x64, arm64 | Vendor-hosted | Per-job VM | $0.004/min | 32 vCPU / 128 GB | Yes | Not documented | No | Finland |
| AWS CodeBuild-hosted runners | GitHub Actions, GitLab CI, Buildkite | Linux, Windows, x64, arm64 | Your cloud account | Fresh build environment | $0.005/min | 72 vCPU / 144 GB | Yes | Yes | No | United States |
| Bitrise Build Hub | GitHub Actions | macOS, Linux, arm64, x64 | Vendor-hosted | Virtual machine | $0.00625/min | 16 vCPU / 64 GB | Not documented | Not documented | No | Not documented |
| CRACI | GitHub Actions | Linux, x64, arm64 | Vendor-hosted | Per-job VM | €0.004/min | 32 vCPU / 96 GB | Not documented | Not documented | No | Finland |
| Depot GitHub Actions Runners | GitHub Actions | Linux, macOS, Windows, x64, arm64 | Vendor-hosted | Single-tenant EC2 instance | $0.006/min | 64 vCPU / 256 GB | Yes | Yes | No | Not documented |
| Fireactions | GitHub Actions | Linux, x64, arm64 | Self-hosted | Firecracker microVM | Free software + your infrastructure | Set by your infrastructure | Not documented | No | Yes | Lithuania |
| GitHub-hosted runners | GitHub Actions | Linux, macOS, Windows, x64, arm64 | Platform-hosted | Fresh VM | $0.006/min | 96 vCPU / 384 GB | Not documented | Yes | No | United States |
| HyperEnv for GitHub Actions Runner | GitHub Actions | Linux, x64 | Your cloud or hardware | EC2 instance | $0.002/min fee + AWS cost | 192 vCPU / 768 GB | Not documented | Yes | No | Germany |
| Managed DevOps Pools | Azure Pipelines | Linux, Windows, x64 | Platform-hosted | Azure VM | $15/month per parallel job + Azure VM cost | Not documented | Not documented | Not documented | No | United States |
| Microsoft-hosted agents | Azure Pipelines | Linux, macOS, Windows, x64 | Platform-hosted | Fresh VM | $40/month per parallel job | 2 vCPU / 7 GB | Not documented | Not documented | No | United States |
| Namespace | GitHub Actions, Buildkite | Linux, macOS, Windows, x64, arm64 | Vendor-hosted | Virtual machine | $0.002/min prepaid, $0.003/min overage (2 vCPU / 4 GB) | 64 vCPU / 512 GB | Yes | Not documented | No | Not documented |
| RunJob | GitHub Actions, GitLab CI | Linux, x64 | Vendor-hosted | KVM virtual machine | €0.00002 per vCPU-second used | 48 vCPU / 96 GB | No | Yes | No | Estonia |
| RunsOn | GitHub Actions | Linux, Windows, x64, arm64 | Your cloud or hardware | EC2 instance | €300/yr licence + AWS cost | 896 vCPU | Yes | Yes | No | France |
| Sprinters | GitHub Actions | Linux, x64, arm64 | Your cloud or hardware | EC2 instance | $0.01/job + AWS cost | 384 vCPU / 3072 GB | Not documented | Not documented | No | Germany |
Frequently asked questions
Are self-hosted runners safe for public repositories?
What should I check before sending my code to a third-party runner?
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/