- Introduction
- Product lifecycle
- Use of customer data in UiPath
- Use of customer data with Agents
- 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 ScreenPlay
- Use of customer data with Studio and StudioX
- Use of customer data with Studio Web
- Use of customer data with Test Manager
- Licensing
- Commercial licensing plans
- Platform licensing
- User licensing
- Service licensing
- Licensing transition
- Delivery options
- UiPath Platform
- UiPath documentation
- Troubleshooting

Overview
UiPath offers two licensing plans: Unified Pricing Plan and Flex Plan. Each of these plans consists of distinct platform, robot, and user licenses, and consumption units. The following sections provide you with a high-level description of the licensing models.
Unified Pricing displays the following characteristics:
-
Currently serves customers who use Automation Cloud and desktop products.
-
Simplifies multiple consumables from the Flex Plan into a streamlined, unified Platform Unit consumable.
-
Promotes flexibility as it enables the reallocation of Platform Units if your initial plans change. Since multiple UiPath services consume Platform Units, you are not constrained to pre-defined uses for the acquired units.
-
-
License consumption occurs at a more granular level, allowing for more detailed tracking and utilization control.
For details on Unified Pricing, refer to Unified Pricing: Licensing plan framework.
For details on how to switch from Flex to Unified Pricing, refer to Switching from Flex to Unified Pricing.
Flex displays the following characteristics:
-
Uses several consumables, including AI Units, Apps Units, Robot Units, API Calls, and Agent Units.
-
Each consumable under the Flex model serves a specific role, and these roles are independent of each other.
For details on Flex, refer to Flex: Licensing plan framework.
You can switch from the Flex licensing plan to Unified Pricing either when reaching your license renewal period or at any point before that. When ready, contact your sales representative for detailed instructions.
Note that switching from Flex to Unified Pricing involves the following steps:
-
Upgrade Studio to version 2025.10 or later to ensure full compatibility with Unified Pricing Licenses.Note: If Studio is running on a version earlier than 2025.10, the Plus license only grants access to StudioX. Users cannot access Studio until the upgrade is complete.
Reassigning user licenses in Unified Pricing
Flex and Unified Pricing include distinct user licenses. For this reason, when moving from Flex to Unified Pricing, as an admin, you must take the steps described in License migration.
Reallocating consumption units in Unified Pricing
Flex and Unified Pricing include distinct consumption units. While multiple consumption units are available in Flex, Unified Pricing relies on one single consumption unit, the Platform Unit.
When switching from Flex to Unified Pricing, if your organization had consumption units allocated to tenants, you must replace the following consumption units with Platform Units:
-
Agent Units
-
AI Units
-
Robot Units
For details, refer to Service consumption units.
Flex to Unified Pricing user license mapping
The following table maps the user license in Flex to the user license in Unified Pricing model after migration.
The Ratio column indicates how many Flex user licenses are converted into Unified Pricing user licenses during migration:
- 1:1 - One Flex user license maps directly to one Unified Pricing user license.
- 1:1 but observing the new packaging - In Test Cloud, a Tester – Named User maps 1:1 to an App Test User, but App Test user licenses are sold in 5-packs. As a result, migrating one Tester – Named User requires purchasing four extra App Test User licenses.
| Flex user license | Unified Pricing user license equivalent | Ratio |
|---|---|---|
| Automation Express 1 | Express User | 1:1 |
| Autopilot Express | Express User | 1:1 |
| Cloud Basic User | Basic User | 1:1 |
| Action Center - Named User | Basic User | 1:1 |
| Attended - Named User | Plus User | 1:1 |
| Citizen Developer - Named User | Plus User | 1:1 |
| Automation Developer - Named User | Pro User | 1:1 |
| Tester - Named User | Plus User | 1:1 |
| Process Mining Business User | Plus User | 1:1 |
| Tester - Named User 2 | App Test User Pack (multiple of 5) | 1:1, but with observing the new packaging |
| Automation Developer - Named User 3 | App Test Developer | 1:1 |
2 When migrating from Test Suite to Test Cloud, one Tester - Named User user license maps to one App Test User license. However, the App Test User licenses are bundled in packs of five, so migrating single Tester - Named User license requires purchasing four additional App Test User licenses.
3 When migrating from Test Suite to Test Cloud, one Automation Developer - Named User license maps to one App Test Developer user license. Test Cloud is included in the Application Testing licensing plans.