Skip to content

Migration guides

Migrate from Ubicloud to runnerhut

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

What Ubicloud does well

  • Aggressive price-performance — the cheapest credible option in the category
  • Open source, which materially reduces lock-in risk
  • Transparent GitHub Actions cache with no configuration change
  • Deep infrastructure engineering blog that earns real technical trust

Where we differ

  • CI runners are one product line among Postgres, Kubernetes, compute and GPU
  • Only eight use-case pages — thin guidance for stack-specific CI problems
  • Price leadership constrains how much headroom there is for support
Ubicloudrunnerhut
EU data residencyYes, EU-based infrastructureYes, all plans
Drop-in runs-onYesYes
Open sourceYesNo
Transparent cacheYesYes
arm64 runnersYesYes
macOS runnersNot publishedYes
Windows runnersNot publishedYes
Dedicated CI focusNoYes
Compiled from each vendor's public documentation, August 2026.

The migration

yaml
jobs:
build:
- runs-on: ubicloud-standard-4
+ 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.