CI Runnerscirunners.org
Use case · GPU jobs

Choosing a runner for GPU jobs

Answer in brief

GPU runners are for testing ML models, CUDA builds, rendering and inference checks in CI. Only some providers offer them. Compare the GPU model and memory, the per-minute price, whether drivers and CUDA come preinstalled, and availability. Running GPU jobs in your own cloud account is the alternative when you need a specific instance type or have GPU quota already.

By the CI Runners editors · Updated

What GPU jobs need from a runner

  • GPU model and VRAM: enough memory for the model or test you run.
  • Drivers and toolkits: NVIDIA drivers, CUDA and the container toolkit preinstalled, or a way to bring your own image.
  • Price and granularity: GPU minutes cost far more than CPU minutes, so per-second billing and fast start-up matter.
  • Availability: GPU capacity is scarcer than CPU capacity. Check queue behaviour.
  • Your own cloud: bring-your-own-cloud and open-source autoscalers can launch any GPU instance type your account has quota for.

Runners that fit, by kind

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

  • 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: Six NVIDIA GPU tiers and AWS Trainium and Inferentia2 runners are listed with CUDA and drivers preinstalled.

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: GPU passthrough to jobs is documented for hosts switched to Cloud Hypervisor.

  • 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: GPU runner groups are available for model training and inference tests.

  • 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: GPU runners are included in every plan and the docs show GPU instances on Google Cloud and Vast.ai as a provider.

  • 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: g4dn instance types with an NVIDIA T4 GPU can be selected per job.

  • 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: GPU images with NVIDIA drivers and CUDA are published for x64 and Graviton GPU instances.

Open-source autoscalers for self-hosted runners

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

  • GitLab Runner

    The open-source agent that runs GitLab CI/CD jobs, with executors for Docker, Kubernetes, shell and autoscaled cloud instances.

    • Depends on executor
    • arm64
    • macOS
    • Windows
    • GPU
    • Open source
    • BYOC
    • Self-hostable

    Why it fits: GPU configuration is documented for the Shell, Docker and Kubernetes executors.

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
CirunGitHub ActionsLinux, macOS, Windows, x64, arm64Your cloud or hardwareCloud VM$29/mo (3 private repos) + cloud costSet by your infrastructureYesYesNoUnited Kingdom
GitHub-hosted runnersGitHub ActionsLinux, macOS, Windows, x64, arm64Platform-hostedFresh VM$0.006/min96 vCPU / 384 GBNot documentedYesNoUnited States
GitLab RunnerGitLab CILinux, macOS, Windows, x64, arm64Self-hostedDepends on executorFree software + your infrastructureSet by your infrastructureNot documentedYesYesNot documented
GitLab-hosted runnersGitLab CILinux, macOS, Windows, x64, arm64Platform-hostedEphemeral VM$10 per 1,000 compute minutes32 vCPU / 128 GBNot documentedYesNoNot documented
HyperEnv for GitHub Actions RunnerGitHub ActionsLinux, x64Your cloud or hardwareEC2 instance$0.002/min fee + AWS cost192 vCPU / 768 GBNot documentedYesNoGermany
machine.devGitHub ActionsLinux, x64, arm64Vendor-hostedDedicated AWS instance$0.00297/min on-demand64 vCPU / 128 GBNot documentedYesNoAustralia
RunsOnGitHub ActionsLinux, Windows, x64, arm64Your cloud or hardwareEC2 instance€300/yr licence + AWS cost896 vCPUYesYesNoFrance

Frequently asked questions

Can GitHub Actions run jobs on a GPU?
Yes. GitHub offers GPU-powered larger runners, some third-party vendors offer GPU runners, and self-hosted or bring-your-own-cloud runners can use any GPU instance in your cloud account. The list on this page shows the runners that document GPU support.

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 GPU jobs. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/use-cases/gpu/