CI Runnerscirunners.org
Use case · Windows builds

Choosing a runner for Windows builds

Answer in brief

Windows runners are needed for .NET Framework, C++ with MSVC, game engines and desktop apps. Fewer providers offer them than Linux, they cost more per minute, and Windows machines start more slowly. Check which Windows Server version and toolchains are preinstalled, the per-minute rate and whether you can bring your own image.

By the CI Runners editors · Updated

What Windows builds need from a runner

  • Image contents: Visual Studio build tools, .NET SDKs and Windows SDK versions preinstalled, and how often the image is refreshed.
  • Price: Windows minutes cost more than Linux minutes; on GitHub the 2-core Windows rate is $0.010 a minute against $0.006 for Linux.
  • Start-up time: Windows VMs boot slowly; ask whether runners are prewarmed.
  • Custom images: large toolchains (game engines, proprietary SDKs) are impractical to install on every run.
  • Your own cloud: bring-your-own-cloud products can launch Windows instances from your own images, with the licence included in the instance price.

Runners that fit, by kind

13 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: Windows 2025 runners are offered from 2 to 16 vCPU.

  • 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

    Why it fits: Windows Server 2025 x64 runners from 2 to 32 vCPU are offered in public beta.

  • 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: Windows amd64 runners on AMD EPYC are included in the Team and Business plans.

  • 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

    Why it fits: Windows Server 2022 and 2025 x64 runners from 4 to 32 vCPU are offered.

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.

  • 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: Windows runners are documented on AWS and Azure, including ARM64 on Azure.

  • 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: Windows Server 2025 images are provided for x64 runners.

Open-source autoscalers for self-hosted runners

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

Side by side

RunnerCI systemsRuns onDeploymentIsolationPriceLargest runnerDocker layer cacheGPUOpen sourceCompany HQ
AvreaGitHub ActionsLinux, macOS, Windows, x64, arm64Vendor-hostedPer-job VM$0.004/min32 vCPU / 128 GBYesNot documentedNoFinland
BlacksmithGitHub ActionsLinux, macOS, Windows, x64, arm64Vendor-hostedFirecracker microVM$0.004/min32 vCPU / 128 GBYesNot documentedNoUnited States
Buildkite hosted agentsBuildkiteLinux, macOS, Windows, x64, arm64Platform-hostedEphemeral virtualized environment$0.008/min64 vCPU / 256 GBYesNot documentedNoNot documented
CirunGitHub ActionsLinux, macOS, Windows, x64, arm64Your cloud or hardwareCloud VM$29/mo (3 private repos) + cloud costSet by your infrastructureYesYesNoUnited Kingdom
Elastic CI Stack for AWSBuildkiteLinux, Windows, x64, arm64Self-hostedEC2 instanceFree software + your infrastructureSet by your infrastructureNot documentedNot documentedYesAustralia
GARM (GitHub Actions Runner Manager)GitHub Actions, Forgejo/Gitea ActionsLinux, Windows, x64, arm64Self-hostedDepends on providerFree software + your infrastructureSet by your infrastructureNot documentedNot documentedYesRomania
GitHub-hosted runnersGitHub ActionsLinux, macOS, Windows, x64, arm64Platform-hostedFresh VM$0.006/min96 vCPU / 384 GBNot documentedYesNoUnited States
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
RunsOnGitHub ActionsLinux, Windows, x64, arm64Your cloud or hardwareEC2 instance€300/yr licence + AWS cost896 vCPUYesYesNoFrance
terraform-aws-github-runnerGitHub ActionsLinux, Windows, macOS, x64, arm64Self-hostedEC2 instanceFree software + your infrastructureSet by your infrastructureNot documentedYesYesNot documented
WarpBuildGitHub ActionsLinux, macOS, Windows, x64, arm64Vendor-hostedEphemeral VM$0.004/min32 vCPU / 128 GBYesNot documentedNoNot documented

Frequently asked questions

Which third-party runners support Windows?
Fewer than support Linux. The list on this page shows the runners whose documentation covers Windows; the first-party runners of GitHub, GitLab and Azure Pipelines all do, and bring-your-own-cloud products can launch Windows instances in your cloud account.

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 Windows builds. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/use-cases/windows/