Which UiPath license for a single internal bot? A practical example

You want to automate exactly one process: an internal validation bot that checks data, not a fleet of 200 robots. The question of the right UiPath license comes up immediately. Here is the short answer, with the reasoning below.

Why the free Community Edition is ruled out for an internal bot

The UiPath Community Edition is not permitted for a productive internal bot. According to the UiPath Community Agreement, it may only be used for non-commercial purposes such as training and research. A bot that supports a real business process does not fall under this, regardless of company size.

• Right of use: The current Community Agreement explicitly allows only non-commercial use; a productive internal bot violates this (Source).
• Old threshold outdated: Previously, an SME exception applied for under 250 users or machines and under USD 5 million in annual revenue. This threshold has been replaced by the stricter non-commercial wording.
• No support: Community users have no SLA and no escalation path if the bot fails in production. For a bot that a workflow depends on, that is a real risk.

Attended or unattended: which UiPath license your single bot needs

For a single internal bot, you need exactly one paid robot license. Whether it becomes the attended or the unattended variant is decided by just one question: does a human start the bot, or does it run on its own?

• Attended: An employee starts the bot at her workstation. Cheaper and suited to workflows that someone triggers anyway.
• Unattended: The bot runs on a schedule or triggered by an event, even at night and on weekends, entirely without supervision.
• Price difference: According to third-party estimates, an unattended robot costs roughly three times as much as an attended robot (Source). UiPath itself does not publish fixed list prices.
• For the validation bot: If it checks data in the background after hours, unattended is the right choice. If it is started as needed by a case worker, attended is enough and saves around two-thirds of the cost.

Cloud or self-hosted: for a single bot, almost always the Automation Cloud

For a single bot, the UiPath Automation Cloud is the pragmatic route. You save yourself your own Orchestrator server, updates, and maintenance. Only when data protection or a legacy system requires processing in your own data center does the self-hosted variant pay off. UiPath documents the details of the license tiers in its official licensing overview.

An example from NordFlux practice

A client wanted incoming form data to be automatically checked against its specialist system: a single bot, one process. Because a case worker triggers the run herself every morning, an attended license via the Automation Cloud was enough. A more expensive unattended license would not have added any value in this case. We clarify this question at the start of every RPA project, before a license is purchased. More on this under AI Agents. Where an AI agent is a better fit than an RPA bot is covered in the article AI Tool or AI Agent.

Frequently asked questions

May I use the UiPath Community Edition for an internal company bot?

No. According to UiPath, the Community Edition is only allowed for non-commercial purposes such as training and research. A bot that productively supports an internal business process needs a paid license, regardless of company size.

Attended or unattended for a single validation bot?

If a human starts the bot, the cheaper attended license is enough. If it runs unsupervised on a schedule, you need an unattended license. For pure background checks, unattended is right; for occasional runs, attended.

What does getting started with a single bot cost?

UiPath does not publish fixed list prices. As a rough guide, an unattended robot costs roughly three times as much as an attended robot, according to third-party estimates. For a first internal bot, the attended license in the Automation Cloud is usually the cheapest way to start.