We are excited to announce that Tower has officially expanded into the Asia-Pacific (APAC) region!
To better support our global users and meet growing demand, we have launched two brand-new execution data planes in
Tokyo (AWS ap-northeast-1) and Sydney (AWS ap-southeast-2).
Whether you are looking to keep compute closer to your local data stores, improve latency, or satisfy data residency
requirements, you can now run your workloads directly across the APAC region.
Performance Boost: Pre-Provisioned Warm Pods
Along with these new regions, we have introduced a major infrastructure performance upgrade. To eliminate cold-start overhead, our newer data planes now utilize pre-provisioned warm pods:
- Near-Zero Pod Initialization Latency: Instead of spinning up a fresh container on every run, workloads are immediately injected into pre-initialized containers. This avoids the typical container spin-up delays on Kubernetes, leading to significantly faster start times.
- Smoother Scaling Under Heavy Load: Resources are pre-allocated, ensuring that sudden spikes in traffic scale smoothly without introducing unexpected latency spikes.
All Available Tower Execution Regions
With this launch, Tower now supports six execution data planes worldwide:
| Cloud | Region Code | Location | Availability |
|---|---|---|---|
| AWS | ap-northeast-1 | Tokyo, Japan | New |
| AWS | ap-southeast-2 | Sydney, Australia | New |
| AWS | us-east-1 | North Virginia, USA | Available |
| AWS | us-west-2 | Oregon, USA | Available |
| AWS | eu-central-1 | Frankfurt, Germany | Available |
| AWS | eu-west-1 | Ireland | Available |
How to Switch Your Region
Configuring your team's execution region takes just a couple of clicks:
- Log into your Tower dashboard.
- Click your Profile icon in the top navigation.
- Select Team Settings.
- Under Execution Region, choose your preferred data plane from the dropdown.

Note: The selected region applies across all runs executed by your team.
You can create additional teams with different Execution Regions to
have runs in multiple concurrent regions.
What's Next?
We are constantly looking for ways to give you more control over your infrastructure. In future iterations, we are exploring features like multi-region team routing or dynamic region assignment per run.
Have thoughts on multi-region support or want to see a specific region added next? Join our Discord community and let us know what you'd like to build with us!
