- Getting started
- Data security and compliance
- Organizations
- Authentication and security
- Licensing
- About licensing
- Unified Pricing: Licensing plan framework
- Flex: Licensing plan framework
- Activating your Enterprise license
- Upgrading and downgrading licenses
- Requesting a service trial
- Assigning licenses to tenants
- Assigning user licenses
- Deallocating user licenses
- Monitoring license allocation
- License overallocation
- Licensing notifications
- User license management
- Tenants and services
- Accounts and roles
- Testing in your organization
- AI Trust Layer
- External applications
- Notifications
- Logging
- Troubleshooting
- Migrating to Automation Cloud
Automation Cloud admin guide
Automation Cloud™ is deployed across various global regions for optimal coverage for our diverse worldwide customer base. As our cloud infrastructure expands, we can better meet global needs for data sovereignty while maintaining high availability and low latency, providing a robust foundation for cloud deployment.
Determining regions for cloud organizations and tenants depends on licensing plans and regional preferences. This documentation aims to show where your business data is stored globally.
Automation Cloud organization data includes critical information such as user identity, metadata, and license details. Each Automation Cloud organization is assigned a unique hosting region based on licensing plans and regions selected by admins.
Each cloud organization has a single region, and enterprise customers have multi-regionality options for their organizations' tenants.
Data residency for cloud organizations
Community
Data for cloud organizations created using community plan is stored in community data centers in the European Union.
Free
Data for cloud organizations created using free plan is stored in community data centers in the European Union.
Pro trial
Data for cloud organizations created using pro trial plan is stored in the region selected during creation.
Pro
Customers on pro plans inherit the organization region. If your organization was created using a non-commercial community or free plan, the data is hosted in the European Union.
Enterprise
Customers on enterprise plans inherit the organization region. If your organization was created using a non-commercial community or free plan, the data is hosted in the European Union. If you are interested in upgrading your plan, contact a sales expert.
Data residency for cloud tenants
Community
A single cloud tenant is provisioned by default for a cloud organization created using Community plan. Data for this tenant is stored in Community scale unit in the European Union.
Free
A single cloud tenant is provisioned by default for a cloud organization created using Free plan. Data for this tenant is stored in community scale unit in the European Union.
Pro Trial
Customers using Pro Trial are offered up to three cloud tenants. These tenants are automatically created in the same region as the cloud organization region selected during sign-up.
Pro
Customers on Pro plans will inherit the tenant(s) region(s).
-
If your organization was created using Community plan, tenant data is hosted in the European Union.
-
If your organization was created using Free plan, tenant data is hosted in the European Union.
-
If your organization was created using Pro Trial plan, tenant data is stored in the same region as the cloud organization region selected during sign-up.
-
For newly created tenants, the data is stored in the same region as the cloud organization region selected during sign up.
Enterprise
Customers on Enterprise plans will inherit tenant(s) region(s).
-
If your organization was created using Community plan, tenant data is hosted in the European Union.
-
If your organization was created using Free plan, tenant data is hosted in the European Union.
-
If your organization was created using Pro Trial plan, tenant data is stored in the same region as the cloud organization region selected during sign-up.
-
For newly created tenants, the data is stored in the region chosen by admins during creation.
Establishing the region for newly created cloud tenants has no effect on already-created cloud tenants in your organization. Customers using Enterprise plans can request changes to regions elections they made in the past for their cloud organization or their tenants. You can contact support to request to schedule the data move to a different region.
In cases where Enterprise customers do not explicitly make region elections for their organizations or default tenants, we proactively move the customer data (from the organization and tenant services) to the corresponding scale units, to ensure the cloud services are deployed in optimal regions worldwide. We use predefined rules to determine region selection. However, in certain situations, our rules might default services to Enterprise scale units in the European Union, if a more suitable location was not identified.
The following table describes data residency for Automation Cloud organization and tenants in accordance with their used plans:
| Data residency for Automation Cloud organization and tenants |
Pro |
Enterprise | |||
|---|---|---|---|---|---|
| Cloud organization regions | European Union only | European Union only |
1 chosen region |
Inherited |
Inherited (can be changed) |
| Tenant regions | European Union only | European Union only |
1 chosen region |
1 inherited region |
Inherited for Default Tenant (can be changed) Note:
Multiple regions are available for new tenants. |
| Max. number of tenants |
1 |
1 |
3 |
3 |
As needed |
Community and Free plans are for non-commercial use only. If you want to test Automation Cloud before buying a license, start with a Pro Trial plan.
- Where each service is available.
- How UiPath handles data residency.
- What exceptions apply to data residency.
Service provisioning and data handling
Before you check the data residency of each service, keep the following in mind:
- Products are provisioned either at the tenant level or the organizational level.
- When a product is available in a region, UiPath stores and processes data mainly in that region.
Note: Some services might process data beyond their designated storage region. However, no data is stored outside the services' respective region.
- If a product uses AI-powered features, data may be temporarily routed to a nearby region where a specific model is available.
UiPath does not store data in the routed region. Product sections document this behavior in detail.
|
Service | Provisioning type |
European Union (EU) |
United States (US) |
Japan (JA) |
Canada (CA) |
Australia (AU) |
Singapore (SI) |
United Kingdom (UK) |
India (IN) |
United States (delayed region) |
European Union (delayed region) |
|---|---|---|---|---|---|---|---|---|---|---|---|
|
Action Center (Actions and Processes) | Tenant level |
|
|
|
|
|
|
|
|
|
|
| Agents | Tenant level |
|
|
|
|
|
|
|
|
|
|
|
AI Center | Tenant level |
|
|
|
|
|
|
|
|
|
|
|
AI Computer Vision | Tenant level |
|
|
|
|
|
|
|
|
|
|
|
Apps | Organization level |
|
|
|
|
|
|
|
|
|
|
|
Automation Cloud portal1 | N/A |
|
|
|
|
|
|
|
|
|
|
|
Automation Hub | tenant level |
|
|
|
|
|
|
|
|
|
|
|
Automation Ops | Organization level |
|
|
|
|
|
|
|
|
|
|
|
IXP | Tenant level |
|
|
|
|
|
|
|
|
|
|
|
Context Grounding | Tenant level |
|
|
|
|
|
|
|
|
|
|
|
Data Fabric | Tenant level |
|
|
|
|
|
|
|
|
|
|
|
Document Understanding Note: Currently, Uipath DocPath is only available for US-based tenants.
| Tenant level |
|
|
|
|
|
|
|
|
|
|
|
Insights | Tenant level |
|
|
|
|
|
|
|
|
|
|
|
Integration Service | Tenant level |
|
|
|
|
|
|
|
|
|
|
|
Maestro | Tenant level |
|
|
|
|
|
|
|
|
|
|
|
Orchestrator (including ACR - VM and ACR - Serverless) | Tenant level |
|
|
|
|
|
|
|
|
|
|
|
Process Mining | Tenant level |
|
|
|
|
|
|
|
|
|
|
| Studio Web | Organization level |
|
|
|
|
|
|
|
|
|
|
|
Task Mining | Tenant level |
|
|
|
|
|
|
|
|
|
|
|
Test Manager | Tenant level |
|
|
|
|
|
|
|
|
|
|
Platform considerations
The Automation Cloud portal includes the home page, all pages under Admin, and the Resource center (Help) page. For a list of all services handled by an organization administrator, refer to Administration services and capabilities.
AI Computer Vision considerations
- Design-time data is centralized in the European Union and in the United States of America, no matter the region of origin.
- The service is available worldwide and it can be accessed from any location around the world. For more details, check the Public endpoints page.
- In the case of a regional Azure failure, to ensure continued service operation for our customers, global AI Computer Vision
traffic (using the
cv.uipath.comendpoint) may be temporarily failed over/redirected to another Azure data center location. The redirection will happen in the same geography, if possible (for example, traffic usually served by the North Europe Azure data center will be redirected to West Europe, if possible, in case of a regional failure in North Europe). In case redirection in the same geography is not possible (examples include, but are not limited to: insufficient GPU availability in Azure or disasters affecting both the primary and secondary regions in a geography), traffic may be redirected to another geography. The redirection will happen for a limited time, until the regional failure has stopped and the service has stabilized.
AI features and model routing
Some UiPath services use AI-powered features delivered through third-party AI models from Azure OpenAI, Google Gemini, and Anthropic Claude. These models are hosted in specific regions. When a model is not available in the same region as the service, UiPath routes data temporarily to the nearest region with an available model endpoint.- AU—Australia
- CA—Canada
- EU—European Union
- IN—India
- JA—Japan
- SI—Singapore
- UK—United Kingdom
- US—United States
| Service | Model type and version | Endpoint region availability | Fallback routing behavior | Notes |
|---|---|---|---|---|
| Apps | Azure OpenAI | CA, EU, US | For AU, IN, SI, data is re-routed to EU. | N/A |
| Agents | GPT 4o-x | EU, JA, US | Fallback to the closest supported region. | N/A |
| Agents | Claude 3.5/3.7 |
| Fallback to the closest supported region. | N/A |
| Agents | Gemini | EU, US | Fallback to the closest supported region. | N/A |
| Autopilot for Developers | Azure OpenAI
| AU, CA, EU, IN, JA, SI, UK, US |
| N/A |
| Autopilot for Developers | Google Gemini
| AU, CA, EU, IN, JA, SI, UK, US |
| N/A |
| Autopilot for Developers | Anthropic Claude
| AU, CA, EU, IN, JA, SI, UK, US |
| N/A |
| Autopilot for Everyone | Azure OpenAI
| AU, CA, EU, IN, JA, SI, UK, US |
| Autopilot for Everyone stores customer data in Orchestrator, for the following regions: EU, JA, US, and US delayed. |
| Autopilot for Everyone | Azure OpenAI
| AU, CA, EU, IN, JA, SI, UK, US | Fallback to the closest supported region. | Autopilot for Everyone stores customer data in Orchestrator, for the following regions: EU, JA, US, and US delayed. |
| Autopilot for Everyone | Azure OpenAI
| AU, CA, EU, IN, JA, SI, UK, US |
| Autopilot for Everyone stores customer data in Orchestrator, for the following regions: EU, JA, US, and US delayed. |
| Autopilot for Everyone | Google Gemini
| EU, JA, US | Fallback to the closest supported region. | Autopilot for Everyone stores customer data in Orchestrator, for the following regions: EU, JA, US, and US delayed. |
| Autopilot for Everyone | Anthropic Claude
| AU, CA, EU, IN, JA, SI, UK, US |
| Autopilot for Everyone stores customer data in Orchestrator, for the following regions: European Union, United States, Japan, and United States (delayed region). |
| Autopilot for Everyone | Anthropic Claude
| AU, CA, EU, IN, JA, SI, UK, US |
| Autopilot for Everyone stores customer data in Orchestrator, for the following regions: EU, JA, US, and US delayed. |
| Autopilot for Everyone | Anthropic Claude
| AU, CA, EU, IN, JA, SI, UK, US |
| Autopilot for Everyone stores customer data in Orchestrator, for the following regions: EU, JA, US, and US delayed. |
| Data Fabric | Azure OpenAI | EU, JA, US | For AU, CA, IN, SI, UK , data is re-routed to the EU. | N/A |
| Document Understanding | Azure OpenAI | AU, CA, EU, EU (delayed), IN, UK, US, US (delayed) |
| The generative model is deployed the same way as our specialized pre-trained models, hence, the same data privacy applies. |
| IXP | Azure OpenAI | AU, CA, EU, EU (delayed), IN, UK, US, US (delayed) | For SI, data is re-routed to the EU. | N/A |
| Studio Web | Azure OpenAI | AU, EU, EU (delayed), US, US (delayed) | For CA, IN, SI, UK , data is re-routed to EU. | N/A |
| Test Manager | Azure OpenAI | EU, JA, US |
| N/A |
| Test Manager | Google Gemini | EU, US |
| N/A |
| Test Manager | Anthropic Claude | EU, US |
| N/A |
We consistently deploy new releases every two weeks for cloud products and services, adhering to the company's safe and secure deployment practices.
Initial deployment is made available to community users where applicable, and later to enterprise customers within a one hour to 14-day window post community deployment.
Delayed ring deployments
Automation Cloud™ is available in cloud scale units in the United States and the European Union with delayed deployments.
To ensure GxP regulatory compliance in life sciences, UiPath® offers Advanced Platform SKU customers the option of a delayed update scale unit for their Automation Cloud setup. Typically, customers utilize a standard scale unit for testing (in any of the Automation Cloud standard regions), alongside a second organization on a delayed update scale unit for production. Automation Cloud is available to customers in a delayed update scale unit accessible in the United States, and a second one in the European Union is available to enterprise customers.
Each Automation Cloud release reaches delayed update scale units at least 14 days after standard scale units, enabling customers to complete an evaluation before the update is released in the delayed scale unit.
Further details regarding delayed update scale units are available in Delayed update organizations.
- Data residency
- Organization and tenant services data
- Data residency for cloud organizations
- Data residency for cloud tenants
- Resources
- Global cloud regions
- Service provisioning and data handling
- Platform considerations
- AI Computer Vision considerations
- AI features and model routing
- Safe deployment practices
- Delayed ring deployments
