Depot GitHub Actions Runners vs GitHub-hosted runners
Depot GitHub Actions Runners suits teams on GitHub Actions that want single-tenant EC2 runners alongside a shared build cache and remote container builds from the same vendor. GitHub-hosted runners suits teams on GitHub Actions that want runners with no setup, and public repositories that can use the free standard runners. Depot GitHub Actions Runners is a managed service hosted by the vendor for GitHub Actions, priced at $0.006/min; GitHub-hosted runners is the CI platform’s own hosted runners for GitHub Actions, priced at $0.006/min.
Key differences between Depot GitHub Actions Runners and GitHub-hosted runners
- Type: Depot GitHub Actions Runners is a managed service hosted by the vendor; GitHub-hosted runners is the CI platform’s own hosted runners.
- Isolation: Depot GitHub Actions Runners: Single-tenant EC2 instance. GitHub-hosted runners: Fresh VM.
- Largest runner: 64 vCPU / 256 GB (Depot GitHub Actions Runners) versus 96 vCPU / 384 GB (GitHub-hosted runners).
- Your own cloud account: Depot GitHub Actions Runners documents running in your own cloud account; GitHub-hosted runners does not.
What they have in common
- Both run GitHub Actions jobs.
- Both document Linux, macOS and Windows runners.
- Both document arm64 runners.
- Both use a virtual machine per runner.
- Both give every job a fresh environment.
- Neither is open source.
- Both document GPU runners.
Depot GitHub Actions Runners vs GitHub-hosted runners at a glance
| Attribute | Depot GitHub Actions Runners | GitHub-hosted runners |
|---|---|---|
| What it is | Managed GitHub Actions runners on single-tenant AWS EC2 instances, connected to Depot’s cache and container build service. | GitHub’s own Actions runners: a new VM per job on Linux, Windows and macOS, with larger, arm64 and GPU sizes billed per minute. |
| Type | Managed runner service | First-party hosted runners |
| CI systems | GitHub Actions | GitHub Actions |
| Operating systems | Linux, macOS, Windows | Linux, macOS, Windows |
| Architectures | x64, arm64 | x64, arm64 |
| Isolation | Each job runs on a new single-tenant EC2 instance that has never been used before and is destroyed when the job completes | 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 | Yes |
| Hardware | AWS EC2 instances: 4th Gen AMD EPYC Genoa for x64 Linux, Graviton4 for arm64, Intel for Windows, and Apple M2 (macOS 14 and 15) or M4 (macOS 26) for macOS; part of the memory is used as a RAM disk on Linux and macOS. | 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) | Depot says its runners are up to 3x faster than GitHub-hosted runners, with 10x faster caching (vendor claim) | Not documented |
| Runner sizes | 2 to 64 vCPU with 8 to 256 GB RAM on Linux x64, Linux arm64 and Windows; macOS runners are 8 vCPU with 24 GB | 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 | Runners are preconfigured to use Depot Cache as the GitHub Actions cache backend (14-day retention and no size limit by default); it also serves Bazel, Go, Gradle, Turborepo, Nx, sccache and Pants. Docker layer caching comes from Depot’s separately metered container build service, which keeps a persistent layer cache on NVMe SSDs for each project. | 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 | Yes | Not documented |
| GPU | Depot’s docs list GPU-enabled runners as available on the Business plan only; models and prices are not published. | 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 | Unlimited concurrency on all plans; macOS runners come from a fixed pool, so jobs can queue when demand spikes | 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 |
| Static IPs | Yes | Yes |
| SSH into running jobs | Not documented | Not documented |
| Pricing | Plans: Developer at $20/month with 2,000 GitHub Actions minutes and 25 GB of cache, Startup at $200/month with 20,000 minutes and 250 GB, Business custom. Additional minutes cost $0.006/min for the 2-vCPU Linux runner (x64 or arm64), scaling with size to $0.192/min at 64 vCPU; the runner-types page lists Windows from $0.008/min and macOS at $0.08/min. Usage is tracked per second with no one-minute minimum, and extra cache storage is $0.20/GB/month. | 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 | 7-day free trial, no credit card required | 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 |
| Open source | No | No |
| Self-host / your cloud | No / Yes | No / No |
| Compliance | SOC 2 Type 2 | Not documented |
| Regions | Depot says it runs on AWS in the United States, and in the European Union when a project selects the EU region; the runner docs do not name specific 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 |
| Company headquarters | Not documented | San Francisco, California, United States |
| Good fit for | Teams on GitHub Actions that want single-tenant EC2 runners alongside a shared build cache and remote container builds from the same vendor | Teams on GitHub Actions that want runners with no setup, and public repositories that can use the free standard runners |
Verified November 22, 2026 from each provider’s documentation. Performance figures are vendor claims, not our measurements.
Which should you choose?
Reasons to choose Depot GitHub Actions Runners
- You want every job on a fresh single-tenant EC2 instance that is destroyed afterwards
- You want per-second usage tracking with no one-minute minimum
- You need large Linux runners: up to 64 vCPU and 256 GB RAM on x64 and arm64
- You already use, or plan to use, Depot’s container builds and remote cache with the same account
Reasons to choose GitHub-hosted runners
- 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
Trade-offs to check first
- Depot GitHub Actions Runners: Plans start at $20/month after a 7-day trial; a permanent free allowance is not documented
- Depot GitHub Actions Runners: Only repositories owned by GitHub organizations are supported
- GitHub-hosted runners: Larger runners are billed in public repositories and need a GitHub Team or Enterprise Cloud plan
- GitHub-hosted runners: Jobs are limited to 6 hours of execution time
Run your slowest workflow on both before deciding. See the full Depot GitHub Actions Runners profile and GitHub-hosted runners profile, or the complete comparison.
More comparisons
- Blacksmith vs Depot GitHub Actions Runners
- Depot GitHub Actions Runners vs Namespace
- Depot GitHub Actions Runners vs Ubicloud Runners
- Depot GitHub Actions Runners vs WarpBuild
- Actions Runner Controller (ARC) vs GitHub-hosted runners
- Blacksmith 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
Is Depot GitHub Actions Runners or GitHub-hosted runners better?
What is the difference between Depot GitHub Actions Runners and GitHub-hosted runners?
Which is open source, Depot GitHub Actions Runners or GitHub-hosted runners?
How do Depot GitHub Actions Runners and GitHub-hosted runners isolate jobs?
How does Depot GitHub Actions Runners pricing compare with GitHub-hosted runners?
Is Depot GitHub Actions Runners or GitHub-hosted runners faster?
Do Depot GitHub Actions Runners and GitHub-hosted runners cache Docker layers?
Do Depot GitHub Actions Runners and GitHub-hosted runners offer GPU runners?
Where do Depot GitHub Actions Runners and GitHub-hosted runners runners run?
Sources
- depot.dev/pricing
- depot.dev/docs/github-actions/overview
- depot.dev/docs/github-actions/runner-types
- depot.dev/docs/github-actions/quickstart
- 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
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). Depot GitHub Actions Runners vs GitHub-hosted runners. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/compare/depot-vs-github-hosted-runners/