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.
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
| Attribute | Details |
|---|---|
| CI systems | GitHub Actions |
| Operating systems | Linux, macOS, Windows |
| Architectures | x64, arm64 |
| Deployment | First-party hosted runners |
| Isolation | 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 |
| Fresh environment per job | Yes |
| Hardware | Azure 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 sizes | Standard: 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 |
| Caching | Dependency 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 caching | Not documented |
| GPU | 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. |
| Concurrency | 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 |
| Job limits | 6 hours of execution per job (15 minutes on ubuntu-slim); 35 days per workflow run; 256 jobs per matrix |
| Static IPs | Yes |
| SSH into running jobs | Not documented |
| Observability | Actions usage metrics and performance metrics (job run time, queue time, failure rate) for organizations and repositories. |
| Setup | 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. |
| Example label | ubuntu-latest |
| Pricing | 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. |
| 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 |
| Compliance | Not documented |
| Regions | 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 |
| Open source | No |
| Company headquarters | San 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
| Runner | CI systems | Runs on | Deployment | Isolation | Price | Largest runner | Docker layer cache | GPU | Open source | Company HQ |
|---|---|---|---|---|---|---|---|---|---|---|
| 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 |
| Blacksmith | GitHub Actions | Linux, macOS, Windows, x64, arm64 | Vendor-hosted | Firecracker microVM | $0.004/min | 32 vCPU / 128 GB | Yes | Not documented | No | United States |
| 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 |
| 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 |
| WarpBuild | GitHub Actions | Linux, macOS, Windows, x64, arm64 | Vendor-hosted | Ephemeral VM | $0.004/min | 32 vCPU / 128 GB | Yes | Not documented | No | Not documented |
| Ubicloud Runners | GitHub Actions | Linux, x64, arm64 | Vendor-hosted | KVM VM | $0.00125/min | 30 vCPU / 120 GB | Yes | Not documented | Yes | United States |
| RunsOn | GitHub Actions | Linux, Windows, x64, arm64 | Your cloud or hardware | EC2 instance | €300/yr licence + AWS cost | 896 vCPU | Yes | Yes | No | France |
| Actions Runner Controller (ARC) | GitHub Actions | Linux, Windows | Self-hosted | Kubernetes pod | Free software + your infrastructure | Set by your infrastructure | Not documented | Not documented | Yes | United States |
| GitLab-hosted runners | GitLab CI | Linux, macOS, Windows, x64, arm64 | Platform-hosted | Ephemeral VM | $10 per 1,000 compute minutes | 32 vCPU / 128 GB | Not documented | Yes | No | Not 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
Frequently asked questions
What is GitHub-hosted runners?
Which CI systems does GitHub-hosted runners work with?
How does GitHub-hosted runners isolate jobs?
Is GitHub-hosted runners open source?
How much does GitHub-hosted runners cost?
How do you set up GitHub-hosted runners?
ubuntu-latest.Does GitHub-hosted runners have a free tier?
Does GitHub-hosted runners support ARM64 runners?
Does GitHub-hosted runners offer macOS runners?
Does GitHub-hosted runners offer GPU runners?
How many jobs can run at once on GitHub-hosted runners?
Where do GitHub-hosted runners runners run?
Where is GitHub, Inc. based?
What are the alternatives to GitHub-hosted runners?
Sources
- docs.github.com/en/billing/reference/actions-runner-pricing
- docs.github.com/en/billing/concepts/product-billing/github-actions
- docs.github.com/en/actions/reference/runners/github-hosted-runners
- docs.github.com/en/actions/reference/runners/larger-runners
- docs.github.com/en/actions/concepts/runners/github-hosted-runners
- docs.github.com/en/actions/reference/limits
- docs.github.com/en/actions/reference/workflows-and-actions/dependency-caching
- docs.github.com/en/actions/reference/security/secure-use
- docs.github.com/en/actions/concepts/metrics
- github.blog/changelog/2025-12-16-coming-soon-simpler-pricing-and-a-better-experience-for-github-actions/
- github.blog/changelog/2026-01-01-reduced-pricing-for-github-hosted-runners-usage/
- github.blog/changelog/2026-01-22-1-vcpu-linux-runner-now-generally-available-in-github-actions/
- github.blog/changelog/2026-01-29-arm64-standard-runners-are-now-available-in-private-repositories/
- github.blog/changelog/2026-10-28-github-actions-adds-multi-cloud-compute-to-improve-reliability/
- 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/