US West
us-west1Planned western US home for customers closest to the Pacific and Mountain regions.
- Google Cloud location
- Oregon and Los Angeles expansion path
- Launch availability
- Late 2026
- Latency guidance
Run AI systems from the right regional home.
EngineGrids starts new grids in Google Cloud us-east1 today, with additional regional homes planned for teams that need execution, operating records, and data boundaries close to their customers and systems.
EngineGrids regional footprint
EngineGrids regional homes are Google Cloud regions with explicit launch-readiness signals. us-east1 in South Carolina is available now for new grids; US West, Europe West, and Asia Southeast are planned expansion regions. Choose the operating home closest to your customers, operators, systems, and data requirements.
1Available now3Planned
US East
us-east1Available now for new grids serving customers, operators, and systems in the eastern half of the Americas.
- Google Cloud location
- South Carolina
- Launch availability
- Available for new grids
- Latency guidance
Europe West
europe-west1Planned European home for teams that need EU-adjacent latency and residency alignment.
- Google Cloud location
- Belgium and Netherlands expansion path
- Launch availability
- Late 2026
- Latency guidance
Asia Southeast
asia-southeast1Planned Asia-Pacific home for customers serving Southeast Asian operators and systems.
- Google Cloud location
- Singapore expansion path
- Launch availability
- Late 2026
- Latency guidance
Regional data placement
Place execution records, runtime activity, and customer-sensitive work in the region where the business carries responsibility.
Residency-aware operations
Keep intent, execution state, and audit history aligned with the selected regional data plane.
Google Cloud regional expansion
Start in available us-east1 and use planned regions as requirements expand across North America, Europe, and Asia Pacific.
Latency and responsibility
Use region selection to account for customer proximity, data requirements, and long-horizon operations.
Regional choice belongs in the operating model.
The question is not only where compute runs. It is where important work is recorded, reviewed, billed, and kept under control as grids move from a first launch to broader operations.
Start in the region that matches the first launch.
Use us-east1 when the first grid needs an available regional home in the eastern United States or the broader Americas.
Keep planned expansion explicit.
Treat US West, Europe West, and Asia Southeast as planned regional homes until they complete launch review.
Use geography as part of control.
Pair regional placement with approvals, marketplace access, and operating records so growth stays understandable.
Launch from the available regional home.
Start with us-east1 for new grids today, then expand regional coverage as the business has a reason to do so.