Contents
At a glance
- Unit
- Robot Unit (RU) - metered on runtime, not on steps
- Serverless production
- Small 1, Standard 2, Medium 4, Large 10 RU per minute
- Serverless testing
- Small 0.5, Standard 1, Medium 2, Large 5 RU per minute
- Testing vs production
- Exactly half the production rate at every size
- VM Standard machine
- 6,000 RU/month production, 3,000 RU/month testing
- Cost profiles
- +500 RU/month on Fast, +1,000 RU/month on Always
- Serverless/VM breakeven
- 6,000 RU is 3,000 minutes on a Standard production robot - about 50 hours a month
- Price per RU
- Not published by UiPath (checked September 2026)
What a Robot Unit meters
A Robot Unit (RU) is what UiPath draws down when an automation runs. The critical property is that it is a time meter, not an action meter. Nothing about how many activities your workflow contains, how many records it touches, or how many applications it drives enters the calculation. What enters is how long the robot was running and how large a machine it ran on.
This puts UiPath in the same family as the Latenode CPU second and a long way from the Zapier task. On a per-action platform, adding a step costs money. Here, adding a step costs nothing unless it costs time - and a step that waits on a slow application costs a great deal.
The serverless rates
For serverless robots, UiPath documents consumption per minute by machine size, verified against UiPath's Orchestrator documentation in September 2026.
Production: Small 1 RU per minute, Standard 2 RU per minute, Medium 4 RU per minute, Large 10 RU per minute.
Testing: Small 0.5 RU per minute, Standard 1 RU per minute, Medium 2 RU per minute, Large 5 RU per minute.
Two things fall out of that table immediately. Testing runs at exactly half the production rate at every size, which makes a test-first workflow genuinely cheap to iterate on. And the size ladder is not linear - Large costs ten times Small, not four. Stepping up one size class is a bigger decision than the label suggests, and a job that runs on Medium out of caution when Standard would do is paying double indefinitely.
The optimisation that follows is unusual for an automation platform: make it finish faster. Every second of wall-clock time bills. A workflow that waits on a UI element with a generous timeout, polls a slow API, or sleeps between retries is burning RU while accomplishing nothing. Replace polling with events where you can - see polling vs webhook - and treat a slow upstream system as a line item rather than an annoyance.
VM-based machines: a block, not a meter
For VM-based machines the model changes shape entirely. A VM Standard machine consumes 6,000 RU per month for production and 3,000 RU per month for testing, as a monthly allocation rather than per minute of use.
Cost profiles add to that block: +500 RU per month on the Fast profile and +1,000 RU per month on the Always profile, for both testing and production.
The consequence is a straightforward breakeven you should actually compute. A serverless Standard production robot burns 2 RU a minute, so 6,000 RU buys 3,000 minutes - fifty hours a month, or roughly two hours a working day. Above that, the VM block is the cheaper structure; well below it, serverless is. Sustained, predictable, high-utilisation work belongs on VM machines; bursty, occasional work belongs on serverless. Getting this wrong is the most common source of RU surprise, and unlike most billing questions it is resolvable with arithmetic you can do today from your own run logs.
No dollar price is published
UiPath's Orchestrator documentation defines RU consumption in exhaustive detail and states no dollar price anywhere. There is no public rate per Robot Unit, and RU entitlements are sold as part of platform agreements rather than as a self-serve line item.
This is the recurring pattern across enterprise automation meters, and it is worth naming rather than working around: the vendor tells you precisely what you will consume so you can size a deal, and tells you nothing about what it costs so the deal stays negotiable. Compare Power Automate licensing, where Microsoft does publish figures, or the Workato recipe, where the packaging unit is public but the price is not.
What that means practically is that the RU number is the transferable artefact, not the dollar number. You can compute your RU demand exactly, from documented rates, without talking to anyone - and that computed figure is what you negotiate against.
Building your RU model
Pull the average runtime per job from your existing logs or a pilot. Multiply by the per-minute rate for the machine size you actually need, not the one you defaulted to. Multiply by runs per month. Do it separately for production and testing, because the testing rate is half. Sum, then compare against the 6,000 and 3,000 RU VM blocks to see which structure fits.
Then ask your rep the questions the docs cannot answer: what is the effective cost per RU at our committed volume, does the entitlement reset monthly, does anything roll over, what does overage cost, and how are Robot Units and Agent Units reconciled if we run both - because agentic automations are metered on an entirely separate scale, and a deal that covers one does not automatically cover the other. See total cost of ownership for the development, maintenance and infrastructure costs the RU meter never sees.
UiPath Robot Unit FAQ
What is a Robot Unit in UiPath?
The consumption unit UiPath meters automation runtime in. Serverless robots consume RU per minute of execution at a rate set by machine size, and VM-based machines consume a fixed monthly block instead. Step count and data volume do not affect the figure - only time and machine size do.
How many Robot Units does a UiPath job consume?
Runtime in minutes multiplied by the machine rate. For serverless production that is 1 RU/min on Small, 2 on Standard, 4 on Medium and 10 on Large. Testing runs at half those rates: 0.5, 1, 2 and 5 respectively.
How many Robot Units does a VM machine use?
A VM Standard machine consumes 6,000 RU a month for production and 3,000 a month for testing, as an allocation rather than per minute. The Fast cost profile adds 500 RU a month and the Always profile adds 1,000, for both testing and production.
Should I use serverless or VM robots?
Compute the breakeven. On a Standard production robot at 2 RU a minute, the 6,000 RU VM block equals 3,000 minutes - roughly 50 hours a month. Sustained high-utilisation work is cheaper on the VM block; bursty or occasional work is cheaper serverless.
How much does a UiPath Robot Unit cost in dollars?
UiPath does not publish a price per Robot Unit. RU entitlements are sold within platform agreements. The documented consumption rates let you compute your exact RU demand without talking to anyone, which is the number to negotiate against.
How do I reduce Robot Unit consumption?
Make jobs finish faster and run them on the smallest machine that works. Because RU bills wall-clock time, waits, generous UI timeouts, polling loops and sleeps between retries all cost money while doing nothing. Also check that jobs are not running on Medium or Large out of caution - the size ladder is not linear, and Large costs ten times Small.
Primary source
UiPath Orchestrator - consuming Robot Units
Checked September 2026. Anything priced or rate-limited moves, so verify against the source before you budget.
Want this built rather than explained?
Knowing what uipath robot unit means is one thing; having it running in your business is another. We scope one workflow at a time, quote a fixed price in writing after a free consult, build it, and hand it over with documentation you own.
