Half the cost. Twice the speed. Hosted in the EU.
Drop-in runners that cost 50% less and run 2× faster than GitHub-hosted — with every build, cache and log staying inside the EU. Change one line in your workflow.
No credit card required · 3,000 free minutes · Six EU regions
- 50% cheaper than GitHub-hosted
- 2× faster pipelines
- EU-only data residency
jobs: test:- runs-on: ubuntu-latest+ runs-on: runnerhut-8vcpu-ubuntu-2404 steps: - uses: actions/checkout@v4 - run: npm ci && npm testTrusted by engineering teams shipping every day
Pricing
Half the price, before you count the time saved
Per-minute rates against GitHub-hosted list prices. The real saving is larger, because a runner that finishes in half the time bills half as many minutes.
| Runner | GitHub | runnerhut |
|---|---|---|
| Linux x64 | $0.0080 | $0.0040 |
| Linux arm64 | $0.0050 | $0.0032 |
| Windows | $0.0160 | $0.0080 |
| macOS | $0.0800 | $0.0400 |
GitHub list prices as published August 2026.
Your builds never leave the EU
Compute, cache, logs, metrics and support access — all pinned to the EU region you choose. Not just the compute. Residency that covers only compute is not residency.
- Job compute
- Cache objects
- Job logs
- Metrics
- Support access
Pinned to your region
Frankfurt
Germany
eu-central-1
Paris
France
eu-west-3
Amsterdam
Netherlands
eu-west-1
Stockholm
Sweden
eu-north-1
Milan
Italy
eu-south-1
Dublin
Ireland
eu-west-2
runnerhut
Everything GitHub-hosted runners leave on the table
The bottleneck is rarely the CPU. It is the cache, the disk and the queue — and for European teams, where the whole thing runs.
Unlimited cache at 1 GB/s
No 10 GB repository cap and no throttling. Caches are organisation-scoped, so a new branch starts warm instead of cold.
Persistent Docker layer cache
A warm BuildKit instance your job attaches to in under two seconds. Nothing is exported to a registry and pulled back.
Native arm64, 20% cheaper
Real aarch64 cores rather than QEMU. Multi-arch images build 5–40× faster and cost less per minute than x64.
macOS, Windows and GPU
Apple silicon with Xcode preinstalled, Windows Server with Build Tools, and NVIDIA runners GitHub does not offer at all.
Per-job cost and utilization
Duration percentiles, cache hit rate and spend per workflow, label and repository — so you tune the right thing.
Your cloud, if you want it
Run inside your own AWS, GCP or Azure account with your VPC, your IAM and your data residency boundary.
Three steps, about five minutes
There is no agent to install and no infrastructure to operate.
- 01
Install the app
Authorise the runnerhut GitHub App for the repositories you want to accelerate.
- 02
Change runs-on
Swap ubuntu-latest for a runnerhut label. Nothing else in your workflow changes.
- 03
Watch the numbers
Per-job duration, cache hit rate and cost land in your dashboard from the first run.
How we compare
Honest comparisons, including where the other option is the right one.
Solutions by stack
What is slow in your language or framework, and how to fix it.
Blog
See allWhat we learned running a million CI jobs
Queue time, cache behaviour, right-sizing and the failure modes that only appear at scale.
2026-08-04 · 11 min readbenchmarksThe 10 GB cache limit is the real CI bottleneck
We instrumented 40,000 workflow runs. Cache behaviour predicted wall-clock time better than vCPU count, and most teams cross the cap without ever noticing.
2026-07-02 · 9 min readcompanyBuildJet shut down. Here is what that means for managed CI.
A competitor exiting the category is worth taking seriously rather than spinning. Here is our honest read on why BuildJet closed and what it says about managed runners.
2026-04-14 · 7 min readYour 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.