One stack per region, routed by label

Multi-region BYOC

Run BYOC stacks in several regions for latency, resilience or data residency, and route workloads with runner labels.

Deploy the module once per region. Each stack is independent — its own capacity, its own cache bucket, its own labels — which is what makes regional pinning enforceable rather than advisory.

yaml

jobs:
  eu-build:
    runs-on: runnerhut-8vcpu-ubuntu-2404-eu-central
  us-build:
    runs-on: runnerhut-8vcpu-ubuntu-2404-us-east

Things that do not cross regions

Cache — a job in Frankfurt does not warm the Dublin cache
Snapshots — they are tied to the region that created them
Capacity — a shortage in one region does not spill into another, by design

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 building See pricing

Capacity and cloud quotasThe limit you will hit first is your own Updating a BYOC stackVersioned module, drained rollout

Multi-region BYOC

Things that do not cross regions

Your next build could be twice as fast, at half the price

Related