UiPath's commercial offering provides multiple SKUs that allow for flexibility when choosing how to deploy and use UiPath software. See the UiPath Licensing Portal for more information about our available SKUs.
You can acquire one license to distribute centrally form the host level, license each organization separately, and for certain products you can also acquire standalone licenses.
License management is performed in either the Licenses page of the host portal (by a system administrator) or in the Admin > Licenses page of Automation Suite (by an organization administrator).
This enables you to license multiple organizations using a single license. It aggregates multiple licenses, making it ideal for being distributed across your organizations.
Only a system administrator can manage this type of license. System administrators can activate the license from the Licenses page while license allocation is done from the Organizations page of the host portal.
In this scenario, you have a license file for one organization.
This type of license is activated at organization level, by an organization administrator, from the Admin > Licenses page in Automation Suite. The organization administrator can then distribute licenses to each tenant within their organization.
You can choose to license only some of your organizations from the host-level and have other organizations license themselves at the organization level.
You cannot track this type of licensing centrally from Automation Suite.
Why use standalone licensing
- You did not have Automation Suite to allow centralized license management when you acquired the products that you licensed separately and want to continue to use standalone licensing.
- You have RPA developers who work with multiple Orchestrator instances that are licensed by different entities. Standalone licensing allows them to license the product locally and then use the Stand-alone license option in the product to prevent them from consuming licenses from your license pool.
Ties the usage of UiPath software to an individual user. It enables them to register any number of robots on any machine, as long as the same username is present on all of them. You must obtain a separate license for each uniquely identified user accessing the product or service. For example, an Automation Developer - Named User license provides a unique user with full operational rights to Studio, StudioX, Attended Robot, Data Service, Action Center, and Task Capture. These operational rights are further controlled using roles and permissions.
This type of license is available for Attended and Studio/StudioX Robots.
Allows more than one individual to use UiPath software and allows for multiple users to benefit from one license successively. This type of license is ideal for users who work in shifts, as licenses are consumed only when they actually use a robot. Each Multiuser license adds up to 3 distinct authenticated users to the maximum number of users that can be granted access. You must obtain a number of Multiuser licenses equal to the number of authenticated users accessing the product or service simultaneously.
This type of license is available for Attended and Studio/StudioX Robots.
This type of license can be displayed as Concurrent User in UiPath products that are at version 2020.10 or older.
A multiuser license is consumed, depending on its type, when:
- the robot is connected to Orchestrator
- the UiPath Assistant is running (and not only while it is executing a process)
- Studio/StudioX is running.
As a result, you can have hundreds of robots defined on multiple machines but only use, for example, 50 multiuser licenses at a specific moment in time if that is the maximum number of users who simultaneously connect their robot to Orchestrator.
If a license file contains licenses for all types of robots, the Concurrent ones are prioritized over the Named User ones. For example, if a license file contains both Attended Concurrent and Attended licenses, the Attended Concurrent ones are shown as available.
Robot licenses, or runtimes, refer to the type of robot that can be used and how.
You can view the total number of runtimes available on all online machines on the License page in Orchestrator. Remember that a machine consumes the licenses as soon as the Robot Service is started. To prevent instant license consumption, disable the machine from the corresponding License page. Note that you cannot use Studio or the robot on a disabled machine.
About concurrent execution
Robots have the ability for concurrent execution, meaning that, on the same machine, they can execute multiple processes simultaneously.
For concurrent execution, a machine must have more than one runtime allocated. The number of allocated runtimes determines the number of processes that can run simultaneously on the same machine.
In the case of foreground processes, only one such process can run at the same time. So even though a machine has, for example, 5 runtimes allocated, foreground processes are executed one at a time.
A Windows workstation can run only one background process at a time, and therefore it is recommended to assign only one runtime to it. But you can also have more robots defined on a machine than the number of runtimes allocated to that machine.
A Windows Server machine can have several robots executing processes simultaneously, and therefore you can assign more runtimes to it to allow for concurrent execution.
When online and connected to Orchestrator, a machine consumes a number of licenses equal to the runtime capacity of the machine template used to connect to Orchestrator. The runtime represents the maximum number of robots that can simultaneously run on a specific machine and it is manually customizable.
The number of runtimes assigned to a machine determines the number of Unattended or NonProduction licenses consumed when the UiPath Robot is running on the machine. The number of robots defined on a machine, on the other hand, is not dependent on the number of runtimes.
For example, if you assign only 3 runtimes to a machine with 5 robots, only 3 licenses are consumed. If you execute 5 jobs or schedule all the robots on that machine, the following sequence occurs:
- 3 jobs are executed on the first 3 licensed robots;
- the remaining 2 unlicensed robots are placed in a pending state;
- the first 3 robots release their licenses;
- the remaining 2 robots can now obtain a license and they execute the assigned jobs.
If on a machine you have only one Unattended or NonProduction robot and assign 30 runtimes to the machine, then 30 licenses are consumed when that machine is online.
If you have 10 users (robots) on a machine, you can only execute one process at a time, and you have to leave the number of runtimes to its default value, 1. If you assign more than 1 runtime to a workstation machine and try to execute multiple jobs at the same time, errors are thrown.
When the UiPath Robot Service starts running on a machine, it acquires a license and is displayed as licensed in Orchestrator. If there are no licenses available, the machine is not going to be licensed and cannot execute processes, but it checks for available licenses with each heartbeat.
In this model of licensing, we count the maximum number of Unattended or NonProduction robots that are able to execute processes simultaneously. This number is given by the total number of runtimes allocated to all the online machines. You can distribute these licenses across all your machines.
All the machines that have robots defined as Unattended are listed in the Unattended or NonProduction page, along with the number of allocated runtimes, the number of defined and running Robots, and the machine's license status.
The Testing license works similar to the Unattended license where we count the maximum number of Testing robots that are able to execute tests simultaneously. This number is given by the total number of runtimes allocated to all the online machines. You can distribute these licenses across all your machines.
These licenses can be distributed to your organizations and tenants. They provide specific functionality to support or manage business processes. These licenses target a specific metric, such as service instances, service capacity, or service consumption units.
Product / Service
2 (Service instances)
5 (Service instances)
Some types of license control the allowed service capacity.
For example, the number of execution slots (runtimes) for Orchestrator and AI Center, throughput limit for Computer Vision, or units for Data Service.
Robot Licenses for Orchestrator
- Testing Robot - with one license you can execute one test case, with two licenses you can execute two test cases concurrently.
- Unattended Robot - with one license you can execute one back-office process, with two licenses you can execute two processes concurrently.
- NonProduction Robot - with one license you can execute one back-office process, with two licenses you can execute two processes concurrently in a non-production environment.
Robot Licenses for AI Center
- AI Robot - with an AI Robot license you can execute one ML training job OR serve two ML Skills concurrently.
- AI Robot Pro - with an AI Robot license you can execute one ML training job OR serve two ML Skills concurrently and the runtime can use a GPU (for both serving a model or training a model).
Data Service Units
- 1 Data Service Unit grants 1 GB of data storage, 5 GB of attachment storage, a maximum of 10K API calls per day.
- 1 Data Service Unit is granted for each pair of user/unattended robot licenses purchased.
Computer Vision Licenses
One account can use a single Computer Vision license. Such a license controls the throughput limit. Throughput means the amount of data (in megapixels) that can be processed every minute by our Computer Vision servers based on your license entitlement. Access to the Computer Vision servers is granted based on an API Key. The API key can be generated (or changed if needed) from the organization-level Admin > Licenses page in Automation Suite, on the Robots & Services tab.
For certain products, you can have distinct instances within each tenant. Licenses for these products control the number of allowed service instances. For example, if you have 3 Automation Hub licenses allocated to your organization and 4 tenants, you can enable the Automation Hub service in any 3 tenants you want.
Automation Hub Licenses
An Automation Hub license controls the number of allowed Automation Hub instances. For each newly created Automation Hub service, a unit is subtracted from the total number of allowed services.
The license controls the allowed service consumption units. For example, for Document Understanding, the license specifies the maximum number of pages it can process.
Document Understanding Licenses
For a Document Understanding license, the license metric is the number of pages, allowing you to extract a certain number of document pages on our ML servers. Available Document Understanding licenses allow 40k page units, 1M page units, or 10M page units. Access to the models' endpoints is granted based on an API Key. The API Key is generated automatically when you create your account, and it is required for the Machine Learning Extractor activity in Studio.
By default, you are notified by email at 180, 90, 30, 14, 7, and 1 day before the license expires. You can configure these values using the
SystemJobs.LicenseExpirationAlert.DaysBefore app setting.
At host level, for single licenses distributed across multiple organizations, only the system administrator receives these email alerts. At organization level, all the active users with the License - View permissions receive them. The emails are localized per user.
Following the expiration of your license, we grant a grace period during which you can renew your license without experiencing any disruption of operations. A notification is displayed after logging in, informing you that your license is expired and the duration of the grace period:
You can close the notification and continue working as usual. After the end of the prescribed grace period, your instance becomes unlicensed and is no longer operational.
If, after an upgrade or migration from a version of Orchestrator older than 2019.10, you did not update your licensing information as described in Managing your host license, you do not benefit from the grace period.
Updated 7 months ago