Skip to content

Migration guides

Migrate from Depot to runnerhut

The exact change to move your workflows from Depot — and the change to move back, so you can evaluate without committing.

What Depot does well

  • Excellent remote Docker build performance with persistent layer cache
  • Native multi-platform builds without QEMU emulation
  • Simple, well-designed developer experience

Where we differ

  • Docker-first — less compelling when your bottleneck is tests, not images
  • Narrower runner matrix than platforms leading with general-purpose CI
Depotrunnerhut
EU data residencyNot publishedSix EU regions
Remote Docker buildersYesYes
Native multi-archYesYes
General CI runnersYesYes
macOS runnersYesYes
Test-suite accelerationSecondary focusPrimary focus
Compiled from each vendor's public documentation, August 2026.

The migration

yaml
jobs:
build:
- runs-on: depot-ubuntu-22.04
+ runs-on: runnerhut-8vcpu-ubuntu-2404
steps:
- uses: actions/checkout@v4
One line. Every other line of your workflow is untouched.

And the migration back

We publish this because after BuildJet's shutdown, "what if you disappear" is a fair question. Leaving is the same single line you changed to arrive.

yaml
jobs:
build:
- runs-on: runnerhut-8vcpu-ubuntu-2404
+ runs-on: ubuntu-latest

Checklist

  1. Install the runnerhut GitHub App on the repositories you want to move
  2. Change runs-on in one job first and compare timings against the old runner
  3. Add runner.arch to cache keys if you are also moving to arm64
  4. Roll out to the rest of the repository once the comparison looks right
  5. Set a budget cap and concurrency cancellation before going organisation-wide

Your next build could be twice as fast, at half the price

Start free. Migrating away is the same one line, and we publish that diff too.