Skip to content
runnerhut
Start building
Managed GitHub Actions runners

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.

Start buildingSee pricing

No credit card required · 3,000 free minutes · Six EU regions

  • 50% cheaper than GitHub-hosted
  • 2× faster pipelines
  • EU-only data residency
yaml
jobs:
  test:
-   runs-on: ubuntu-latest
+   runs-on: runnerhut-8vcpu-ubuntu-2404
    steps:
      - uses: actions/checkout@v4
      - run: npm ci && npm test
2×
Faster pipelines
−50%
Lower CI spend
1 GB/s
Cache restore
3s
Runner start

Trusted by engineering teams shipping every day

NorthwindHarboursideKestrelOrbitalLumenFathomArcadiaBeaconVantageIronwoodNorthwindHarboursideKestrelOrbitalLumenFathomArcadiaBeaconVantageIronwood

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.

See pricing
RunnerGitHubrunnerhut
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.

EU hosting

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
EU hosting in detail

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.

  1. 01

    Install the app

    Authorise the runnerhut GitHub App for the repositories you want to accelerate.

  2. 02

    Change runs-on

    Swap ubuntu-latest for a runnerhut label. Nothing else in your workflow changes.

  3. 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.

runnerhut vs 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.runnerhut vs 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.runnerhut vs WarpBuildA hosted runner platform offering Linux, macOS and Windows runners plus bring-your-own-cloud deployments on AWS, GCP and Azure. Advertises roughly 2× faster builds at about half the cost of GitHub-hosted runners.runnerhut vs NamespaceEphemeral compute for CI and development: drop-in GitHub runners alongside devboxes, sandboxes and ephemeral Kubernetes clusters, with Bazel remote execution and egress filtering.runnerhut vs 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.Shut downrunnerhut vs BuildJetAnnounced 6 February 2026; stopped running jobs 31 March 2026.runnerhut vs DepotBest known for accelerated remote Docker builds, with GitHub Actions runners added alongside. Strongest when container image build time dominates your pipeline.runnerhut vs Actions Runner Controller (ARC)The open-source Kubernetes operator for self-hosted GitHub Actions runners. Free software, but you operate the cluster, the autoscaling, the images and the caching yourself.

Solutions by stack

What is slow in your language or framework, and how to fix it.

See all
RustCold build: 12m → 4mGoTest suite: 8m → 2mPythonInstall: 180s → 12sNode.jsnpm ci: 95s → 11sJavaDependency resolve: 120s → 4sKotlinCompile: 7m → 2mScalasbt startup: 90s → 8sRubybundle install: 140s → 6s

Blog

See all
engineering

What 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 readbenchmarks

The 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 readcompany

BuildJet 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 read

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.

Start buildingRead the docs