Infrastructure
Regions
Choose in which region to run your workloads.
Blaxel is available in many regions across the globe. Some types of resources can be deployed ‘globally’ over multiple regions (for example: agents), while some other types are deployed only in one specific region (for example: sandboxes).
This guide details the available regions for Mark 3 infrastructure generation.
All regions are not necessarily available in self-service by default. Please contact us if you would like access to a specific region.
Mark 2 infrastructure is globally distributed over 15 regions — it does not feature the ability to specify a single deployment region (except though deployment policies).
Available regions
The following regions are available for Mark 3 infrastructure generation:| Region code | Location | Country |
|---|---|---|
us-pdx-1 | Oregon | United States |
us-was-1 | North Virginia | United States |
eu-lon-1 | London | United Kingdom |
Selecting a region for deployment
When deploying a resource on Blaxel, you sometimes have the option to choose the deployment region. This depends on the type of resource, as explained below. For all resource types, the deployment region is always subject to the deployment policies applied to the resource or workspace. A resource will never be deployed in a region that is prohibited by an existing deployment policy.Resources which are globally distributed over multiple regions
This is the case of: When deploying For these types of resources, you don’t specify a region during deployment. The resource becomes available across all regions allowed by applicable deployment policies. When requesting For these types of resources, you receive a global query endpoint that automatically routes to the optimal region as determined by Blaxel’s Global Agentics Network.Resources which are deployed in one specific region
- sandboxes (and their preview URLs)