Six regions, six member states
EU regions
Frankfurt, Paris, Amsterdam, Stockholm, Milan and Dublin. Pick one and every part of your CI stays there.
Frankfurt
Germany
Paris
France
Amsterdam
Netherlands
Stockholm
Sweden
Milan
Italy
Dublin
Ireland
Region choice matters for two different reasons that are easy to conflate: latency to your own infrastructure, and the legal boundary your data sits inside. Both are satisfied by pinning, but they point at different regions.
| Region | Location | Member state |
|---|---|---|
| eu-central-1 | Frankfurt | Germany |
| eu-west-3 | Paris | France |
| eu-west-1 | Amsterdam | Netherlands |
| eu-north-1 | Stockholm | Sweden |
| eu-south-1 | Milan | Italy |
| eu-west-2 | Dublin | Ireland |
Choosing one
- Pick the region closest to the services your build talks to — registries, package mirrors, internal APIs
- If a public-sector or regulated customer requires a specific member state, pick that one and pin it
- Multi-region is available: label per region and route workloads independently
- Cache is regional, so a job in Frankfurt does not warm the Paris cache
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.