- Introduction
- Product lifecycle
- Use of customer data in UiPath
- Use of customer data with AI Center
- Use of customer data with AI Computer Vision
- Use of customer data with Apps
- Use of customer data with Assistant
- Use of customer data with Automation Ops
- Use of customer data with Automation Hub
- Use of customer data with Autopilot for Everyone
- Use of customer data with cloud robots
- Use of customer data with Context Grounding
- Use of customer data with Data Service
- Use of customer data with Document Understanding™
- Use of customer data with Healing Agent
- Use of customer data with Insights
- Use of customer data with Integration Service
- Use of customer data with IT Automation
- Use of customer data with IXP
- Use of customer data with Orchestrator
- Use of customer data with Process Mining
- Use of customer data with Robot
- Use of customer data with Studio and StudioX
- Use of customer data with Studio Web
- Licensing
- Delivery options
- Product availability
- Product differences
- UiPath Platform
- UiPath documentation
- Troubleshooting
Overview
UiPath® offers you second-to-none flexibility on delivery options, with two ways to get the full, cloud-native platform as well as continued support for installing key individual products yourself.
- Automation Cloud™ is designed and optimized to offer the complete UiPath Platform as a service, so you can focus on automation and leave the infrastructure to us.
- Automation Suite is designed and optimized to deliver a similar full-platform experience, but self-hosted in cloud or on-premises. Accordingly, it contains platform, container, and infrastructure configurations and management as part of the single installation.
- We also offer support and new functionality for standalone product installations.
This table highlights some of the key feature differences between the options.
- Available
- Not applicable
|
Capability |
Standalone |
Automation Suite |
Automation Cloud |
Details |
|---|---|---|---|---|
|
Organization as the highest level of resources isolation |
The organization is the highest level of resource isolation. By resources, we mean accounts, roles, packages, and so on. These are shared, but only within the context of the organization. | |||
|
Support for multiple tenants in an organization |
In standalone installations, we support one tenant per organization. | |||
|
Products available in one place |
In Automation Suite and Automation Cloud, all your services are available from the same portal, and you can switch between services easily using the left rail, without leaving the page. In standalone installations, each product is available at a different address, so users who work in multiple products must access each one in a separate browser window. | |||
|
Co-brand the interface of available products by applying a custom logo |
In Automation Cloud and Automation Suite, you can apply your logo and have it available throughout all products. In standalone installations, you can also apply a custom logo, but it only applies for Orchestrator. | |||
|
User license management |
User license management is not available in standalone installations. | |||
|
Unified administration experience for available products |
In Automation Cloud and Automation Suite you can manage all aspects for your organization centrally from the Admin page. These settings concern all products and apply to all tenants in your organization. In Automation Suite, we have an additional superior level, called the host level, which you can manage from the host portals. These settings apply to all your organizations, and in turn to all tenants in each organization. In standalone installations, we have the Orchestrator host portal where you can configure settings regarding the Orchestrator functionality. Settings here apply to all tenants. | |||
|
Federated host administrators |
The host portal is not available to customers in Automation Cloud because settings here are managed by UiPath. | |||
|
Basic authentication for external apps |
Only secure authentication mechanisms are supported on public networks. For Automation Cloud we recommend delegating UiPath authorization using OAuth. | |||
|
Sharing libraries via the host feed |
In Automation Cloud, libraries cannot be shared across tenants via the host feed. Use a custom feed instead. | |||
|
Custom credential store plugins |
Automation Cloud only allows for secure stores with built-in support. | |||
|
MinIO storage buckets |
Automation Cloud does not support MinIO storage buckets. See storage buckets docs for a list of supported storage providers. | |||
|
Elastic robot orchestration | Elastic robot orchestration lets you use our auto-scaling engine to create, start, and stop machines as you need them for running automations.
You self-host the virtual machines (VMs) in your own Cloud Services Provider (CSP), and set up how you want auto-scaling to work for you. | |||
|
UiPath Automation CloudTM Robots - VM |
Called Cloud Robots - VM for short. this feature lets you use the auto-scaling engine, but, as opposed to elastic robot orchestration, we host everything for you. This is an Enterprise-only feature. | |||
|
UiPath Automation CloudTM Robots - Serverless UiPath Automation Suite Robots |
Automation Cloud Robots - Serverless are meant for those who don't want any hassle at all with setting up and maintaining infrastructure to get more robotic power. These cloud robots are also hosted by UiPath, but they run on Linux machines and machine customization is a bit less flexible compared to Cloud Robots - VM. Automation Suite Robots are the Automation Suite counterpart of Automation Cloud Robots - Serverless |
In the table below you can find a side-by-side comparison of our current AI Computer Vision deployment options.
| Automation Cloud | Automation Cloud public sector | Strandalone On-premises | Automation Suite | Local server | Comments | |
|---|---|---|---|---|---|---|
| Model regression testing | Every new model still detects all the design-time data its previous iteration was detecting so that running automation do not break. | |||||
| Mock design-time data storage | The model learns shapes and colors of UI elements, so using mock data with no sensitive information is recommended. | |||||
| Runtime data storage | Runtime production data (which could contain sensitive information) is never used or stored 0 it is only used as input for the AI model. | |||||
| Hassle and cost free server | N/A | |||||
| Speed | High (GPU) | High (GPU) | High (GPU) | High (GPU) | Slightly lower (CPU) | The local server is a compressed version of the cloud model (less neurons) which might fit well light scenarios with more generic looking UI elements. |
| Vision accuracy | Very high | Very high | High | High | Slightly lower | The local server is a compressed version of the cloud model (less neurons) which might fit well light scenarios with more generic looking UI elements. |
| Free with an Enterprise license | N/A | |||||
| Usage |
| 240 MP/min | unlimited | unlimited | unlimited | The UiPath cloud server usage limit is designed to allow for very large headroom. It is very difficult to reach this limit even in the most intense usage scenarios. |
UiPath offers two primary types of robots to cater to your resources, deployment and management needs: self-hosted and UiPath-managed robots.
Self-hosted robots
Self-hosted, or standalone, robots are deployed and managed on your own infrastructure, also known as on-premises. This approach gives you full control over the hosting environment and security. You are responsible for maintaining the infrastructure, manually scaling resources, and handling updates yourself.
The installaion procedure for self-hosted robots depends on the machine operating system:
-
For Windows: using the MSI installer, either
UiPathStudio.msiandUiPathRobot.msi. -
For macOS: using the DMG installer.
-
For Linux: using the Docker image deployment.
Standalone robots can perform attended, unattended, and test automations, and are managed through any Orchestrator delivery.
For systems operating on Windows Server, you can also configure a High-Density Robots environment, which allows concurrent robot executions on the same machine, but under different user accounts.
They can run either Windows, Windows-Legacy, or cross-platform projects, depending on the operating system. Refer to Comparison table for details.
License consumption for attended automations is based on allocated user licenses, which include Attended, Citizen Developer, and Automation Developer licenses.
For unattended automations, license consumption is based on allocated robot licenses or runtimes, which include Production (Unattended), Testing, and Application Testing licenses.
UiPath-managed robots include Standalone and Automation Suite Robots.
Automation Suite Robots
Automation Suite Robots are container-based robots, packed within Automation Suite and managed via Orchestrator. They execute unattended automations in your Automation suite environment using Docker images, similar to Linux robots.
These robots are optimized for cross-platform and web-based projects. They can automatically scale to handle up to 50 parallel jobs.
You can run Automation Suite robots on-demand, and also address spikes in your activity as consumption is based on a per-minute execution.
To manage Automation Suite Robots, use Orchestrator in Automation Suite.
UiPath-managed robots
UiPath-managed robots are deployed and managed by UiPath in a cloud environment. This approach relieves you from the need to manage an infrastructure. Additionally, the required hardware resources are automatically provisioned, and UiPath handles updates and security maintenance for Windows and UiPath software.
For unattended automations that handle sensitive data, you should evaluate UiPath compliance and data residency requirements when considering UiPath-managed robots.
The licensing model for these robots follows a consumption-based approach, metered by Robot units.
UiPath-managed robots include Automation Cloud™ Robots - VMs and Automation Cloud™ Robots - Serverless.
Automation Cloud™ Robots - VM
Automation Cloud™ Robots - VMs are UiPath SaaS offering that uses Windows-based virtual machines hosted in Automation Cloud™ to execute unattended automations. You can deploy either standard or customized Windows images, which can be configured to meet specific automation requirements, such as machine size, VPN integration, or joined domain. Executing automatins requires a constant internet connection.
Automation Cloud™ Robots - VMs support the execution of Windows Desktop applications, provided that proper licensing is in place for any third-party software installed on the VMs. They do not autoscale resource usage, as they offer you the option to select a machine size upon configuration.
In terms of network connectivity, these robots support site-to-site VPN connections to on-premises networks, and enable automated domain join for integration with existing Active Directory environments.
Automation Cloud™ Robots - VMs execute solely Windows and cross-plattform projects.
To manage Automation Cloud™ Robots - VM, use Orchestrator in Automation Cloud™.
Automation Cloud™ Robots - Serverless
Automation Cloud™ Robots - Serverless provide limitless executions of unattended automations in a fully cloud-native environment, where you do not need to manage or configure any underlying infrastructure. They use Docker images for execution, similar to Linux robots.
These robots are optimized for cross-platform and web-based projects. They can autoscale to handle up to 50 parallel jobs.
You can run Serverless robots on-demand, and also address spikes in your activity as consumption is based on a per-minute execution.
To manage Automation Cloud™ Robots - Serverless, use Orchestrator in Automation Cloud™.
Elastic robot orchestration
Elastic robot orchestration offers a way to delegate UiPath for scaling the resources used by your robots to execute unattended automations, by:
-
configuring a maximum number of virtual machines to run in the preferred cloud environment (GCP, Azure, AWS),
-
choosing to optimize for speed, for cost, or choosing a balanced model,
-
scheduling different settings for certain periods when, by exception, you need more or less speed.
Comparison table
The following table summarizes the main differences between the available UiPath robot offerings:
|
UiPath Robot offering |
Infrastructure (hardware) management |
Types of projects run |
Types of automations | Support for auto-scaling |
Licensing model |
Orchestator delivery option |
Plan availability |
|---|---|---|---|---|---|---|---|
|
Standalone: Windows robots (.MSI installer) |
Self-hosted |
|
|
Per number of allocated user licenses (for attended automations) or runtimes (for unattended automations) |
|
| |
|
Standalone: High-Density robots (.MSI installer) |
Self-hosted |
|
|
Per number of allocated runtimes |
|
| |
|
Standalone: Linux robots |
Self-hosted |
|
|
Per number of allocated user licenses (for attended automations) or runtimes (for unattended automations) |
|
| |
|
Standalone: MacOS robots (.DMG installer) |
Self-hosted |
|
|
Per number of allocated user licenses (for attended automations) or runtimes (for unattended automations) |
|
| |
|
Automation Cloud™ robots - VM |
UiPath-managed |
|
|
Platform units, consumption per active VM |
|
| |
|
Automation Suite Robots |
Self-hosted |
|
|
Robot units, consumption per execution minute. |
|
| |
|
Automation Cloud™ Robots - Serverless | UiPath-managed |
|
|
Platform units, consumption per execution minute. |
|
|
