CI Runnerscirunners.org
Head-to-head

Blacksmith vs Depot GitHub Actions Runners

Answer in brief

Blacksmith suits teams on GitHub Actions that want microVM-isolated runners on bare metal with built-in Docker layer caching and CI observability. 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. Blacksmith is a managed service hosted by the vendor for GitHub Actions, priced at $0.004/min; Depot GitHub Actions Runners is a managed service hosted by the vendor for GitHub Actions, priced at $0.006/min.

By the CI Runners editors · Updated

Key differences between Blacksmith and Depot GitHub Actions Runners

  • Isolation: Blacksmith: Firecracker microVM. Depot GitHub Actions Runners: Single-tenant EC2 instance.
  • Published price: $0.004/min (Blacksmith) versus $0.006/min (Depot GitHub Actions Runners).
  • Largest runner: 32 vCPU / 128 GB (Blacksmith) versus 64 vCPU / 256 GB (Depot GitHub Actions Runners).

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 give every job a fresh environment.
  • Neither is open source.
  • Both document Docker layer caching.

Blacksmith vs Depot GitHub Actions Runners at a glance

AttributeBlacksmithDepot GitHub Actions Runners
What it isManaged GitHub Actions runners in Firecracker microVMs on the vendor’s own bare-metal fleet, with caches kept next to the runners.Managed GitHub Actions runners on single-tenant AWS EC2 instances, connected to Depot’s cache and container build service.
TypeManaged runner serviceManaged runner service
CI systemsGitHub ActionsGitHub Actions
Operating systemsLinux, macOS, WindowsLinux, macOS, Windows
Architecturesx64, arm64x64, arm64
IsolationEach Linux and Windows job runs in an ephemeral Firecracker microVM on Blacksmith’s bare-metal hosts and is destroyed afterwards; the isolation used for macOS runners is not documentedEach 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 jobYesYes
HardwareBlacksmith describes its hosts as bare-metal machines with gaming CPUs chosen for single-core performance and NVMe drives, in ISO 27001 data centers; CPU models are not named, and macOS runners use Apple M4.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.
Performance (vendor claim)Blacksmith says most CI jobs run about 2x faster than on GitHub-hosted runners and cache downloads about 4x faster, and that customers report 2x to 40x faster Docker builds (vendor claims)Depot says its runners are up to 3x faster than GitHub-hosted runners, with 10x faster caching (vendor claim)
Runner sizes2 to 32 vCPU with 8 to 128 GB RAM on Linux x64; 2 to 32 vCPU with 6 to 96 GB on Linux arm64; 2 to 32 vCPU with 7 to 112 GB on Windows x64 (public beta); 6 or 12 vCPU with 24 or 48 GB on macOS2 to 64 vCPU with 8 to 256 GB RAM on Linux x64, Linux arm64 and Windows; macOS runners are 8 vCPU with 24 GB
CachingStandard cache actions (actions/cache and the setup-* actions) are served from a cache in the same data center as the runners, with 25 GB of free storage per repository per week and eviction of entries unused for 7 days. Docker layers persist on NVMe-backed sticky disks through useblacksmith/setup-docker-builder, billed at $0.50/GB/month; the docs also cover Git checkout, container image and Bazel, Go, Turborepo and Nx build 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.
Docker layer cachingYesYes
GPUNot documentedDepot’s docs list GPU-enabled runners as available on the Business plan only; models and prices are not published.
ConcurrencyBlacksmith documents no limit on concurrent jobs or vCPUsUnlimited concurrency on all plans; macOS runners come from a fixed pool, so jobs can queue when demand spikes
Static IPsYesYes
SSH into running jobsYesNot documented
PricingThe pricing page lists Ubuntu x64 at $0.004/min, Ubuntu ARM at $0.0025/min, Windows x64 at $0.008/min and macOS M4 at $0.08/min; the docs say runners cost half of GitHub’s per-minute rate. Add-ons: Docker layer caching and sticky disks at $0.50/GB/month and static IPs at $100/IP/month. Flex scheduling costs 40% less for jobs that can wait up to 24 hours to start.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.
Free tier3,000 free minutes per organization per month, counted as x64 2-vCPU minutes; larger, ARM, Windows and macOS runners consume them at weighted rates7-day free trial, no credit card required
Open sourceNoNo
Self-host / your cloudNo / Not documentedNo / Yes
ComplianceSOC 2 Type 2; GDPR compliant (as stated by Blacksmith); HIPAA described as in progressSOC 2 Type 2
Regionsus-east (Ashburn), us-west (Phoenix), eu-west (Amsterdam) and eu-central (Frankfurt); changing region requires contacting supportDepot 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
Company headquartersSan Francisco, California, United StatesNot documented
Good fit forTeams on GitHub Actions that want microVM-isolated runners on bare metal with built-in Docker layer caching and CI observabilityTeams on GitHub Actions that want single-tenant EC2 runners alongside a shared build cache and remote container builds from the same vendor

Verified November 22, 2026 from each provider’s documentation. Performance figures are vendor claims, not our measurements.

Which should you choose?

Reasons to choose Blacksmith

  • You want each Linux or Windows job in its own Firecracker microVM that is destroyed after the job
  • You want Docker layers kept on persistent NVMe-backed disks between runs
  • You need to run many jobs at once: Blacksmith documents no concurrency limit
  • You want to SSH into running jobs and search CI logs from one console

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

Trade-offs to check first

  • Blacksmith: Available to GitHub organizations only, not personal repositories
  • Blacksmith: Windows runners are in public beta and do not support Docker Linux containers
  • 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

Run your slowest workflow on both before deciding. See the full Blacksmith profile and Depot GitHub Actions Runners profile, or the complete comparison.

More comparisons

Frequently asked questions

Is Blacksmith or Depot GitHub Actions Runners better?
Neither is better for every pipeline. Blacksmith suits teams on GitHub Actions that want microVM-isolated runners on bare metal with built-in Docker layer caching and CI observability. 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.
What is the difference between Blacksmith and Depot GitHub Actions Runners?
Isolation is Firecracker microVM on Blacksmith and Single-tenant EC2 instance on Depot GitHub Actions Runners. Published price: $0.004/min (Blacksmith) versus $0.006/min (Depot GitHub Actions Runners). Largest runner: 32 vCPU / 128 GB (Blacksmith) versus 64 vCPU / 256 GB (Depot GitHub Actions Runners).
Which is open source, Blacksmith or Depot GitHub Actions Runners?
Neither is open source.
How do Blacksmith and Depot GitHub Actions Runners isolate jobs?
Blacksmith: Each Linux and Windows job runs in an ephemeral Firecracker microVM on Blacksmith’s bare-metal hosts and is destroyed afterwards; the isolation used for macOS runners is not documented. Depot GitHub Actions Runners: Each job runs on a new single-tenant EC2 instance that has never been used before and is destroyed when the job completes.
How does Blacksmith pricing compare with Depot GitHub Actions Runners?
Blacksmith: The pricing page lists Ubuntu x64 at $0.004/min, Ubuntu ARM at $0.0025/min, Windows x64 at $0.008/min and macOS M4 at $0.08/min; the docs say runners cost half of GitHub’s per-minute rate. Add-ons: Docker layer caching and sticky disks at $0.50/GB/month and static IPs at $100/IP/month. Flex scheduling costs 40% less for jobs that can wait up to 24 hours to start. Depot GitHub Actions Runners: 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. Rates change, so check the Blacksmith and Depot GitHub Actions Runners pricing pages before deciding.
Is Blacksmith or Depot GitHub Actions Runners faster?
We have not benchmarked them, and speed depends on the workload. What each provider says: Blacksmith: Blacksmith says most CI jobs run about 2x faster than on GitHub-hosted runners and cache downloads about 4x faster, and that customers report 2x to 40x faster Docker builds (vendor claims). Depot GitHub Actions Runners: Depot says its runners are up to 3x faster than GitHub-hosted runners, with 10x faster caching (vendor claim).
Do Blacksmith and Depot GitHub Actions Runners cache Docker layers?
Blacksmith: Standard cache actions (actions/cache and the setup-* actions) are served from a cache in the same data center as the runners, with 25 GB of free storage per repository per week and eviction of entries unused for 7 days. Docker layers persist on NVMe-backed sticky disks through useblacksmith/setup-docker-builder, billed at $0.50/GB/month; the docs also cover Git checkout, container image and Bazel, Go, Turborepo and Nx build caching. Depot GitHub Actions Runners: 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.
Do Blacksmith and Depot GitHub Actions Runners offer GPU runners?
Blacksmith: Not documented. Depot GitHub Actions Runners: Depot’s docs list GPU-enabled runners as available on the Business plan only; models and prices are not published.
Where do Blacksmith and Depot GitHub Actions Runners runners run?
Blacksmith is a managed service hosted by the vendor. Depot GitHub Actions Runners is a managed service hosted by the vendor (AWS).

Sources

  1. blacksmith.sh/
  2. blacksmith.sh/pricing
  3. blacksmith.sh/security
  4. docs.blacksmith.sh/blacksmith-runners/overview
  5. depot.dev/pricing
  6. depot.dev/docs/github-actions/overview
  7. depot.dev/docs/github-actions/runner-types
  8. depot.dev/docs/github-actions/quickstart

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). Blacksmith vs Depot GitHub Actions Runners. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/compare/blacksmith-vs-depot/