self-host →

Runner capabilities

Compare optional RunsOn runner capabilities across Linux, Windows, Flex, and Fleet.

Capabilities are optional features you can layer on top of a runner. In Flex, a workflow usually opts in with a job label. In Fleet, the platform team enables them on a Terraform-owned runner fleet. Integration-specific guides document exceptions such as Dependabot, which also requires GitHub settings.

Platform availability#

CapabilityLinuxWindowsFlexFleet
Static IPsYesYesYesYes
Nested virtualizationKVM, x64Hyper-V, x64YesYes
Remote accessSSM and SSHSSM and SSHYesYes
AI agentsYesYesYesYes
Local storage (NVMe)Yes, on instance-store types (usually d variants)Yes, on instance-store types (usually d variants)YesYes
YOLO mode (tmpfs)YesNoYesYes
Shared volumes (EFS)YesNoYesNo
Sticky disks (EBS)YesYesYesYes
Docker Hub pull-throughTransparent mirrorExplicit ECR pathsTerraform onlyYes
Local OTEL collectorOTLP/HTTPOTLP/HTTPYesYes

Some capabilities also depend on the selected EC2 instance type, runner image, or stack configuration. Each guide lists those requirements.