Use case
Run in every region, manage one fleet.
Group servers by region, roll changes out one region at a time and see the whole fleet's health at a glance. When a region has a bad day, you'll know which one, and why.
A rollout of release r142 of the api service, region by region: all four servers in eu-central are done, us-east has two of three servers healthy and is still rolling, and ap-southeast waits for a ten-minute pause before it starts.
Staged rollouts
One region at a time, on purpose.
Pick the order, how long to watch each region and what counts as failure. If health checks fail in the first region, the others never see the release.
services:
api:
target: role=api
rollout:
order: [region=eu-central, region=us-east, region=ap-southeast]
pause: 10m # watch each region before the next
abort_on: health # stop everywhere if checks failBuilt for fleets that span the map
Regions are just labels
Tag servers with region=…, and every deploy, job and alert can target or group by it.
Health per region
See each region's servers, error rate and uptime side by side, and which release each one runs.
Per-region overrides
Secrets and settings can differ by region, like a nearby database or a regional API key.
Jobs once per region
Run a job on one healthy server in each region, instead of everywhere or only once.
Questions about multi-region
How do servers in different regions talk to each other?
Fwoop doesn't sit in your data path. Use your provider's private networking or a mesh such as WireGuard or Tailscale, as you would today.
What happens if the control plane is unreachable?
Agents keep running your services and their local cron schedules, and report back when they reconnect. Deploys wait until it's back.
Which plan includes multi-region rollouts?
Business and Enterprise. Smaller plans can still label servers by region and target them.
Bring your first server online in five minutes.
Start free with three servers. No credit card, no sales call, and your workloads stay on machines you own.