- 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 Communications Mining
- Use of customer data with Data Service
- Use of customer data with Document Understanding™
- 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 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
- UiPath Platform
- UiPath documentation
- Troubleshooting
Overview
Service licensing
These licenses can be distributed to your organizations and tenants. They provide specific functionality to support or manage business processes. Service licenses target a specific metric, such as service instances, service capacity, or service consumption units.
Some types of licenses control the allowed robot and 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.
Runtimes are licenses related to robot use - in this case, robot refers to the entity that executes an automation.
They are used for executing unattended processes and are meant to be assigned to machine objects - either a standard machine or a machine template.
-
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.
-
Foreground processes: 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.
-
Background processes: 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.
Runtimes are allocated to tenants and constitute the tenant's pool of runtimes. When a host machine connects to UiPath® Orchestrator, the number of runtimes assigned to its associated machine object is consumed from the tenant pool. When the host machine disconnects, the runtimes return to the tenant pool.
While 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.
Types of runtimes
There are several types of runtimes that are required to run certain types of processes or to use automations that pertain to a certain UiPath product.
Unattended or NonProduction runtimes
Unattended runtimes can be used in production to run unattended processes, while NonProduction runtimes are reserved for dry-running unattended process to make sure they run as expected before deploying them to production.
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 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.
Testing runtimes
The Testing license works similarly 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.
For the full list of available runtimes, see the UiPath Licensing page. On the Licensing page, the term Robot is used when referring to runtimes.
Unattended runtimes
-
Execute unattended processes in production environments.
-
Count the maximum number of Unattended runtimes that can run processes simultaneously.
-
Determine the number of Unattended licenses consumed based on the runtimes assigned to a machine.
-
Define the number of robots on a machine independently from the number of runtimes.
-
List machines with Unattended runtimes on the Unattended page, including:
-
Display the number of allocated runtimes
-
Show the number of defined and running robots
-
Indicate the machine license status
-
-
Calculate the total number of Unattended licenses consumed based on the runtimes allocated across all online machines.
Testing runtimes
-
Dry-run unattended processes to ensure they function correctly before deployment to production.
-
Count the maximum number of Testing robots that can run tests simultaneously.
-
Determine the number of Testing licenses consumed based on the runtimes assigned to a machine.
-
Define the number of robots on a machine independently from the number of runtimes.
-
List machines with Testing robots on the Testing page, including:
-
Display the number of allocated runtimes
-
Show the number of defined and running robots
-
Indicate the machine license status
-
-
Calculate the total number of Testing licenses consumed based on the runtimes allocated across all online machines.
App Testing runtimes
-
Enable the use of App Testing robots only in Test Cloud.
-
Operate similarly to Unattended runtimes.
-
Allow you to run Test automation projects and Processes in non-production environments only.
-
Count the maximum number of App Testing robots that can run tests simultaneously.
-
Determine the total number of App Testing licenses you can consume based on the number of runtimes allocated across all online machines.
For more information on App Testing runtimes and App Testing robots, visit Test Cloud licensing.
- 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.
This type of license controls the throughput limit. Throughput means the amount of data (in megapixels) that can be processed every minute by our AI Computer Vision servers based on your license entitlement.
One account can use a single AI Computer Vision license.
Access to the AI Computer Vision servers is granted based on an API Key. The API key can be generated (or re-generated, if needed) from:
- Automation Cloud and Automation Suite: the Admin > Licenses page, on the Robots & Services tab.
- Orchestrator standalone: the Licenses page of the host Management portal.
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 is any 3 tenants you want.
The licensing plan and user licenses you choose control what UiPath functionality you can use. Consumption units measure how you consume your licenses. As the service is being used, units are consumed, and when you run out of units, you can no longer use the service.
For example, for Document Understanding, the license specifies the maximum number of pages you can process using the service. As you process pages, the units are used up and your unit count goes down. When you have no more units, you can no longer process pages and you must purchase additional units to use the service further.
This section covers the consumption units specific to both UiPath commercial licensing plans: Unified Pricing and Flex.
Platform Units are credit-based consumption units specific to the Unified Pricing commercial plan that measure the licensing usage for a specific set of UiPath services. As you perform specific operations within these services, you consume Platform Units. When you run out of Platform Units, you can no longer perform those operations.
Platform Units power your usage of UiPath services, but their effective use depends on your choice of licensing plan and user licenses. The selected licensing options determine how you can use your units.
The following table provides an overview of the products that consume Platform Units, the used metric, and the standard consumption rate. For precise details on how each service uses Platform Units, refer to the product-specific documentation.
|
Product |
Metric |
Standard consumption rate in Platform Units |
|---|---|---|
|
Per action |
0.20 | |
|
Per LLM call |
0.20 | |
|
(External Apps - anonymous users) |
Per 500 users per month |
100 |
|
(Small machine) |
Per runtime minute |
0.20 |
|
(small machine) |
Per month (reservation) |
1,000.00 |
|
(predictions) |
Per prediction |
0.20 |
|
(Standard machine) |
Per compute hour |
0.20 |
| Context Grounding |
Per request |
0.20 |
| Communications Mining |
Per message uploaded, modified, or predicted |
0.20 |
|
Per page |
0.20 | |
|
(GenAI and Semantic) |
Per request |
0.20 |
| Healing Agent |
Per heal |
3.00 |
| Integration Activities |
Per 100 executed activities |
2.00 |
| IXP |
Per page |
0.20 |
|
Per process instance execution |
1.00 | |
| Process Mining |
125 row |
1.00 |
Test Execution units measure the executions of jobs performed using the App Testing robot in the Unified Pricing commercial licensing plan. Each job performed by the App Testing robot consumes one test execution unit. No units are consumed if a test execution is not marked as Finished. For test executions, Finished can also mean either Failed or Passed.
Test Execution units are available only with the Application Testing Enterprise platform plan. For more information on Test Execution units and App Testing robots, visit Test Cloud licensing.
Agent units measure the usage of agent-specific activities in the Flex commercial licensing model.
For detailed information on metering and charging logic, or tracking, refer to the Agents user guide.
AI units is the measure used to license AI products in the the Flex commercial licensing plan. AI units are charged based on consumption when the models are bringing value to you.
For detailed information on metering and charging logic, or tracking, see:
- AI Center AI units
- Document Understanding metering and charging logic
- Task Mining running the ML Pipeline
- Process Mining licensing
- GenAI Activities consumption
- Semantic activities consumption
Autopilot actions measure the usage of Autopilot-specific activities in the Flex commercial licensing plan. One such action is counted from the time you click a button or write a prompt up until the time you receive a result from that click or prompt.
Autopilot actions are included by default in existing SKUs and plans. For details on the number of available actions, check out Plan breakdown.
For a Document Understanding license, the license unit 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 and 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 UiPath Studio.
Starting May 1, 2025, Integration Service API calls are free for a two-month promotional period. We are using this time to refine our licensing model as we continue to enhance our API Automation offering.
Integration Service API calls measure the usage of Integration Service activities. One API call is consumed when a call is made to a third party application, regardless of how the call is initiated, i.e. manually, through an attended process, or through an unattended automation.
Integration Service API calls are available as follows:
-
As a dedicated bundle, purchased as a platform individual SKU. These can be used until the available quantity runs out.
-
Bundled with a license, as part of a combined SKU. These are renewed monthly, along with the license they pertain to.
See the dedicated Integration Service documentation for details on consumption.
The UiPath licensing platform lists all SKUs relevant to Integration Service API calls.
RUs are required to run unattended automations using robots that are hosted by UiPath, namely:
- UiPath Automation CloudTM Robots - VM (Cloud Robots - VM) - Documentation
- UiPath Automation CloudTM Robots - Serverless (Cloud Robots - Serverless) - Documentation
- UiPath Automation Suite Robots - Serverless
VM and serverless robots do not require unattended runtimes. They are licensed for unattended use through robot units.
Robot units allow you to use one or both types of cloud robots, but they consume robot units differently:
SAP Transport units are used for licensing the SAP Change Impact Analysis feature within Test Manager. SAP Transport units are available with both the Flex and Unified Pricing commercial licensing plans. They can be purchased in bundles of 100 units, and are only available on the Enterprise licensing plan.
One SAP Transport unit is consumed for each unique SAP transport that you choose to analyze on your SAP Instance. No units are consumed if you want to repeat the analysis on transports that have already been analyzed.
- Robot and service licenses
- Runtimes (robot licenses)
- Data Service units
- AI Computer Vision licenses
- Service instances
- Automation Hub licenses
- Service consumption units
- Platform Units
- Test Execution units
- Agent units
- AI units
- Autopilot actions
- Document Understanding™ licenses
- Integration Service API calls
- Robot units
- SAP Transport Units
