CI Runnerscirunners.org
Runner profile · Managed runner service

Depot GitHub Actions Runners

Answer in brief

Managed GitHub Actions runners on single-tenant AWS EC2 instances, connected to Depot’s cache and container build service. A managed GitHub Actions runner service built on single-tenant AWS instances, suited to teams that also want Depot’s cache and container build service.

By the CI Runners editors · Updated

Overview

Depot GitHub Actions Runners are managed runners that replace GitHub-hosted ones through a runs-on label such as depot-ubuntu-24.04. GitHub still orchestrates the workflow; Depot receives the job webhook and assigns a fresh EC2 instance from a standby pool, then terminates it when the job completes. Linux runners use AMD EPYC Genoa or Graviton4 processors in sizes from 2 to 64 vCPU, and Windows and macOS runners are also offered.

Runners are one part of a wider platform: they are preconfigured for Depot Cache and sit in the same private network as Depot’s remote container builders, which keep Docker layers on persistent NVMe storage. Billing is by plan with included minutes, tracked per second. Egress filtering is available on all plans, while static outbound IPs, GPU runners, custom images and deployment in your own AWS account are Business-plan features. Only repositories owned by GitHub organizations are supported.

Notable

  • Depot was incorporated in January 2022 and launched publicly in July 2022, according to its about page.
  • Depot completed a $4.1M seed round in August 2024.
  • Depot raised a $10M Series A in March 2026.

Depot GitHub Actions Runners specifications

AttributeDetails
CI systemsGitHub Actions
Operating systemsLinux, macOS, Windows
Architecturesx64, arm64
DeploymentManaged runner service · BYOC available
Where it can runAWS
IsolationEach job runs on a new single-tenant EC2 instance that has never been used before and is destroyed when the job completes
Fresh environment per jobYes
HardwareAWS 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.
Performance (vendor claim)Depot says its runners are up to 3x faster than GitHub-hosted runners, with 10x faster caching (vendor claim)
Runner sizes2 to 64 vCPU with 8 to 256 GB RAM on Linux x64, Linux arm64 and Windows; macOS runners are 8 vCPU with 24 GB
CachingRunners 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.
Docker layer cachingYes
GPUDepot’s docs list GPU-enabled runners as available on the Business plan only; models and prices are not published.
ConcurrencyUnlimited concurrency on all plans; macOS runners come from a fixed pool, so jobs can queue when demand spikes
Job limitsNot documented
Static IPsYes
SSH into running jobsNot documented
ObservabilityGitHub Actions analytics with CPU and memory utilisation, runner sizing recommendations, step-level timing, failure rates and live runner status.
SetupConnect a GitHub organization by installing the Depot GitHub App from the Depot dashboard (organization owner role required), then change runs-on to a Depot label. Repositories owned by personal accounts are not supported.
Example labeldepot-ubuntu-24.04
PricingPlans: 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.
Free tier7-day free trial, no credit card required
ComplianceSOC 2 Type 2
RegionsDepot 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
Open sourceNo
Company headquartersNot documented

Facts from Depot GitHub Actions Runners’s public documentation, verified November 22, 2026. Performance figures are vendor claims.

Strengths and trade-offs

Reasons to choose it

  • 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
  • You may later need the runners in your own AWS account, which Depot offers on its Business plan

Trade-offs

  • Plans start at $20/month after a 7-day trial; a permanent free allowance is not documented
  • Only repositories owned by GitHub organizations are supported
  • macOS capacity is a fixed pool, so macOS jobs can queue when demand spikes
  • Windows runners have no Hyper-V, so Docker-dependent workloads are unlikely to work

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.

Use cases Depot GitHub Actions Runners fits

  • Faster builds: Depot says its runners are up to 3x faster than GitHub-hosted runners and come preconfigured for its distributed cache (vendor claim).
  • Docker builds: Depot’s container build service keeps a persistent Docker layer cache on NVMe SSDs and is used from Actions through depot/build-push-action.
  • ARM64 builds: Graviton4 arm64 runners from 2 to 64 vCPU are priced the same as x64.
  • Your own cloud: Depot’s docs say runners can run in its cloud or in your AWS account, the latter on the Business plan.
  • Security and compliance: Each job gets a never-reused single-tenant EC2 instance, with egress filtering on all plans and SOC 2 Type 2 compliance stated.

How Depot GitHub Actions Runners compares

RunnerCI systemsRuns onDeploymentIsolationPriceLargest runnerDocker layer cacheGPUOpen sourceCompany HQ
Depot GitHub Actions RunnersGitHub ActionsLinux, macOS, Windows, x64, arm64Vendor-hostedSingle-tenant EC2 instance$0.006/min64 vCPU / 256 GBYesYesNoNot documented
BlacksmithGitHub ActionsLinux, macOS, Windows, x64, arm64Vendor-hostedFirecracker microVM$0.004/min32 vCPU / 128 GBYesNot 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
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
GitHub-hosted runnersGitHub ActionsLinux, macOS, Windows, x64, arm64Platform-hostedFresh VM$0.006/min96 vCPU / 384 GBNot documentedYesNoUnited States

Head-to-head: Blacksmith vs Depot GitHub Actions Runners · Depot GitHub Actions Runners vs GitHub-hosted runners · Depot GitHub Actions Runners vs Namespace · Depot GitHub Actions Runners vs Ubicloud Runners · Depot GitHub Actions Runners vs WarpBuild

See all Depot GitHub Actions Runners alternatives →

Frequently asked questions

What is Depot GitHub Actions Runners?
Managed GitHub Actions runners on single-tenant AWS EC2 instances, connected to Depot’s cache and container build service. A managed GitHub Actions runner service built on single-tenant AWS instances, suited to teams that also want Depot’s cache and container build service.
Which CI systems does Depot GitHub Actions Runners work with?
Depot GitHub Actions Runners runs jobs for GitHub Actions, on Linux, macOS, Windows, x64 and arm64.
How does Depot GitHub Actions Runners isolate jobs?
Depot GitHub Actions Runners documents its isolation as: 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 gets a fresh environment that is discarded afterwards.
Is Depot GitHub Actions Runners open source?
No, Depot GitHub Actions Runners is not open source. It does run in your own cloud account or on your own hardware.
How much does Depot GitHub Actions Runners cost?
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. Check the official pricing page for current rates.
How do I switch from GitHub-hosted runners to Depot GitHub Actions Runners?
Connect a GitHub organization by installing the Depot GitHub App from the Depot dashboard (organization owner role required), then change runs-on to a Depot label. Repositories owned by personal accounts are not supported. An example label is depot-ubuntu-24.04.
How fast is Depot GitHub Actions Runners?
Depot says its runners are up to 3x faster than GitHub-hosted runners, with 10x faster caching (vendor claim). Speed figures are the provider’s own and depend on the workload.
Does Depot GitHub Actions Runners have a free tier?
7-day free trial, no credit card required.
Does Depot GitHub Actions Runners support ARM64 runners?
Yes, Depot GitHub Actions Runners documents arm64 runners (Linux, macOS and Windows).
Does Depot GitHub Actions Runners offer macOS runners?
Yes, Depot GitHub Actions Runners documents macOS runners alongside Linux and Windows.
Does Depot GitHub Actions Runners cache Docker layers?
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.
Does Depot GitHub Actions Runners offer GPU runners?
Depot’s docs list GPU-enabled runners as available on the Business plan only; models and prices are not published.
Can Depot GitHub Actions Runners run in my own cloud account?
Yes, Depot GitHub Actions Runners documents a bring-your-own-cloud option on AWS.
How many jobs can run at once on Depot GitHub Actions Runners?
Unlimited concurrency on all plans; macOS runners come from a fixed pool, so jobs can queue when demand spikes.
Where do Depot GitHub Actions Runners runners run?
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.
What compliance certifications does Depot GitHub Actions Runners have?
SOC 2 Type 2.
What are the alternatives to Depot GitHub Actions Runners?

Sources

  1. depot.dev/pricing
  2. depot.dev/docs/github-actions/overview
  3. depot.dev/docs/github-actions/runner-types
  4. depot.dev/docs/github-actions/quickstart
  5. depot.dev/docs/github-actions/troubleshooting
  6. depot.dev/products/github-actions
  7. depot.dev/docs/security
  8. depot.dev/security
  9. depot.dev/docs/cache/overview
  10. depot.dev/docs/container-builds/overview
  11. depot.dev/docs/managed/overview
  12. depot.dev/about
  13. depot.dev/terms-of-service

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