Supported GCP regions
Glean can host your tenant in any Google Cloud Platform (GCP) region that offers the GCP services a Glean deployment uses. The supported regions on this page are regions that Glean has validated. If your organization needs a region that isn't listed, ask Glean to confirm that the region offers the required services.
The default region for tenants hosted by Glean is us-central1, which is located in North America. Tell Glean if you want your tenant deployed in a different region.
Considerations for region selection
- GCP service availability — The region must offer the services that Glean deploys, including Cloud Run functions and GPU accelerators for machine learning workflows. If the region doesn't offer Cloud Tasks or Cloud Scheduler, Glean runs those services in a fallback region. Glean's machine learning pipelines don't use Tensor Processing Unit (TPU) accelerators, so TPU availability doesn't affect region selection.
- GPU accelerator choice — The GPU types on offer vary by region, and Glean runs its machine learning workflows on the GPUs that the region provides. A region with fewer or smaller GPU types can increase infrastructure cost and reduce machine learning performance.
- Data residency — Choose a region in the country or geography that your data residency requirements specify.
- Model availability in Vertex AI — This applies only if you use Vertex AI to access models. If you use Glean's model key or your own Azure OpenAI, OpenAI, or Anthropic account key, you can disregard it. For details, see Model availability in Vertex AI.
Supported regions
Glean supports the following regions in the Americas (AMER), Asia Pacific (APAC), and Europe, the Middle East, and Africa (EMEA).
- AMER
- APAC
- EMEA
| Location | GCP Region | GCP Zone |
|---|---|---|
| USA (Iowa) | us-central1 | us-central1-a |
| Brazil (Sao Paulo) | southamerica-east1 | southamerica-east1-a,c |
| Canada (Montreal) | northamerica-northeast1 | northamerica-northeast1-c |
| Location | GCP Region | GCP Zone |
|---|---|---|
| Australia (Sydney) | australia-southeast1 | australia-southeast1-a,c |
| India (Mumbai) | asia-south1 | asia-south1-a,b |
| Japan (Tokyo) | asia-northeast1 | asia-northeast1-a |
| Singapore (Jurong West) | asia-southeast1 | asia-southeast1-c,b,a |
| South Korea (Seoul) | asia-northeast3 | asia-northeast3-b,a,c |
| Taiwan (Changhua County) | asia-east1 | asia-east1-c |
| Location | GCP Region | GCP Zone |
|---|---|---|
| Belgium (St. Ghislain) | europe-west1 | europe-west1-b,c,d |
| Germany (Frankfurt) | europe-west3 | europe-west3-b |
| Israel (Tel Aviv) | me-west1 | me-west1-b,c |
| Netherlands (Eemshaven) | europe-west4 | europe-west4-a |
| Poland (Warsaw) | europe-central2 | europe-central2-b,c |
| UK (London) | europe-west2 | europe-west2-a,b |
Where possible, use the first GCP zone listed for a region. Some zones offer higher-memory GPUs that are better suited to machine learning workflows.
In EMEA, europe-west1 (Belgium) offers more GPU types than europe-west2 (London) and europe-central2 (Warsaw). If your organization can use any EU region, europe-west1 is a good choice.
europe-west4 (Netherlands) doesn't offer Cloud Tasks, so for tenants in europe-west4, Glean deploys Cloud Tasks in europe-west1 (Belgium). Cloud Scheduler runs in the selected region when it's available there, and falls back to europe-west1 otherwise.
Cost by region
Infrastructure cost varies by region, mostly because of the GPU types each region offers.
- For Glean-hosted tenants: Subscription pricing can be higher in regions with higher infrastructure costs. Your Glean account team can confirm pricing for your region.
- For customer-hosted tenants: Expect the monthly infrastructure cost for the Glean component of your GCP billing account to vary by region.
Model availability in Vertex AI
If you want Glean to access your model through Vertex AI, check that the model is available in Vertex AI in your GCP region.
- More information: Generative AI on Vertex AI locations (cloud.google.com)