Migration guides
Migrate from WarpBuild to runnerhut
The exact change to move your workflows from WarpBuild — and the change to move back, so you can evaluate without committing.
What WarpBuild does well
- The broadest runner matrix in the category — Linux, macOS, Windows, arm64, snapshots
- Mature bring-your-own-cloud story with per-provider documentation
- By far the strongest content and SEO footprint: ~750 indexed pages
- Remote Docker builders and snapshot runners are genuinely differentiated
Where we differ
- Breadth comes with configuration surface — more knobs to get wrong
- Snapshot runners add a storage line item that is easy to under-forecast
- BYOC shifts cloud cost and IAM risk back onto your team
| WarpBuild | runnerhut | |
|---|---|---|
| EU data residency | Yes, enterprise tier | Yes, all plans |
| Drop-in runs-on | Yes | Yes |
| Runner families | Linux, macOS, Windows | Linux, macOS, Windows, GPU |
| Bring your own cloud | AWS, GCP, Azure | AWS, GCP, Azure |
| Snapshot runners | Yes | Yes |
| Included cache | Metered | Unlimited |
| Setup surface | Large | One line |
| Per-job cost analytics | Yes | Yes |
The migration
yaml
jobs: build:- runs-on: warp-ubuntu-latest-x64-4x+ runs-on: runnerhut-8vcpu-ubuntu-2404 steps: - uses: actions/checkout@v4And 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-latestChecklist
- Install the runnerhut GitHub App on the repositories you want to move
- Change runs-on in one job first and compare timings against the old runner
- Add runner.arch to cache keys if you are also moving to arm64
- Roll out to the rest of the repository once the comparison looks right
- 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.
Related
GitHub-hosted runnersThe default runners built into GitHub Actions. Zero setup, billed per minute against your GitHub plan, with larger runners and native arm64 available on paid tiers.BlacksmithA YC-backed managed runner platform positioned as a drop-in GitHub Actions replacement, advertising up to 2× faster CI with faster caching and lower cost. Raised a Series B led by Peak XV and is SOC 2 Type 2 compliant.NamespaceEphemeral compute for CI and development: drop-in GitHub runners alongside devboxes, sandboxes and ephemeral Kubernetes clusters, with Bazel remote execution and egress filtering.UbicloudAn open-source cloud that runs managed GitHub Actions runners alongside managed Postgres and Kubernetes, competing primarily on price-performance and on being open and portable.