# RunsOn vs Ubicloud vs WarpBuild: pricing compared, and Skipbox's flat price

> Skipbox is a flat $39 a month with unlimited minutes. RunsOn is a yearly license plus your own AWS bill; Ubicloud and WarpBuild bill by the minute. At 20,000 minutes on 4 vCPU: RunsOn $62.17, Ubicloud $77.50, WarpBuild $160.

RunsOn, Ubicloud and WarpBuild are three ways to pay for the same thing, a GitHub Actions job on someone's VM. Skipbox is the fourth, and the only one with a flat price: $39 a month with unlimited minutes, on a machine kept for your account.

RunsOn runs in your own AWS account: you pay a yearly license, and AWS bills you for every instance. Ubicloud is managed and bills each minute. WarpBuild bills each minute too, on its cloud or, with BYOC, in yours.

- 20,000 minutes at 4 vCPU: Skipbox $39, RunsOn $62.17 on Spot, Ubicloud $77.50, WarpBuild $160
- Running all month on 4 vCPU: Skipbox still $39, RunsOn $92.33, Ubicloud $170.30, WarpBuild $345.60
- No stack in your cloud account, and caches stay on a machine Skipbox hosts for your account alone between jobs

**GitHub Actions at a flat price, unlimited minutes** Skipbox runs your GitHub Actions jobs on your own dedicated machine: $39 a month, however many minutes you run. Docker layers and dependency caches stay between jobs, so the next job starts right away.

A 4 vCPU runner, 20,000 minutes a month: GitHub $222 → Skipbox $39. You save $183 every month.

Moving takes one line: `runs-on: skipbox`.

[Start my 7-day free trial](https://app.skipbox.dev/sign-in?ref=compare-runs-on-vs-ubicloud-vs-warpbuild-en)

## What each one bills

Linux x64 runners, from each vendor's pricing page, read on 17 November 2026:

| Runner | How it bills | Where jobs run | 4 vCPU | 8 vCPU | 16 vCPU |
|---|---|---|---|---|---|
| **Skipbox** | **Flat monthly price, unlimited minutes** | **A machine kept for your account, run by Skipbox** | **$39 a month** | **$79 a month** | **$149 a month** |
| RunsOn | A license, €300 a year ($350 in dollars) under 50,000 jobs a month, plus your AWS bill | EC2 instances in your own AWS account | $0.0013 a minute on Spot, $0.0041 on demand | $0.0024 a minute on Spot, $0.0074 on demand | $0.0034 a minute on Spot, $0.0148 on demand |
| Ubicloud | Per minute, after a $2.50 monthly credit. Premium runners, the default for new accounts; standard is $0.0025 a minute at 4 vCPU | Ubicloud's VMs in data centers in Germany | $0.004 a minute | $0.008 a minute | $0.016 a minute |
| WarpBuild | Per minute | WarpBuild's cloud, or your AWS, GCP or Azure account with BYOC | $0.008 a minute | $0.016 a minute | $0.032 a minute |

WarpBuild's BYOC is $0.002 a minute paid to WarpBuild, plus your cloud provider's bill for the instances.

RunsOn's Spot rates are for Spot instances, which AWS takes back when it needs the capacity.

## The monthly bill at your minutes

Jobs on a 4 vCPU runner:

| Minutes a month (4 vCPU) | Skipbox S | RunsOn, Spot | RunsOn, on demand | Ubicloud premium | WarpBuild |
|---|---|---|---|---|---|
| 20,000 | $39 | $62.17 | $117.31 | $77.50 | $160 |
| 30,000 | $39 | $75.17 | $157.89 | $117.50 | $240 |
| Always on | $39 | $92.33 | $211.44 | $170.30 | $345.60 |

At 20,000 minutes on bigger machines:

| 20,000 minutes a month | Skipbox | RunsOn, Spot | RunsOn, on demand | Ubicloud premium | WarpBuild |
|---|---|---|---|---|---|
| 8 vCPU | $79 (M) | $84.17 | $184.01 | $157.50 | $320 |

How the figures are counted:

- **Skipbox:** the plan's price. Minutes are unlimited, so every row is the same.
- **RunsOn:** its Starter license, $350 a year ($29.17 a month, under 50,000 jobs a month), plus the control plane it puts at "about $7 a month", plus the instances. Spot is the per-minute rate on RunsOn's pricing page for its default instances in us-east-1 (m8a.xlarge, c8id.2xlarge, c8id.4xlarge), a 7-day average with a 30 GB disk. On demand is AWS's price for the same instances in US East (N. Virginia): $0.2434, $0.4435 and $0.8870 an hour, before the disk.
- **Ubicloud:** its premium runner, the default for new accounts, at $0.004 a minute at 4 vCPU and $0.008 at 8, less the $2.50 monthly credit.
- **WarpBuild:** $0.008 a minute at 4 vCPU, $0.016 at 8 and $0.032 at 16.
- **Always on** is 43,200 minutes, a 30-day month.

Check your own minutes in the [calculator on the home page](https://skipbox.dev/?ref=compare-runs-on-vs-ubicloud-vs-warpbuild-en#cost).

## Managed service or your own AWS account

Skipbox is managed, and the machine is still yours alone:

- **Skipbox:** nothing to install in a cloud account. Skipbox provisions, updates, cleans and health-checks the machine for you, and that machine runs only your account's jobs. One invoice, the plan's flat price.
- **RunsOn:** you install it as a CloudFormation stack in your AWS account, and you apply each new version as a stack update. The EC2 instances, their EBS volumes, the Fargate control plane, the S3 cache bucket and the data transfer are on your AWS bill; the license is a second invoice.
- **WarpBuild BYOC:** you connect your cloud account through an IAM role, create a WarpBuild Stack (a VPC, subnets and object storage buckets) in a region, and apply the updates WarpBuild asks for. The instances are on your cloud bill, and WarpBuild bills $0.002 a minute on top.
- **Ubicloud and WarpBuild's cloud runners:** managed, a new VM for every job, billed by the minute.

## Where Skipbox jobs run, and how each job is isolated

- **Where.** On a server Skipbox operates in Japan, on Hetzner Cloud servers in Finland and Germany (EU), and on Google Cloud servers in France, Spain and Italy (EU).
- **A machine for your organization alone.** Skipbox hosts one with each plan: a VM that runs only your organization's jobs, one at a time. It never runs another organization's job.
- **After every job.** Skipbox deletes the runner's credentials, stops every process of the runner user, removes every container and deletes the credential files in the home directory.
- **Code from outside your team.** Jobs of code from people without write access, such as pull requests from forks, run on a fresh VM that has run no other job and is deleted with its disk when the job ends. It reads your caches and can't change them.
- **A runner for one job.** Skipbox registers each runner just in time, for a single job.
- **No inbound connections.** Nothing on the internet can connect to a job's VM. Outbound, the internet is open as on GitHub-hosted runners, and traffic isn't charged.
- **Clean every job.** Turn it on and every job gets a fresh machine.

The details are in [job isolation](https://docs.skipbox.dev/isolation) and [network and egress](https://docs.skipbox.dev/network).

## Cache between jobs

On Skipbox the machine your next job runs on is the one the last job left: Docker images and build cache, `~/.npm`, `~/.cache/pip`, `~/.gradle`, tools from `setup-*` actions, your checkout and Cargo's `target/` are already on disk. Nothing is uploaded, downloaded or priced per GB, and there is 7× the room of GitHub's default 10 GB cache.

| Runner | New machine each job | What carries over | Storage price |
|---|---|---|---|
| **Skipbox** | **No: a machine kept for your account** | **Everything on its disk, and `actions/cache` served from the same disk** | **Included in the flat plan price** |
| RunsOn | Yes, an EC2 instance destroyed after the job | Magic Cache in an S3 bucket in your AWS account; sticky disks as EBS snapshots | S3 and EBS on your AWS bill |
| Ubicloud | Yes | Its cache behind `actions/cache` and Docker's `type=gha` | 30 GB free on standard runners, 100 GB on premium |
| WarpBuild | Yes, ephemeral VMs | `WarpBuilds/cache` in place of `actions/cache`; snapshot runners; Docker builders | $0.20 per GB-month plus $0.0001 per operation; snapshots $0.025 an hour each and $0.04 per restore |

More in [runners that keep your cache between jobs](https://skipbox.dev/compare/github-actions-runners-persistent-cache).

## Depot, Blacksmith, Namespace and RunsOn: prices side by side

The same 4 vCPU job, 20,000 minutes a month:

| Runner | How it bills | 4 vCPU rate | 20,000 minutes a month |
|---|---|---|---|
| **Skipbox** | **Flat monthly price, unlimited minutes** | **$39 a month** | **$39** |
| Depot | $20 or $200 plan with minutes included, then per minute | $0.012 a minute (2× minutes) | $248 |
| Blacksmith | Per minute, past 3,000 free 2 vCPU minutes | $0.008 a minute | $148 |
| Namespace | $0, $100 or $250 plan, then per unit minute | $0.006 a minute (4 vCPU, 8 GB) | $100 |
| RunsOn | A $350 yearly license plus your AWS bill | $0.0013 a minute on Spot | $62.17 |

Every runner's bill at more volumes is in [GitHub Actions runners compared](https://skipbox.dev/compare/github-actions-runners-compared), and Depot's and Blacksmith's limits are in [Depot vs Blacksmith](https://skipbox.dev/compare/depot-vs-blacksmith).

## What a team saves each month

A team that runs 20,000 minutes a month on 4 vCPU pays GitHub $222 for its 4-core runner. On Skipbox the same month is $39: $183 less, every month.

Against the three here, the same 20,000 minutes are $160 on WarpBuild, $77.50 on Ubicloud's premium runners and $62.17 on RunsOn with Spot instances. Skipbox stays at $39 at 30,000 minutes, and at 43,200.

| Plan | Machine | Per month |
|---|---|---|
| S | 4 vCPU, 16 GB | $39 |
| M | 8 vCPU, 16 GB | $79 |
| L | 16 vCPU, 32 GB | $149 |

Unlimited minutes, no usage charges. Plans add up in any mix: each plan you add runs more jobs at once, at its flat price.

## Moving is one line

```yaml
jobs:
  test:
    runs-on: skipbox # was a RunsOn label, ubicloud-standard-4 or warp-ubuntu-latest-x64-4x
    steps:
      - uses: actions/checkout@v4
      - run: npm ci && npm test
```

1. Sign in to Skipbox with GitHub.
2. Install the Skipbox GitHub app and pick the repositories.
3. Change `runs-on` and push.

Use `skipbox-8x16` for 8 vCPU jobs and `skipbox-16x32` for 16 vCPU jobs.

## Try it before you pick

You can try it on your own jobs first: free for 7 days or 3,000 minutes, no card.

Point one job you were about to move to RunsOn, Ubicloud or WarpBuild at `runs-on: skipbox` instead, and compare the second run and the bill.

## FAQ

### RunsOn vs Ubicloud vs WarpBuild: which GitHub Actions runner should I pick?

Skipbox, if you want the bill fixed: a flat $39 a month with unlimited minutes, on a machine kept for your account. RunsOn runs in your own AWS account for a yearly license plus your AWS bill. Ubicloud and WarpBuild are managed and bill every minute: $0.004 and $0.008 a minute at 4 vCPU.

### Is RunsOn cheaper than WarpBuild?

Skipbox costs less than both at 20,000 minutes a month on 4 vCPU: a flat $39. Between the two, RunsOn is lower: $62.17 a month ($26 of Spot instances, $29.17 of its $350 yearly license and about $7 of control plane, all but the license paid to AWS) against WarpBuild's $160. On on-demand instances RunsOn comes to $117.31.

### Does Ubicloud bill per minute?

Yes. Ubicloud bills each minute: $0.004 at 4 vCPU on the premium runners new accounts get by default, after a $2.50 monthly credit. Skipbox has no per-minute charge: $39 a month with unlimited minutes.

### Which has a flat monthly price: RunsOn, Ubicloud or WarpBuild?

Skipbox is the one with a flat monthly price: $39, $79 or $149 a month for 4, 8 or 16 vCPU jobs, with unlimited minutes. RunsOn's license is a flat yearly fee, with the instances billed by AWS per second. Ubicloud and WarpBuild bill per minute.

### Depot, Blacksmith, Namespace and RunsOn: how do their prices differ?

Skipbox is a flat $39 a month with unlimited minutes. Depot sells a $20 or $200 plan with minutes included, then $0.012 a minute at 4 vCPU. Blacksmith bills $0.008 a minute past 3,000 free minutes. Namespace sells a $0, $100 or $250 plan, then $0.006 a minute at 4 vCPU. RunsOn is a $350 yearly license plus your AWS bill. At 20,000 minutes a month on 4 vCPU that is Depot $248, Blacksmith $148, Namespace $100 and RunsOn $62.17.

### Managed runners or runners in my own AWS account?

Managed, on Skipbox: there is no stack to install, upgrade or pay AWS for, and your account's machine runs only your account's jobs. With RunsOn you install a CloudFormation stack in your AWS account and apply each upgrade yourself; with WarpBuild's BYOC you connect an IAM role and create a Stack in your cloud account.

### How do I move a job from RunsOn, Ubicloud or WarpBuild to Skipbox?

Change one line. Install the Skipbox GitHub app, set runs-on to skipbox, and push; steps and actions stay as they are.

Updated 2026-11-19 · https://skipbox.dev/compare/runs-on-vs-ubicloud-vs-warpbuild
