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.

Service capacity

---

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.

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

This type of 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.

One account can use a single Computer Vision license.

Access to the 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.

Runtimes (robot licenses)

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.

The number of runtimes assigned to a machine object represents the execution capacity for running automations on each host machine that is attached to that machine object concurrently.
For example, with one runtime, only one automation can be executed at a time. With 5 runtimes, up to 5 automations can be executed at the same time on the same host machine.

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.

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.
For example, here are the types that are available for UiPath Orchestrator:

• An Unattended runtime can be used in production to run unattended processes
• A NonProduction runtime is reserved for dry-running unattended process to make sure they run as expected before deploying them to production.
• A Testing runtime allows you to use robots to run test sets and test cases.

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.

Runtimes naming history

The names of our user licenses have changed over time. To better identify our robot licenses, check the naming progress below:

 

Service instances

---

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.

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.

 

Service consumption units

---

The license controls the allowed service-specific units that are available. 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.

Document Understanding licenses

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.

AI units

AI units is the measure used to license AI products. 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

Robot units

Robot units (RUs) are specific to UiPath Orchestrator in Automation Cloud.

RUs are required to run unattended automations using cloud robots that are hosted by UiPath, namely:

• UiPath Automation Cloud^TM Robots - VM (Cloud Robots - VM) - Documentation
• UiPath Automation Cloud^TM Robots - Serverless (Cloud Robots - Serverless) - Documentation

VM and serverless cloud robots do not require unattended runtimes. They are licensed for unattended use through robot units.

Consumption

Robot units allow you to use one or both types of cloud robots, but they consume robot units differently:

¹ You must be on the Enterprise, Pro, or Pro Trial licensing plan to use this feature.

 

Robot unit reserve

For Cloud Robot - VM machines, once a machine is created and the RUs are consumed, we also make note of the required RU quantity and internally reserve it for the following month.
What this means is that when a month starts, the required RUs for your existing Cloud Robot - VM machines are automatically deducted from the tenant's monthly RU pool to make sure they can run for the month.
For this reason, you could find that the robot unit amount for a tenant can be lower than you would expect at the start of the month.

Example: Let's consider a tenant with 30,000 RUs allocated. If, on the 31st of May, the tenant has 3 Cloud Robot - VM standard machines, then on the 1st of June when the next month's RUs are allocated, the amount of 18,000 RUs (3 x 6,000) is automatically deducted from the tenant's RU balance. Therefore, this tenant has only 12,000 available RUs at the beginning of the month.

Deleted machines: If, during the month, you delete a Cloud Robot- VM machine, the RUs that were consumed to create the machine are not refunded. You can, however, for the duration of the month, create another Cloud Robot - VM machine without using additional RUs. Once consumed, RUs allow you the use of one Cloud Robot - VM machine for the entire month - they are not tied to a particular machine.
If you want to reduce your monthly RU budget for Cloud Robot - VM, you can delete a Cloud Robot - VM machine before the month ends. This way, RUs are no longer reserved for the machine and are not consumed from next month's RUs.

 

Example for calculating RU requirements

Let's consider an organization with 3 tenants that opt for production runtimes.