CI Runnerscirunners.org
Head-to-head

Ubicloud Runners vs WarpBuild

Answer in brief

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. WarpBuild suits teams on GitHub Actions that want managed runners now with the option to move the same setup into their own AWS, Google Cloud or Azure account. Ubicloud Runners is a managed service hosted by the vendor for GitHub Actions, priced at $0.00125/min; WarpBuild is a managed service hosted by the vendor for GitHub Actions, priced at $0.004/min.

By the CI Runners editors · Updated

Key differences between Ubicloud Runners and WarpBuild

  • Operating systems: Only WarpBuild documents macOS and Windows.
  • Isolation: Ubicloud Runners: KVM VM. WarpBuild: Ephemeral VM.
  • Published price: $0.00125/min (Ubicloud Runners) versus $0.004/min (WarpBuild).
  • Largest runner: 30 vCPU / 120 GB (Ubicloud Runners) versus 32 vCPU / 128 GB (WarpBuild).
  • Open source: Ubicloud Runners is open source (AGPL-3.0); WarpBuild is not.
  • Self-hosting: Ubicloud Runners documents a self-hosted option; WarpBuild 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.

Ubicloud Runners vs WarpBuild at a glance

AttributeUbicloud RunnersWarpBuild
What it isManaged Linux runners for GitHub Actions from an open-source cloud platform that runs on leased bare metal.Managed GitHub Actions runners in ephemeral VMs, also offered as a deployment in your own AWS, Google Cloud or Azure account.
TypeManaged runner serviceManaged runner service
CI systemsGitHub ActionsGitHub Actions
Operating systemsLinuxLinux, macOS, Windows
Architecturesx64, arm64x64, arm64
IsolationEach 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 finishesEach runner runs in its own virtual machine with an encrypted storage volume, created on demand and destroyed after each build
Fresh environment per jobYesYes
HardwareStandard 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.The cloud provider and CPU models behind the standard cloud runners are not documented; macOS runners and the “xfast” Linux arm64 runners use Apple M4 Pro and M5 Pro hardware.
Performance (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)WarpBuild advertises runners that are “2x faster, 50% cheaper” and 3-10x faster caching (vendor claims)
Runner sizes2 to 30 vCPU with 8 to 120 GB RAM on x64; 2 to 30 vCPU with 6 to 90 GB on arm642 to 32 vCPU with 8 to 128 GB RAM on Linux x64 and arm64; 4 to 32 vCPU with 16 to 128 GB on Windows; 6 or 12 vCPU with 14 or 28 GB on macOS
CachingA 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.WarpBuild Cache (WarpBuilds/cache) is a drop-in replacement for actions/cache, enabled by default on Linux runners, with entries expiring 7 days after last use. Docker layer caching is offered through remote Docker Builders or a type=gha cache endpoint, and snapshot runners can save and boot from full VM disk snapshots on cloud Ubuntu runners.
Docker layer cachingYesYes
GPUNot documentedNot documented
ConcurrencyNot documentedUnlimited concurrency on Linux and Windows for generally available features; high-concurrency macOS requires contacting support
Static IPsNot documentedYes
SSH into running jobsYesYes
PricingStandard 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.Cloud runners per minute: Linux x64 from $0.004 (2 vCPU) to $0.064 (32 vCPU); Linux arm64 from $0.003 to $0.048; Windows from $0.016 (4 vCPU) to $0.128; macOS $0.08 (6 vCPU) and $0.16 (12 vCPU). Cache storage is $0.20 per GB-month plus $0.0001 per operation, and snapshot restore is $0.04 per job. BYOC runners carry a $0.002/min fee, with infrastructure billed by your cloud provider and cache and snapshots free.
Free tier$2.5/month credit, which Ubicloud equates to 1,250 runner minutesNot documented
Open sourceYes (AGPL-3.0)No
Self-host / your cloudYes / Not documentedNo / Yes
ComplianceSOC 2 Type 2 report available through the Trust Center; GDPR data processing agreement offeredSOC 2 Type 2 (Security, Availability and Confidentiality criteria)
RegionsEurope 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 requestNot listed for the standard cloud runners; region-specific infrastructure is offered on enterprise plans, and BYOC runners run in the region of your own stack
Company headquartersSan Francisco, California, United StatesNot documented
Good fit forTeams on GitHub Actions that want low per-minute Linux runners in European data centers from a vendor whose cloud platform is open sourceTeams on GitHub Actions that want managed runners now with the option to move the same setup into their own AWS, Google Cloud or Azure account

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

Which should you choose?

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

Reasons to choose WarpBuild

  • You want the choice between vendor-hosted runners and runners inside your own AWS, Google Cloud or Azure account
  • You want each runner in its own VM that is destroyed after the build
  • You need Linux x64 and arm64, Windows and macOS runners under one account
  • You want to boot jobs from a saved VM disk snapshot for incremental builds

Trade-offs to check first

  • Ubicloud Runners: Windows and macOS runners are not documented
  • Ubicloud Runners: Runner prices were raised twice in 2026, in May and September
  • WarpBuild: Static IPs are available only with BYOC deployments
  • WarpBuild: WarpBuild Cache is not supported on Windows runners

Run your slowest workflow on both before deciding. See the full Ubicloud Runners profile and WarpBuild profile, or the complete comparison.

More comparisons

Frequently asked questions

Is Ubicloud Runners or WarpBuild better?
Neither is better for every pipeline. 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. WarpBuild suits teams on GitHub Actions that want managed runners now with the option to move the same setup into their own AWS, Google Cloud or Azure account.
What is the difference between Ubicloud Runners and WarpBuild?
Only WarpBuild documents macOS and Windows. Isolation is KVM VM on Ubicloud Runners and Ephemeral VM on WarpBuild. Published price: $0.00125/min (Ubicloud Runners) versus $0.004/min (WarpBuild). Largest runner: 30 vCPU / 120 GB (Ubicloud Runners) versus 32 vCPU / 128 GB (WarpBuild). Ubicloud Runners is open source (AGPL-3.0); WarpBuild is not.
Which is open source, Ubicloud Runners or WarpBuild?
Ubicloud Runners is open source (AGPL-3.0); WarpBuild is not open source.
How do Ubicloud Runners and WarpBuild isolate jobs?
Ubicloud Runners: 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. WarpBuild: Each runner runs in its own virtual machine with an encrypted storage volume, created on demand and destroyed after each build.
How does Ubicloud Runners pricing compare with WarpBuild?
Ubicloud Runners: 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. WarpBuild: Cloud runners per minute: Linux x64 from $0.004 (2 vCPU) to $0.064 (32 vCPU); Linux arm64 from $0.003 to $0.048; Windows from $0.016 (4 vCPU) to $0.128; macOS $0.08 (6 vCPU) and $0.16 (12 vCPU). Cache storage is $0.20 per GB-month plus $0.0001 per operation, and snapshot restore is $0.04 per job. BYOC runners carry a $0.002/min fee, with infrastructure billed by your cloud provider and cache and snapshots free. Rates change, so check the Ubicloud Runners and WarpBuild pricing pages before deciding.
Is Ubicloud Runners or WarpBuild faster?
We have not benchmarked them, and speed depends on the workload. What each provider says: Ubicloud Runners: 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). WarpBuild: WarpBuild advertises runners that are “2x faster, 50% cheaper” and 3-10x faster caching (vendor claims).
Do Ubicloud Runners and WarpBuild cache Docker layers?
Ubicloud Runners: 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. WarpBuild: WarpBuild Cache (WarpBuilds/cache) is a drop-in replacement for actions/cache, enabled by default on Linux runners, with entries expiring 7 days after last use. Docker layer caching is offered through remote Docker Builders or a type=gha cache endpoint, and snapshot runners can save and boot from full VM disk snapshots on cloud Ubuntu runners.
Where do Ubicloud Runners and WarpBuild runners run?
Ubicloud Runners is a managed service hosted by the vendor (Hetzner, Leaseweb, AWS and Bare metal). WarpBuild is a managed service hosted by the vendor (AWS, Google Cloud and Azure).

Sources

  1. ubicloud.com/use-cases/github-actions
  2. ubicloud.com/docs/about/pricing
  3. ubicloud.com/docs/github-actions-integration/quickstart
  4. ubicloud.com/docs/github-actions-integration/runner-types
  5. warpbuild.com/
  6. warpbuild.com/pricing
  7. warpbuild.com/docs/ci
  8. warpbuild.com/docs/ci/cloud-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). Ubicloud Runners vs WarpBuild. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/compare/ubicloud-vs-warpbuild/