Migrate from GitHub-hosted runners to runnerhut

What GitHub-hosted runners does well

• Zero configuration — nothing to install, nothing to trust
• Billing already consolidated on your GitHub invoice
• Native arm64 and larger runner sizes on paid plans
• Backed by GitHub's own support and status page

Where we differ

• Roughly twice the per-minute price of runnerhut on every OS
• No EU-only residency for Actions compute, cache and logs — GitHub is a US-headquartered Microsoft subsidiary
• Cache is capped at 10 GB per repository and evicted aggressively
• Cache restore is throttled — large caches often take minutes
• Standard runners use shared vCPU with noisy-neighbour variance
• Docker layer cache has to be rebuilt or shipped to a registry yourself
• No cross-workflow cache sharing and no cache analytics

The migration

jobs:
  build:
-   runs-on: ubuntu-latest
+   runs-on: runnerhut-8vcpu-ubuntu-2404
    steps:
      - uses: actions/checkout@v4

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.

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