Understanding UiPath licences: what mid-sized businesses really need

Anyone buying UiPath licences for the first time faces a catalogue of Studio variants, attended and unattended robots, Orchestrator, Automation Cloud and, more recently, Platform Units. That is why many companies look for UiPath licensing advice before they sign. Rightly so: buy the wrong things here and you pay for years for building blocks that never run.

Why the UiPath licensing model is confusing

The UiPath licensing model combines three layers that often get muddled in quotes: licences for people (who may build and start automations), licences for robots (what may run automatically) and the platform on which both are managed. On top of that, UiPath has reworked its pricing model. According to the UiPath documentation (as of July 2026), billing increasingly runs through what is called Unified Pricing: a single consumption unit named the Platform Unit replaces the many individual units of the older Flex model, such as AI Units, Robot Units and Agent Units.

The short answer for mid-sized businesses is this: to get started, you need a developer licence (Studio) for the person who builds the workflows, an unattended robot for processes that should run without human involvement, and the Automation Cloud with Orchestrator for control. Everything else, from Process Mining to AI add-on modules, is an expansion stage and does not belong in the first contract.

The building blocks explained simply: build, run, manage

At its core UiPath consists of three types of building block, and every licensing decision comes down to one question: who builds, who runs, who manages?

• Build: UiPath Studio is the development environment. This is where the workflow is created, for example “open the business application, read the invoice, type the values into DATEV”. It is licensed per developer, in current plans usually as an Automation Developer user.
• Run: Attended robots run on an employee's workstation and are started by that person, acting as an assistant in day-to-day work. Unattended robots run on their own on a server or in the cloud, on a schedule or a trigger. Unattended is more expensive but replaces the most manual work.
• Manage: The Orchestrator, today part of the Automation Cloud, distributes tasks to the robots, manages credentials and logs every run. Dispensable for a single attended robot, but practically mandatory for unattended operation.

What a typical SME starter setup includes

A typical starter setup for a mid-sized company comprises exactly three items: one Studio developer licence, one unattended robot and the cloud platform. On costs: according to the UiPath pricing overview (as of July 2026), the Automation Cloud Basic plan starts at 25 US dollars per month, but it is limited to a few users and at most two unattended robots and is intended more for testing. The Standard and Enterprise plans for productive company use are only available with an individual quote. Project experience shows that the unattended robot is the largest single item, and the developer licence the second largest.

For trying it out there is also a free version (the Community or Free plan) with Studio and a few attended robots. It is suitable for learning, testing and a first prototype, but according to UiPath it is aimed at individuals and very small organisations and is not a permanent solution for productive operation.

When UiPath is the right tool: what good UiPath advice checks

UiPath pays off above all when you need to automate systems that have no interface. That is exactly what RPA was built for: the robot operates the user interface like a human. Typical cases are legacy industry software without an API, SAP and DATEV screens, terminal server and Citrix environments or old ERP systems that nobody wants to touch any more.

For processes whose systems have modern interfaces, however, UiPath is often oversized. A data exchange between cloud services can usually be solved faster and far more cheaply with n8n or Power Automate. How the tools differ is shown in our comparison of n8n, Power Automate and Zapier. A serious consultant examines this question before selling licences, not afterwards.

How we at NordFlux approach UiPath projects, from process selection through licensing advice to operation, is set out on our page on UiPath consulting.

How to keep UiPath licensing costs small

The most effective cost brake is a small, cleanly scoped start. Concretely, that means:

• Start with one process, not five. An unattended robot works through several processes one after another when the time windows fit.
• Choose attended over unattended wherever a human triggers the workflow anyway. That is the cheaper robot class.
• Only book add-on modules such as Document Understanding or Process Mining once a specific process needs them.
• Size the Platform Unit allowance to the actual rollout, not to the ambition from the kickoff.
• Have it checked before you buy whether the process needs RPA at all or is cheaper served by an API solution.

Frequently asked questions

Which consultancy offers automation with UiPath?

Automation with UiPath is offered by specialised RPA and digitalisation consultancies, in Germany often organised as UiPath partners. NordFlux offers UiPath consulting for mid-sized businesses in the DACH region, from process analysis through licence selection to implementation. Make sure the consultancy masters several tools and does not automatically solve every task with UiPath.

What do UiPath licences cost for a small business?

Publicly, UiPath (as of July 2026) names only the entry price of 25 US dollars per month for the heavily limited Basic plan of the Automation Cloud. Productive company plans (Standard, Enterprise) are available on request only. The actual cost depends on the number of developers, the type of robot and the add-on modules booked. Have every quote explained to you item by item.

What are Platform Units in UiPath?

Platform Units are the central consumption unit in UiPath's current Unified Pricing model (as of July 2026). Instead of separate allowances for AI features, cloud robots and agents, you buy one shared allowance from which all services draw. The allowance can be reallocated flexibly, but it must be sized realistically.

Do I really need the Orchestrator?

For robots running unattended, practically yes: without the Orchestrator there is no central control, no schedules and no clean logs. In the current cloud plans it is included as part of the Automation Cloud and no longer a separate buying decision. Only those who use exclusively an attended robot at the workstation can do without it.

Is the free UiPath version enough to start with?

For learning, testing and a prototype, yes. For productive, permanent operation in the company it is not intended, either in licensing terms or functionally: it lacks, among other things, support, governance features and full unattended operation. As a risk-free first step before the buying decision, it is nevertheless worthwhile.