Depot GitHub Actions Runners vs Namespace
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. Namespace suits teams on GitHub Actions or Buildkite that want VM-isolated Linux, macOS and Windows runners with persistent cache volumes and fine-grained machine shapes. Depot GitHub Actions Runners is a managed service hosted by the vendor for GitHub Actions, priced at $0.006/min; Namespace is a managed service hosted by the vendor for GitHub Actions and Buildkite, priced at $0.002/min prepaid, $0.003/min overage (2 vCPU / 4 GB).
Key differences between Depot GitHub Actions Runners and Namespace
- CI systems: Only Namespace documents Buildkite.
- Isolation: Depot GitHub Actions Runners: Single-tenant EC2 instance. Namespace: Virtual machine.
- Published price: $0.006/min (Depot GitHub Actions Runners) versus $0.002/min prepaid, $0.003/min overage (2 vCPU / 4 GB) (Namespace).
- Largest runner: 64 vCPU / 256 GB (Depot GitHub Actions Runners) versus 64 vCPU / 512 GB (Namespace).
What they have in common
- Both are managed services hosted by the vendor.
- 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 Docker layer caching.
Depot GitHub Actions Runners vs Namespace at a glance
| Attribute | Depot GitHub Actions Runners | Namespace |
|---|---|---|
| What it is | Managed GitHub Actions runners on single-tenant AWS EC2 instances, connected to Depot’s cache and container build service. | Managed runners for GitHub Actions and Buildkite on the vendor’s own hardware, configured through profiles with persistent cache volumes. |
| Type | Managed runner service | Managed runner service |
| CI systems | GitHub Actions | GitHub Actions, Buildkite |
| 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 | Every job runs in its own instance inside a virtual machine that is discarded when the job ends; the hypervisor is not named |
| 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. | Namespace says it deploys its own hardware in its own racks: AMD EPYC for Linux and Windows amd64, AmpereOne for Linux arm64 (Linux on Apple Silicon is in early access), and Apple M4 Pro and M5 Max for macOS. |
| 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 | Linux up to 64 vCPU and 512 GB RAM, Windows up to 32 vCPU and 512 GB, macOS up to 16 vCPU and 56 GB; standard label shapes run from 2 vCPU / 4 GB to 32 vCPU / 64 GB, and instances over 64 GB RAM need special access |
| 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. | Cache Volumes persist data across runs; a runner profile can cache container images, toolchain downloads, action downloads and Git checkouts, and nscloud-cache-action replaces actions/cache. Docker builds go to Remote Builders with layer caching by default, and there are cache integrations for Bazel, Turborepo, Pants and Moonrepo. |
| Docker layer caching | Yes | Yes |
| GPU | Depot’s docs list GPU-enabled runners as available on the Business plan only; models and prices are not published. | Not documented |
| Concurrency | Unlimited concurrency on all plans; macOS runners come from a fixed pool, so jobs can queue when demand spikes | Per plan: Developer 32 Linux vCPU and 12 macOS vCPU; Team 64 Linux, 24 macOS and 32 Windows vCPU; Business 160 Linux, 48 macOS and 80 Windows vCPU; custom on Enterprise |
| Static IPs | Yes | Yes |
| SSH into running jobs | Not documented | Yes |
| 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. | Billed in unit minutes (vCPU × minutes × platform multiplier: Linux 1, Windows 2, macOS 10), with a 1-minute minimum. Team is $100/month with 100,000 unit minutes and Business $250/month with 250,000; Developer is pay as you go. A 2 vCPU / 4 GB Linux runner is listed at $0.002/min prepaid and $0.003/min overage, 2 vCPU / 8 GB at $0.004 and $0.006, and macOS 6 vCPU / 14 GB at $0.06 and $0.09. Cache volume storage is $0.0048/GB-day on Developer, with free allowances on Team and Business. |
| Free tier | 7-day free trial, no credit card required | 30-day free trial of Developer plan features, no credit card required |
| Open source | No | No |
| Self-host / your cloud | No / Yes | No / Not documented |
| Compliance | SOC 2 Type 2 | SOC 2 Type II |
| 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 | Specific regions are not named; Namespace says it runs its own hardware at multiple sites, offers a regional preference on all plans and region-exclusive residency on enterprise plans |
| Company headquarters | Not documented | Not documented |
| 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 or Buildkite that want VM-isolated Linux, macOS and Windows runners with persistent cache volumes and fine-grained machine shapes |
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 Namespace
- You want each job in its own virtual machine that is discarded when the job ends
- You want cache volumes that persist container images, toolchains, action downloads and Git checkouts between runs
- You need Linux, macOS and Windows runners, with Linux shapes up to 64 vCPU and 512 GB RAM
- You run Buildkite as well as GitHub Actions and want one provider for both
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
- Namespace: Concurrency is capped per plan, for example 32 Linux vCPU on Developer and 64 on Team
- Namespace: Maximum instance duration is 3 hours on Developer and 5 hours on Team
Run your slowest workflow on both before deciding. See the full Depot GitHub Actions Runners profile and Namespace profile, or the complete comparison.
More comparisons
Frequently asked questions
Is Depot GitHub Actions Runners or Namespace better?
What is the difference between Depot GitHub Actions Runners and Namespace?
Which is open source, Depot GitHub Actions Runners or Namespace?
How do Depot GitHub Actions Runners and Namespace isolate jobs?
How does Depot GitHub Actions Runners pricing compare with Namespace?
Is Depot GitHub Actions Runners or Namespace faster?
Do Depot GitHub Actions Runners and Namespace cache Docker layers?
Do Depot GitHub Actions Runners and Namespace offer GPU runners?
Where do Depot GitHub Actions Runners and Namespace runners run?
Sources
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 Namespace. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/compare/depot-vs-namespace/