Depot GitHub Actions Runners vs Ubicloud 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. Ubicloud Runners suits teams on GitHub Actions that want low per-minute Linux runners in European data centers from a vendor whose cloud platform is open source. Depot GitHub Actions Runners is a managed service hosted by the vendor for GitHub Actions, priced at $0.006/min; Ubicloud Runners is a managed service hosted by the vendor for GitHub Actions, priced at $0.00125/min.
Key differences between Depot GitHub Actions Runners and Ubicloud Runners
- Operating systems: Only Depot GitHub Actions Runners documents macOS and Windows.
- Isolation: Depot GitHub Actions Runners: Single-tenant EC2 instance. Ubicloud Runners: KVM VM.
- Published price: $0.006/min (Depot GitHub Actions Runners) versus $0.00125/min (Ubicloud Runners).
- Largest runner: 64 vCPU / 256 GB (Depot GitHub Actions Runners) versus 30 vCPU / 120 GB (Ubicloud Runners).
- Open source: Ubicloud Runners is open source (AGPL-3.0); Depot GitHub Actions Runners is not.
- Self-hosting: Ubicloud Runners documents a self-hosted option; Depot GitHub Actions Runners does not.
What they have in common
- Both are managed services hosted by the vendor.
- Both run GitHub Actions jobs.
- Both document Linux runners.
- Both document arm64 runners.
- Both use a virtual machine per runner.
- Both give every job a fresh environment.
- Both document Docker layer caching.
Depot GitHub Actions Runners vs Ubicloud Runners at a glance
| Attribute | Depot GitHub Actions Runners | Ubicloud Runners |
|---|---|---|
| What it is | Managed GitHub Actions runners on single-tenant AWS EC2 instances, connected to Depot’s cache and container build service. | Managed Linux runners for GitHub Actions from an open-source cloud platform that runs on leased bare metal. |
| Type | Managed runner service | Managed runner service |
| CI systems | GitHub Actions | GitHub Actions |
| Operating systems | Linux, macOS, Windows | Linux |
| 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 fresh virtual machine provisioned with Linux KVM, using Cloud Hypervisor as the virtual machine monitor; the VM and its block storage are destroyed when the job finishes |
| 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. | Standard x64 runners use AMD EPYC 9454P (two vCPUs per physical core), premium x64 runners use AMD Ryzen 9 7950X3D, and arm64 runners use Ampere Altra Q80-30 with one physical core per vCPU; all have NVMe SSDs. |
| Performance (vendor claim) | Depot says its runners are up to 3x faster than GitHub-hosted runners, with 10x faster caching (vendor claim) | Ubicloud says premium runners are around 2x faster on CPU-heavy workflows and that its cache gives 4x faster downloads and 3x faster uploads (vendor claims) |
| 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 | 2 to 30 vCPU with 8 to 120 GB RAM on x64; 2 to 30 vCPU with 6 to 90 GB on arm64 |
| 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. | A transparent cache backend serves actions/cache, setup-* package caching and Docker layer caching through type=gha without workflow changes. Each repository gets 30 GB free (100 GB with premium runners enabled), entries unused for seven days are removed, and extra storage is $0.04 per GB per month on request. |
| 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 | Not documented |
| Static IPs | Yes | Not documented |
| 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. | Standard x64 per minute: $0.00125 (2 vCPU), $0.0025 (4), $0.005 (8), $0.01 (16) and $0.01875 (30 vCPU). Premium x64: $0.002 (2 vCPU) to $0.03 (30 vCPU). arm64 is priced the same as standard x64. Billing is per minute, and new users get premium runners by default with fallback to standard runners when premium capacity is full. |
| Free tier | 7-day free trial, no credit card required | $2.5/month credit, which Ubicloud equates to 1,250 runner minutes |
| Open source | No | Yes (AGPL-3.0) |
| Self-host / your cloud | No / Yes | Yes / Not documented |
| Compliance | SOC 2 Type 2 | SOC 2 Type 2 report available through the Trust Center; GDPR data processing agreement offered |
| 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 | Europe by default: Hetzner (Falkenstein, Germany) as the primary fleet and Leaseweb (Frankfurt), with AWS eu-central-1 as overflow; US runners are used only on explicit request |
| 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 low per-minute Linux runners in European data centers from a vendor whose cloud platform is open source |
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 Ubicloud Runners
- You want Linux runners at $0.00125 per minute for 2 vCPU, on x64 or arm64
- You want the underlying cloud platform to be open source and self-hostable
- You need jobs to run in European data centers by default
- You want existing actions/cache and type=gha Docker layer caching to work without workflow changes
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
- Ubicloud Runners: Windows and macOS runners are not documented
- Ubicloud Runners: Runner prices were raised twice in 2026, in May and September
Run your slowest workflow on both before deciding. See the full Depot GitHub Actions Runners profile and Ubicloud Runners profile, or the complete comparison.
More comparisons
- 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 WarpBuild
- Blacksmith vs Ubicloud Runners
- GitHub-hosted runners vs Ubicloud Runners
- Namespace vs Ubicloud Runners
- TestFlows GitHub Hetzner Runners vs Ubicloud Runners
- Ubicloud Runners vs WarpBuild
Frequently asked questions
Is Depot GitHub Actions Runners or Ubicloud Runners better?
What is the difference between Depot GitHub Actions Runners and Ubicloud Runners?
Which is open source, Depot GitHub Actions Runners or Ubicloud Runners?
How do Depot GitHub Actions Runners and Ubicloud Runners isolate jobs?
How does Depot GitHub Actions Runners pricing compare with Ubicloud Runners?
Is Depot GitHub Actions Runners or Ubicloud Runners faster?
Do Depot GitHub Actions Runners and Ubicloud Runners cache Docker layers?
Do Depot GitHub Actions Runners and Ubicloud Runners offer GPU runners?
Where do Depot GitHub Actions Runners and Ubicloud 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
- ubicloud.com/use-cases/github-actions
- ubicloud.com/docs/about/pricing
- ubicloud.com/docs/github-actions-integration/quickstart
- ubicloud.com/docs/github-actions-integration/runner-types
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 Ubicloud Runners. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/compare/depot-vs-ubicloud/