Every RPA vendor splits its robots into two categories: attended bots that work alongside a human, and unattended bots that run entirely on their own. The distinction isn’t just technical — it drives licensing cost, infrastructure needs, and which processes you can realistically automate first. This explainer breaks down what each type actually does, what vendors charge for them according to their own pricing pages, and how to decide which one a given process needs.
At a Glance
| Attended Bots | Unattended Bots | |
|---|---|---|
| Trigger | Started by a human, on demand | Runs on a schedule, event, or queue, with no human present |
| Typical licensing unit | Per user | Per bot / per robot |
| Example price (2026) | Microsoft Power Automate Premium: $15/user/month | Microsoft Power Automate Process: $150/bot/month; Hosted Process: $215/bot/month |
| Infrastructure | Runs on the employee’s own workstation | Needs a dedicated machine or virtual machine per concurrent run |
| Best for | Variable, judgment-heavy tasks a person still triggers or reviews | High-volume, fully-defined, rule-based processes that run the same way every time |
What an Attended Bot Actually Does
An attended bot sits on a specific employee’s desktop and waits to be invoked, usually with a button click, a keyboard shortcut, or a trigger inside an application the person is already using. It then automates a defined sub-task, such as pulling data into a form, reformatting a document, or cross-referencing a record across systems, while the employee stays in the loop to handle exceptions or make a final judgment call. Because it only runs when a human starts it, an attended bot needs no dedicated server or virtual machine; it consumes the same workstation the employee is already using. Microsoft licenses this model directly: its Premium plan, at $15 per user per month (billed annually), bundles cloud flows with attended desktop flows under a single per-user price, according to Microsoft’s own Power Automate pricing page.
What an Unattended Bot Actually Does
An unattended bot runs on its own machine (physical or virtual) and executes without a person present to start it or watch it work. It’s typically triggered by a schedule, a queue item, or an event from another system, and it runs the same logic every time with no variation unless the underlying data changes in a way the bot wasn’t built to handle. Because it has to occupy a machine for the duration of its run, unattended automation is priced per bot rather than per user: Microsoft’s Process plan costs $150 per bot per month, and its Hosted Process plan, which adds a Microsoft-managed virtual machine so you don’t have to provision your own, costs $215 per bot per month, again per Microsoft’s own pricing page. A single bot can only run one unattended flow at a time, so running five processes concurrently around the clock means licensing five bots, not one.
How UiPath and Automation Anywhere Price the Same Split
UiPath doesn’t break attended and unattended pricing into separate line items the way Microsoft does. Its published Basic plan, starting at $25/month, bundles two robots with a small number of user seats (up to 5 Basic, 5 Plus, and 1 Pro user), without the pricing page specifying how many of those robots are attended versus unattended. Anything beyond Basic — the Standard and Enterprise tiers, which is where most production unattended automation actually runs — requires a custom quote from UiPath sales, so there’s no public per-robot rate to cite for serious unattended deployments.
Automation Anywhere is even less transparent: its own site publishes no pricing at all beyond a capped, free Community Edition, and the only way to get a quote for either attended or unattended bot licenses is to talk to sales. Third-party pricing research has surfaced old reference points — a 2020 press release describing a $750/month Cloud Starter Pack that included one unattended “Bot Runner” and one attended-capable “Bot Creator,” with additional unattended runners at $500/month and attended runners at $125/month — but those figures are more than five years old and Automation Anywhere’s current site gives no way to confirm whether they still apply. We’re flagging that explicitly rather than presenting dated numbers as current pricing.
The Real Trade-off: Cost vs Control
Attended automation is cheaper per seat and faster to deploy because it doesn’t need its own infrastructure, but it only saves time during the minutes an employee actively uses it, and it can’t run overnight or scale to volumes a person physically can’t trigger. Unattended automation removes the human bottleneck entirely and can run 24/7, but each concurrent process needs its own licensed bot and, in Microsoft’s case, potentially its own hosted virtual machine, so costs scale directly with how many processes you want running at once rather than with how many employees you have.
In practice, most organizations don’t choose one model exclusively. A common pattern is to start with attended bots on a handful of well-understood, high-friction tasks to prove value quickly and cheaply, then migrate the most stable, highest-volume of those processes to unattended bots once the logic is reliable enough to run without a human watching it.
When You Need Attended Automation
Attended bots fit processes where a person still needs to exercise judgment, handle exceptions, or satisfy a compliance requirement that a human sign off on the action. Customer service agents pulling customer data into multiple systems during a live call, underwriters assembling a loan file before making a decision, or finance staff reconciling an invoice flagged as unusual are all good candidates: the bot removes the repetitive data-handling, but the human stays accountable for the outcome.
When You Need Unattended Automation
Unattended bots fit processes that are fully rule-based, high-volume, and don’t require human judgment once the rules are defined: nightly batch reconciliation, invoice processing against a fixed set of validation rules, data migration between systems, or report generation that runs on a fixed schedule. If the process runs the same way every single time regardless of who’s watching, it’s a strong candidate to move off a person’s desktop and onto a dedicated unattended bot.
Bottom Line
Attended and unattended bots aren’t a better-or-worse choice; they’re priced and deployed differently because they solve different problems. Budget for attended automation per employee who’ll use it, and budget for unattended automation per process you want running independently, not per person — and when comparing vendors, check whether a platform publishes a real per-bot or per-user rate (as Microsoft does) or requires a sales call to find out (as UiPath’s higher tiers and Automation Anywhere do).
FAQ
Can one bot license cover both attended and unattended work?
Not typically. Microsoft licenses them as separate plans (Premium for attended, Process/Hosted Process for unattended); check each vendor’s own pricing page, since bundling varies.
Do unattended bots need their own computer?
Yes. An unattended bot needs a machine (yours or a vendor-hosted VM) dedicated to it for the duration of each run; one bot license generally covers one concurrent run.
Is attended automation always cheaper?
Per seat, usually yes — Microsoft’s attended plan is $15/user/month versus $150+/bot/month for unattended — but attended automation only saves time while an employee is actively using it, so the comparison depends on volume, not just sticker price.
Which type should a new RPA program start with?
Many organizations start with attended automation on a small number of high-friction tasks to prove value before investing in the infrastructure unattended bots require, though this varies by process maturity and in-house technical capacity.
Why don’t UiPath and Automation Anywhere publish per-bot prices like Microsoft?
Both companies publish only entry-level or free-tier pricing; their Standard, Enterprise, and comparable paid tiers (where most unattended production work runs) require a custom quote, according to their own pricing and sales pages.
