Understand your UiPath deployment

A deployment or delivery option defines who hosts and manages the UiPath platform you use.

Note:

A deployment model describes where and how the UiPath platform is hosted. For example, Automation Cloud (hosted by UiPath) or Automation Suite (hosted by your organization). A version describes which software release is running on that platform, for example, 2024.10. Two organizations can both be on Automation Suite but on different versions. An organization can upgrade its version without changing its deployment model. Knowing your version does not indicate your deployment model, and vice versa.

There are three deployment models:

• UiPath-managed (SaaS), where UiPath hosts and maintains the platform. You access it through a UiPath-provided URL, and UiPath handles infrastructure, upgrades, and maintenance. This model comes in three different flavors: Automation Cloud, Public Sector, and Dedicated.
• Customer-managed, where your organization installs and operates the platform on infrastructure it controls, either on-premises or in a private cloud. Your IT team is responsible for upgrades and ongoing operations. It comes in several installation flavors dpeending on your infrastructure.
• Standalone is also a customer-managed deployment model. Individual UiPath products are installed and maintained separately, outside of the unified Automation Suite platform.

Your deployment model determines where you access the platform, how data is managed, which capabilities are available, and who is responsible for maintenance.

Clarifying the role of Orchestrator

A clear understanding of Orchestrator is essential before examining each deployment model.

Orchestrator is UiPath's core automation management service. It handles robot execution, job scheduling, queues, assets, and more. Orchestrator is present in every UiPath deployment - it is not a deployment model itself. In early versions of the UiPath platform, Orchestrator was commonly installed as a standalone, on-premises server application. As a result, the term "Orchestrator" was sometimes used informally to refer to that specific installation model.

Today, Orchestrator is available across deployment models. Therefore, stating that you "use Orchestrator" does not indicate which deployment model you are using. The relevant distinction is which deployment option hosts your Orchestrator instance.

All deployment models at a glance

The table below provides a high-level comparison of all UiPath deployment options, including who manages them, how they are accessed, and the underlying infrastructure model.

For more detailed information about each deployment model, see Cloud platforms and On-premises platforms.

Table 1. Deployment models at UiPath

Deployment	Managed by	Access URL	Description
Automation Cloud	UiPath	https://cloud.uipath.com	Automation Cloud is the default multi-tenant SaaS platform, providing access to the full UiPath product suite.
Automation Cloud Public Sector	UiPath	https://govcloud.uipath.us	Automation Cloud Public Sector is a dedicated SaaS environment for US government organizations that meets FedRAMP Moderate requirements and restricts access to US-based citizens and permanent residents.
Automation Cloud Dedicated	UiPath	https://<customURL>.dedicated.uipath.com	Automation Cloud Dedicated is a single-tenant SaaS environment with isolated compute and data resources, fully managed by UiPath.
Test Cloud	UiPath	https://cloud.uipath.com	Test Cloud is UiPath’s SaaS testing platform, providing application testing, test management, execution scheduling, and Test Manager integration.
Test Cloud Public Sector	UiPath	https://govcloud.uipath.us	Test Cloud Public Sector is a SaaS environment for US government organizations that provides FedRAMP-compliant testing for government QA workflows.
Test Cloud Dedicated	UiPath	https://<customURL>.dedicated.uipath.com	Test Cloud Dedicated is a single-tenant SaaS testing environment with isolated resources, designed for enterprises with strict compliance or isolation requirements.
Automation Suite	Your organization	https://<yourDomain>.com (Custom company URL)	Automation Suite is UiPath’s Kubernetes-based, Linux (including OpenShift) on-premises platform that bundles multiple products into a single deployment.
Standalone	Your organization	https://<yourDomain>.com (Custom company URL)	Standalone refers to individual UiPath products installed separately on Windows Server using Windows installers.
Test Cloud (on-premises)	Your organization	https://<yourDomain>.com (Custom company URL)	Test Cloud (on-premises) is UiPath's Kubernetes-based, Linux (including OpenShift) on-premises testing platform that bundles multiple products into a single deployment.

Identify your deployment model and version

There are several ways to check which deployment you are on, depending on what you have access to. The fastest method is by checking the URL you use to log in to the UiPath platform.

Tip:

Want to know which deployment model your product is available in? See Product and feature availability across delivery options.

Check your URL

Look at the URL you use to log in to the UiPath platform.

Table 2. URL identification table

If your URL starts with...	You're on...
https://cloud.uipath.com	Automation Cloud or Test Cloud
https://govcloud.uipath.us	Automation Cloud Public Sector or Test Cloud Public Sector
https://<customURL>.dedicated.uipath.com	Automation Cloud Dedicated or Test Cloud Dedicated (UiPath manages your application)
https://<yourDomain>.com	Automation Suite or Test Cloud (on-premises) Your IT team manages your application.
https://<yourDomain>.com	Standalone (your IT team manages your application)

Check from the login page

You can also identify your deployment by the URL and sign-in options on the login screen.

Table 3. Login identification table

Deployment	URL	Notes
Automation Cloud or Test Cloud	https://cloud.uipath.com	Shows sign-in options for email or password, Google, and Microsoft.
Automation Cloud or Test Cloud Public Sector	https://govcloud.uipath.us	Shows sign-in options for email or password, and Microsoft.
Automation Cloud or Test Cloud Dedicated	https://<customURL.dedicated.uipath.com	Shows sign-in options for email or password, and Enterprise SSO (if configured by your administrator).
Automation Suite or Test Cloud (on-premises)	https://<yourDomain>.com (Custom company URL)	You sign in through a unified portal that manages authentication and access across all products in the suite.
Standalone	https://<yourDomain>.com (Custom company URL)	None.

Check from within the product (for standalone applications)

If you're not sure whether you're on a standalone deployment, your best bet is to check with your IT or infrastructure team. Some products also have in-product indicators that can help confirm this.

Table 4. Standalone guidelines

Product	How to identify a standalone deployment
AI Center	Check which Orchestrator instance AI Center is connected to. In this configuration, AI Center is part of Automation Suite but connected to an external standalone Orchestrator, rather than one hosted within the suite.
AI Computer Vision	To confirm you are on a standalone deployment, check how you access AI Computer Vision. If you access it from your local system, you are on a standalone deployment.
Assistant	To confirm you're using Assistant standalone, check how you are accessing it. If Assistant is a desktop application running from your system tray, you are using Assistant standalone. If you are accessing Assistant through a browser, you are using Assistant Web, which is part of Automation Cloud.
Document Understanding	For AI Center-based projects, Document Understanding runs on top of AI Center and follows the same configuration: AI Center is part of Automation Suite connected to an external standalone Orchestrator. For modern projects, this configuration does not apply. Modern projects run exclusively within Automation Suite, independently of AI Center.
Insights	In the Templates section, a standalone deployment shows fewer dashboard templates than the cloud version. This is because certain integrations - such as Action Center and Document Understanding - are available only on cloud.
Orchestrator	Both Automation Suite and Standalone use a custom internal URL, so the URL alone does not distinguish between the two. For a definitive answer, contact your IT or infrastructure team.
Process Mining	Standalone Process Mining is installed and licensed separately from the cloud and Automation Suite versions. The User Interface (UI) does not include the platform-level navigation view present in Automation Cloud and Automation Suite.
Studio	To confirm you are using Studio standalone, check how you are accessing Studio. If you opened Studio from an icon on your desktop or taskbar, you are using Studio Desktop. If you are accessing Studio through a browser, you are using Studio Web.
StudioX	StudioX is only available as a standalone deployment. It is installed locally on your desktop. Your robot runs locally and is managed through UiPath Assistant on your desktop. Starting with Studio 2025.10.1, StudioX capabilities are integrated in Studio.
Task Capture	Task Capture is only available as a standalone deployment.
Test Manager	If you're on MSI (Standalone), your URL is a custom URL chosen by your organization and the UI does not include platform-level navigation.