- Introduction
- Product lifecycle
- Licensing
- Delivery options
- Product availability
- Orchestrator differences
- UiPath Platform
- UiPath documentation
- Troubleshooting
Orchestrator differences
UiPath® Orchestrator has roughly the same capabilities across deployment options, but for a few notable exceptions, which are described on this page.
The information on this page refers to the following deployment options for Orchestrator:
-
On-premises deployment options:
- Standalone Orchestrator (on-premises, latest version)
- Orchestrator service in UiPath Automation Suite (on-premises platform, latest version)
- Cloud deployment: Orchestrator service in UiPath Automation CloudTM
Check this page periodically, as it is updated on a regular basis to reflect the differences between the deployment options.
|
On-premises behavior |
Cloud behavior | |
|---|---|---|
|
API Authentication |
On-premises Orchestrator can use:
|
Automation Cloud, and therefore Orchestrator as well, can use two mechanisms:
|
|
Libraries Feeds |
For on-premises Orchestrator, you can publish libraries both at host and tenant level feeds |
In Automation Cloud you can publish libraries only at tenant level. To share libraries between tenants, you can use a custom feed. |
|
Password Complexity Settings |
As an administrator of an on-premises Orchestrator, you can manage the password complexity for your host or organization. |
By default, when users sign up for Automation Cloud and create their account, the password they set must meet specific requirements, which cannot be modified. You can choose to change your Authentication Settings to use the Azure Active Directory integration, which allows you to configure password requirements. |
