AI features and models

Some UiPath services use AI-powered capabilities delivered through third-party large language models (LLMs), including the GPT family (via Azure OpenAI Service) and Claude models (via Amazon Bedrock).

Automation Cloud Public Sector organizations are available exclusively in the United States. All LLM endpoints that power AI features for public sector organizations are hosted in the United States, ensuring that data is processed in the same region as your organization and tenants.

UiPath does not control the geographic availability of third-party LLMs. However, UiPath works closely with providers to ensure continued model availability in the US region for public sector customers.

How data is processed

When you use an AI feature, the data path involves three separate regions:

Region types	Description	Who controls it
Organization region	The region where your UiPath organization is provisioned. The organization region is considered for services enabled at the organizational level, that inherit the organization region (for example, Apps, Automation Ops, and Studio Web).	You choose the organization region when you create the organization. An organization region is not visible in the UI.
Tenant region	The region where a tenant-level service (for example, Orchestrator, Test Manager, or Agents) is hosted and processes data.	You choose the tenant region when you create the tenant. A tenant's region is visible in the UI, from the tenant dropdown.
LLM processing region	The region where the third-party model actually runs.	Determined by the third-party LLM provider. For Automation Cloud Public Sector, all available LLM endpoints are located in the United States, matching the organization and tenant region.

For Automation Cloud Public Sector, all three regions are the United States. Data used when working with AI features is processed in the same region as your organization and tenants — no cross-region routing occurs.

AI features residency

Check the following definitions to understand the residency scopes used when working with UiPath's AI features:

• Organization region: The geographic region you select when creating your UiPath organization. This determines where your organization data is stored, including the data for services that inherit the organization region. Such services are marked as Organization-level in the Global cloud regions table.
• Tenant region: The region where a tenant is hosted and where its services (for example, Orchestrator, Test Manager, or Agents) operate. Services that inherit the tenant region are marked as Tenant-level in the Global cloud regions table.
• Service region: The region where a specific service within an organization or tenant runs. In most cases, all services in a tenant follow the tenant region, but some follow the organization region. The data residency of a service is marked in the Global cloud regions table as either inheriting the organization region or tenant region, along with its availability across cloud regions.
• LLM model endpoint region: The region where the third-party large language model (LLM) executes data processing. For Automation Cloud Public Sector, all LLM model endpoints are located in the United States.

Models consumed by Autopilot

Some UiPath services use AI models that are consumed through Autopilot, alongside other proprietary AI capabilities specific to those services. Because Autopilot capabilities are shared across multiple UiPath services, we document Autopilot-consumed models by Autopilot type to clearly indicate how models are used and reused.

Categorizing models by Autopilot type helps you understand which Autopilot capability consumes a given model and how the same model may be reused across multiple services.

The following Autopilot types are used when documenting model consumption:

• Autopilot Chat: Represents the conversational interface that enables natural-language interaction with UiPath products. Models in this category power chat-based assistance, explanations, and guidance within supported services. Currently, Autopilot Chat is surfaced in the following services: Orchestrator, Studio, and Test Manager.
• Autopilot for Developers: Represents capabilities that help generate and refine automations or agents using prompt-based generation. Models in this category support developer-focused scenarios such as creating workflows, improving logic, and accelerating automation development. Currently, Autopilot for Developers is surfaced in the following services: Apps and Studio.
• Autopilot for Testers: Represents capabilities that accelerate the testing lifecycle using prompt-based generation. Models in this category support generating, refactoring, and analyzing test cases. With a single natural-language prompt, you can create or modify manual, low-code, or coded test cases directly within Studio, or Test Manager.

Available models

The following table lists the models available to Automation Cloud Public Sector organizations and the UiPath services that use them. All models are served from endpoints in the United States.

UiPath Service	Vendor	Model
Autopilot for Everyone	Anthropic	anthropic.claude-sonnet-4-5-20250929-v1:0
	Microsoft/OpenAI	gpt-4o-2024-11-20
	Microsoft/OpenAI	text-embedding-ada-002
Context Grounding	Microsoft/OpenAI	text-embedding-3-large
Document Understanding	Microsoft/OpenAI	gpt-4o-2024-11-20
	Microsoft/OpenAI	text-embedding-3-large
	Microsoft/OpenAI	text-embedding-ada-002
GenAI Activities	Anthropic	anthropic.claude-haiku-4-5-20251001-v1:0
	Anthropic	anthropic.claude-sonnet-4-5-20250929-v1:0
	Microsoft/OpenAI	gpt-4o-2024-11-20
Test Manager	Anthropic	anthropic.claude-sonnet-4-5-20250929-v1:0
	Microsoft/OpenAI	gpt-4o-2024-11-20

Data residency

Automation Cloud Public Sector organizations are available in the United States only. All models listed in the table above are available in the US. Because all models are served in the same region where public sector organizations reside, data residency is maintained for all listed models — your data is not routed outside the United States when using AI features.

Note:

You can disable Anthropic models for your organization using the AI Trust Layer policies in Automation Ops. To manage which models are available to your users, go to Settings for AI Trust Layer policies and use the Models tab of the policy.