- Introduction
- Getting started
- Building with Maestro BPMN
- Understanding Maestro BPMN modeling
- Opening the modeling canvas
- Modeling your process
- Aligning and connecting BPMN elements
- Autopilot for Maestro (Preview)
- Process Repository
- Implementing a simple BPMN process
- Implementing a complex BPMN process
- Debugging
- Simulating
- Evaluations (Preview)
- Common implementation scenarios
- Building with Maestro Case
- Introduction to Maestro Case
- Maestro BPMN vs. Maestro Case: when to use case management
- The Maestro Case lifecycle: from event trigger to app experience
- Build your first case with Maestro Case
- Build a Maestro Case with a coding agent (preview)
- Defining case keys (system vs. external)
- Establishing task I/O and write-back contracts
- Exit rules and early stage termination
- Modeling primary and secondary stages
- Triggering a case from Data Fabric
- Implementing stage-level personas and permissions
- Setting SLAs and automated escalation rules
- Configuring a rework loop (re-entry)
- Configuring and testing the Case Manager Agent (preview)
- Case Manager input and output contract
- Maestro Case component dictionary
- Building with Maestro Flow
- Maestro Automate
- Integrations
- Operating
- Monitoring
- Optimizing
- Reference information
Maestro licensing under the Unified Pricing model, covering Platform Units consumption, platform tier requirements, and user license types.
This page describes Maestro licensing under the Unified Pricing model.
Platform tiers (Unified Pricing)
Maestro is not available on the Basic platform tier.
| Feature | Standard | Enterprise |
|---|---|---|
| Process modeling | ✅ | ✅ |
| Process implementation | ✅ | ✅ |
| Process operations | ✅ | ✅ |
| Process monitoring | ✅ | ✅ |
| Process optimization | ❌ | ✅ |
| Process simulations | ❌ | ✅ |
User rights (Unified Pricing)
| Feature | Unlicensed | Express | Basic | Plus | Pro |
|---|---|---|---|---|---|
| Process modeling | ✅ | ✅ | ✅ | ✅ | ✅ |
| Process implementation | ❌ | ❌ | ✅* | ✅ | ✅ |
| Process operations | ❌ | ❌ | ✅ | ✅ | ✅ |
| Process monitoring | ❌ | ❌ | ✅ | ✅ | ✅ |
| Process optimization | ❌ | ❌ | ✅** | ✅ | ✅ |
| Process simulations | ❌ | ❌ | ✅ | ✅ | ✅ |
* Personal use only ** Read-only
Unlicensed and Express user access
With Maestro Flow generally available, Unlicensed and Express users have the following access, in addition to the rights in the table:
- Deploying processes to shared folders and the tenant, not only to a personal workspace
- Access to UiPath Intelligent eXtraction Platform (IXP), Document Understanding, and Communications Mining projects
- Publishing more than one process in a personal workspace, previously limited to one
- Access to Action Center, to build and test human-in-the-loop workflows
Consumption logic (Unified Pricing)
Maestro consumes Platform Units based on usage.
| Activity | Metering unit | Platform Units consumed |
|---|---|---|
| Maestro Orchestrate (Case, Flow, BPMN): instance orchestrated | Process instance | 1 |
| Maestro Orchestrate: Business rule executed | Business rule executed | 0.2 |
| Maestro Automate: workflow executed | Process instance | 0.05 |
Maestro Orchestrate covers Maestro Case, Maestro Flow, and Maestro Business Process Model and Notation (BPMN) processes, which all consume at the Maestro Orchestrate rate, with no included allowance. Maestro Automate is a separate product for short-running workflows, with its own rate and an included monthly allowance of runs. For what each product includes, refer to Choosing between Maestro Orchestrate and Maestro Automate.
Maestro Automate runs that fall within the monthly allowance do not consume Platform Units for process execution. Runs beyond the allowance consume Platform Units at the reduced rate in the table. In both cases, the underlying platform consumption a run generates, such as agent executions or document processing, is metered according to the orchestrated component's licensing.
| Platform tier | Included Maestro Automate executions |
|---|---|
| Standard | 10,000 per month |
| Enterprise | 50,000 per month |
A debug run does not consume Platform Units for process execution. Any services the debug run calls, such as AI agents or document processing, consume their own units as usual.
For general licensing information, refer to the Automation Cloud admin guide.