CI Runnerscirunners.org
Runner profile · First-party hosted runners

GitHub-hosted runners

Answer in brief

GitHub’s own Actions runners: a new VM per job on Linux, Windows and macOS, with larger, arm64 and GPU sizes billed per minute. The default runners for GitHub Actions, suited to teams that prefer zero setup and to public repositories, with larger sizes available per minute on paid plans.

By the CI Runners editors · Updated

Overview

GitHub-hosted runners are the machines GitHub provides for GitHub Actions jobs. A workflow selects one with a runs-on label such as ubuntu-latest, and GitHub starts a new virtual machine for the job from an image it maintains in the runner-images repository. Standard runners cover Linux, Windows and macOS on x64 and arm64. They are free in public repositories and draw on a monthly included amount in private ones.

Organizations on GitHub Team or Enterprise Cloud can also create larger runners: 2 to 96 vCPU machines, GPU machines, static IP ranges, Azure private networking and custom images, all billed per minute, including in public repositories. A 1-vCPU ubuntu-slim runner, generally available since January 2026, runs short automation jobs in a container. Since October 2026 eligible Linux jobs may run on AWS as well as Azure.

Notable

  • GitHub reduced GitHub-hosted runner prices by up to 39% on January 1, 2026; a $0.002 per-minute charge for self-hosted runners announced on December 16, 2025 was postponed
  • Linux and Windows arm64 standard runners became available in private repositories on January 29, 2026
  • The 1-vCPU ubuntu-slim runner became generally available on January 22, 2026
  • On October 28, 2026 GitHub began scheduling eligible Linux jobs across a multi-cloud pool that includes AWS

GitHub-hosted runners specifications

AttributeDetails
CI systemsGitHub Actions
Operating systemsLinux, macOS, Windows
Architecturesx64, arm64
DeploymentFirst-party hosted runners
IsolationEach job runs in a new virtual machine hosted by GitHub; the 1-vCPU ubuntu-slim runner instead runs in an unprivileged container on a shared VM
Fresh environment per jobYes
HardwareAzure virtual machines, with eligible 2-core and 4-core Linux jobs also scheduled on AWS; standard macOS runners are 3-core M1 or 4-core Intel, and the macOS XLarge runner is a 5-core M2
Performance (vendor claim)Not documented
Runner sizesStandard: 1 vCPU / 5 GB (ubuntu-slim); 2 vCPU / 8 GB in private and 4 vCPU / 16 GB in public repositories on Linux and Windows, x64 and arm64. Larger runners: 2 to 96 vCPU on x64 and 2 to 64 vCPU on arm64; macOS 3 to 12 cores
CachingDependency caching through the cache action, with 10 GB per repository included; entries not accessed for 7 days are removed and the oldest are evicted at the limit. The limit can be raised, billed at $0.07 per GB per month. Larger runners can use custom VM images.
Docker layer cachingNot documented
GPUGPU larger runners have 4 vCPU, 28 GB RAM and one Tesla T4 with 16 GB VRAM, at $0.052/min on Linux and $0.102/min on Windows.
ConcurrencyStandard runners: 20 concurrent jobs on Free, 40 on Pro, 60 on Team and 500 on Enterprise, of which 5 macOS (50 on Enterprise). Larger runners: up to 1,000 concurrent jobs and 100 GPU jobs
Job limits6 hours of execution per job (15 minutes on ubuntu-slim); 35 days per workflow run; 256 jobs per matrix
Static IPsYes
SSH into running jobsNot documented
ObservabilityActions usage metrics and performance metrics (job run time, queue time, failure rate) for organizations and repositories.
SetupNothing to install: set runs-on to a GitHub-hosted label. Larger runners are created by an organization or enterprise owner on GitHub Team or Enterprise Cloud and need a payment method on file.
Example labelubuntu-latest
PricingPrivate repositories, per minute: Linux 2-core x64 $0.006, Linux 2-core arm64 $0.005, Linux 1-core $0.002, Windows 2-core $0.010, macOS 3- or 4-core $0.062. Larger Linux x64 runners run from $0.012 (4-core) to $0.252 (96-core); larger macOS runners are $0.077 (12-core Intel) and $0.102 (M2 Pro). Usage is rounded up to the whole minute.
Free tierStandard runners are free in public repositories. Private repositories get $12 of included compute usage per month on GitHub Free, $18 on Pro and Team, and $300 on Enterprise Cloud
ComplianceNot documented
RegionsRegions are not documented for github.com. GitHub says Windows runners and other Linux runners run on Microsoft Azure, eligible Linux jobs on Azure or AWS, and macOS runners in Azure data centers
Open sourceNo
Company headquartersSan Francisco, California, United States · More from the United States

Facts from GitHub-hosted runners’s public documentation, verified November 22, 2026. Performance figures are vendor claims.

Strengths and trade-offs

Reasons to choose it

  • You want runners that need no installation or account beyond GitHub itself
  • You maintain public repositories, where standard runners are free
  • You need Linux, Windows and macOS, on x64 and arm64, from one provider
  • You want every job to start in a clean VM that is not reused
  • You need GPU machines or static IP ranges without operating your own runners

Trade-offs

  • Larger runners are billed in public repositories and need a GitHub Team or Enterprise Cloud plan
  • Jobs are limited to 6 hours of execution time
  • Standard runners have 14 GB of SSD storage and at most 4 vCPU
  • Static IP addresses and Azure private networking are not available for macOS runners

Good fit for: Teams on GitHub Actions that want runners with no setup, and public repositories that can use the free standard runners.

Use cases GitHub-hosted runners fits

  • ARM64 builds: Linux and Windows arm64 standard runners are available in public and private repositories, with larger arm64 runners up to 64 vCPU.
  • macOS and iOS builds: macOS runners are offered on M1, M2 and Intel hardware with macOS 15 and 26 images and an Xcode 27 image.
  • Windows builds: Windows Server 2022 and 2025 and Windows 11 arm64 images are available on standard and larger runners.
  • GPU jobs: Larger runners include a 4-vCPU Tesla T4 machine on Linux and Windows.
  • Security and compliance: GitHub documents its hosted runners as clean, ephemeral virtual machines and says self-hosted runners should almost never be used for public repositories.

How GitHub-hosted runners compares

RunnerCI systemsRuns onDeploymentIsolationPriceLargest runnerDocker layer cacheGPUOpen sourceCompany HQ
GitHub-hosted runnersGitHub ActionsLinux, macOS, Windows, x64, arm64Platform-hostedFresh VM$0.006/min96 vCPU / 384 GBNot documentedYesNoUnited States
BlacksmithGitHub ActionsLinux, macOS, Windows, x64, arm64Vendor-hostedFirecracker microVM$0.004/min32 vCPU / 128 GBYesNot documentedNoUnited States
Depot GitHub Actions RunnersGitHub ActionsLinux, macOS, Windows, x64, arm64Vendor-hostedSingle-tenant EC2 instance$0.006/min64 vCPU / 256 GBYesYesNoNot documented
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
WarpBuildGitHub ActionsLinux, macOS, Windows, x64, arm64Vendor-hostedEphemeral VM$0.004/min32 vCPU / 128 GBYesNot documentedNoNot documented
Ubicloud RunnersGitHub ActionsLinux, x64, arm64Vendor-hostedKVM VM$0.00125/min30 vCPU / 120 GBYesNot documentedYesUnited States
RunsOnGitHub ActionsLinux, Windows, x64, arm64Your cloud or hardwareEC2 instance€300/yr licence + AWS cost896 vCPUYesYesNoFrance
Actions Runner Controller (ARC)GitHub ActionsLinux, WindowsSelf-hostedKubernetes podFree software + your infrastructureSet by your infrastructureNot documentedNot documentedYesUnited States
GitLab-hosted runnersGitLab CILinux, macOS, Windows, x64, arm64Platform-hostedEphemeral VM$10 per 1,000 compute minutes32 vCPU / 128 GBNot documentedYesNoNot documented

Head-to-head: Actions Runner Controller (ARC) vs GitHub-hosted runners · Blacksmith vs GitHub-hosted runners · Depot GitHub Actions Runners vs GitHub-hosted runners · GitHub-hosted runners vs GitLab-hosted runners · GitHub-hosted runners vs Namespace · GitHub-hosted runners vs Ubicloud Runners · GitHub-hosted runners vs WarpBuild

See all GitHub-hosted runners alternatives →

Frequently asked questions

What is 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. The default runners for GitHub Actions, suited to teams that prefer zero setup and to public repositories, with larger sizes available per minute on paid plans.
Which CI systems does GitHub-hosted runners work with?
GitHub-hosted runners runs jobs for GitHub Actions, on Linux, macOS, Windows, x64 and arm64.
How does GitHub-hosted runners isolate jobs?
GitHub-hosted runners documents its isolation as: Each job runs in a new virtual machine hosted by GitHub; the 1-vCPU ubuntu-slim runner instead runs in an unprivileged container on a shared VM. Each job gets a fresh environment that is discarded afterwards.
Is GitHub-hosted runners open source?
No, GitHub-hosted runners is not open source.
How much does GitHub-hosted runners cost?
Private repositories, per minute: Linux 2-core x64 $0.006, Linux 2-core arm64 $0.005, Linux 1-core $0.002, Windows 2-core $0.010, macOS 3- or 4-core $0.062. Larger Linux x64 runners run from $0.012 (4-core) to $0.252 (96-core); larger macOS runners are $0.077 (12-core Intel) and $0.102 (M2 Pro). Usage is rounded up to the whole minute. Check the official pricing page for current rates.
How do you set up GitHub-hosted runners?
Nothing to install: set runs-on to a GitHub-hosted label. Larger runners are created by an organization or enterprise owner on GitHub Team or Enterprise Cloud and need a payment method on file. An example label is ubuntu-latest.
Does GitHub-hosted runners have a free tier?
Standard runners are free in public repositories. Private repositories get $12 of included compute usage per month on GitHub Free, $18 on Pro and Team, and $300 on Enterprise Cloud.
Does GitHub-hosted runners support ARM64 runners?
Yes, GitHub-hosted runners documents arm64 runners (Linux, macOS and Windows).
Does GitHub-hosted runners offer macOS runners?
Yes, GitHub-hosted runners documents macOS runners alongside Linux and Windows.
Does GitHub-hosted runners offer GPU runners?
GPU larger runners have 4 vCPU, 28 GB RAM and one Tesla T4 with 16 GB VRAM, at $0.052/min on Linux and $0.102/min on Windows.
How many jobs can run at once on GitHub-hosted runners?
Standard runners: 20 concurrent jobs on Free, 40 on Pro, 60 on Team and 500 on Enterprise, of which 5 macOS (50 on Enterprise). Larger runners: up to 1,000 concurrent jobs and 100 GPU jobs.
Where do GitHub-hosted runners runners run?
Regions are not documented for github.com. GitHub says Windows runners and other Linux runners run on Microsoft Azure, eligible Linux jobs on Azure or AWS, and macOS runners in Azure data centers.
Where is GitHub, Inc. based?
GitHub, Inc., the organisation behind GitHub-hosted runners, is headquartered in San Francisco, California, United States. That is where the company is based, not where jobs run; for that, see the regions listed for GitHub-hosted runners.
What are the alternatives to GitHub-hosted runners?

Sources

  1. docs.github.com/en/billing/reference/actions-runner-pricing
  2. docs.github.com/en/billing/concepts/product-billing/github-actions
  3. docs.github.com/en/actions/reference/runners/github-hosted-runners
  4. docs.github.com/en/actions/reference/runners/larger-runners
  5. docs.github.com/en/actions/concepts/runners/github-hosted-runners
  6. docs.github.com/en/actions/reference/limits
  7. docs.github.com/en/actions/reference/workflows-and-actions/dependency-caching
  8. docs.github.com/en/actions/reference/security/secure-use
  9. docs.github.com/en/actions/concepts/metrics
  10. github.blog/changelog/2025-12-16-coming-soon-simpler-pricing-and-a-better-experience-for-github-actions/
  11. github.blog/changelog/2026-01-01-reduced-pricing-for-github-hosted-runners-usage/
  12. github.blog/changelog/2026-01-22-1-vcpu-linux-runner-now-generally-available-in-github-actions/
  13. github.blog/changelog/2026-01-29-arm64-standard-runners-are-now-available-in-private-repositories/
  14. github.blog/changelog/2026-10-28-github-actions-adds-multi-cloud-compute-to-improve-reliability/
  15. docs.github.com/en/site-policy/privacy-policies/github-general-privacy-statement

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). GitHub-hosted runners. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/runners/github-hosted-runners/