Depot vs compiler.dev: Runners and Docker Builds

Depot is best known for fast Docker image builds with a persistent remote cache, and it also sells GitHub Actions runners. compiler.dev only does the runner part, with simple per-minute prices and no plan tiers. If your pain is slow docker build steps, Depot is the more specialised tool. If your pain is slow tests and compiles across a whole workflow, compiler.dev is the simpler and cheaper start. Prices were checked in October 2026 on Depot's pricing page.

What Depot is

Depot started as a hosted build service for Docker. Remote builders (up to 64 vCPUs on higher plans) keep a cache disk between builds, so layers persist and you do not export and import cache through a registry. Its pricing page shows 50 GB to 1 TB cache disks. The runners product came later: Intel and Arm Linux runners from 2 to 64 vCPUs, with a faster GitHub Actions cache included in every plan.

The pricing is plan-based. Developer is $20 a month with 2,000 runner minutes and 500 Docker build minutes. Startup is $200 a month with 20,000 and 5,000. Business is custom. Extra runner usage is $0.006 a minute and extra Docker build time is $0.04 a minute on the default 16 vCPU builder. Both paid plans have a 7-day trial.

Side-by-side

The Depot figure of $0.006 is for the base 2 vCPU Linux runner; its page does not publish the larger sizes, so we compare only that one. At 2 vCPU the difference is $0.006 against $0.003 a minute, after Depot's included minutes are used up.

Where Depot is the better choice

• Container builds are your biggest cost. A persistent cache disk next to a 16 to 64 vCPU builder is a purpose-built answer. A multi-stage image that takes ten minutes cold can take far less warm, and Depot is designed around that. See Docker layer caching in CI for the general problem.
• You build multi-architecture images. Depot can build Intel and Arm natively, which avoids slow emulation. compiler.dev has no ARM.
• You want one vendor for builds and runners and are happy with a plan fee. At 20,000 included minutes for $200 a month, the effective rate is $0.01 a minute at full use, and builds are in the same dashboard.
• You need ARM Linux runners. Depot has them; compiler.dev does not.

Where compiler.dev is the better choice

• You do not want a monthly plan. compiler.dev has no seat or plan fee. You buy prepaid credit that never expires, and unused credit is refundable on request. Light months cost less.
• Your minutes are mostly tests, not image builds. Running a test suite across 10 shards on larger machines is where the per-minute price and machine speed show up. Our benchmarks measured GitHub-hosted vs compiler.dev in full pipeline time: median 1.5× faster across 18 measured stacks (15 faster, 2 the same, 1 slower). We have no Depot benchmark and do not claim one.
• You want automatic fallback. If credit runs out or a job cannot start, it runs on your original runners.
• You want one-line setup with no builder changes. Depot's best results need you to swap your Docker build step for its action or CLI. compiler.dev needs only the runs-on change.

How to switch

To Depot runners, per its quickstart, change the label:

jobs:
  build:
    runs-on: depot-ubuntu-24.04

To use Depot builders for images, replace your Buildx step. The exact inputs are in Depot's docs; the shape is:

- uses: depot/setup-action@v1
- uses: depot/build-push-action@v1
  with:
    project: your-project-id
    push: true
    tags: ghcr.io/acme/app:latest

To compiler.dev:

jobs:
  build:
    runs-on: [self-hosted, Linux, compiler-ci]

Install the app at app.compiler.dev. If you use Depot builders today, you can keep them and move only the test jobs to compiler.dev. runs-on is per job, so this is a normal split.

A split setup worth considering

Many teams do not need to choose. Keep Depot for the one job that builds your image and put the rest of the pipeline, which is usually the bigger share of minutes, on a cheaper runner. Check your last month of usage first: the Actions cost calculator shows how much of your bill is Docker work. For ways to cut minutes before paying anyone, see speeding up GitHub Actions. The full provider ranking puts Depot in context.

FAQ

Is Depot a GitHub Actions runner provider?

Yes, among other things. It sells GitHub Actions runners and also hosted Docker builders with persistent cache. The two products are priced separately on its pricing page.

Does Depot have a free tier?

Not on its pricing page as of October 2026. The Developer plan includes 2,000 runner minutes for $20 a month and both paid plans offer a 7-day trial.

Can compiler.dev build Docker images faster than Depot?

We have not measured that and make no claim. compiler.dev keeps a Docker layer cache on the runner machine. Depot's dedicated builders with large cache disks are built for this one job.

Can I use Depot builders and compiler.dev runners together?

Yes. A job on a compiler.dev runner can call the Depot build action like any other runner. You pay each vendor for its part.

Does Depot support macOS?

Its pricing page says macOS runners are included in the plans, with no separate per-minute rate listed. Check with Depot for current rates.