---
title: "Ballet vs UiPath"
description: "TL;DR: UiPath is an RPA leader evolving into \"agentic automation\" — bots that interact with UI screens, orchestrated by Maestro and Agent Builder. Ballet is API- and MCP-native agent ops with no screen-scraping bots. Choose UiPath for legacy UI automation at scale; choose Ballet for modern API-driven agent workflows."
canonical_url: "https://docs.ballet.dev/articles/ballet-vs-uipath-V1vXUGHLpb"
md_url: "https://docs.ballet.dev/articles/ballet-vs-uipath-V1vXUGHLpb.md"
---
# Ballet vs UiPath

**TL;DR:** UiPath is an RPA leader evolving into "agentic automation" — bots that interact with UI screens, orchestrated by Maestro and Agent Builder. Ballet is API- and MCP-native agent ops with no screen-scraping bots. Choose UiPath for legacy UI automation at scale; choose Ballet for modern API-driven agent workflows.

## What UiPath is

UiPath pioneered robotic process automation (RPA): software robots that click through applications, enter data, and follow scripted paths. In 2026 UiPath rebranded around **agentic automation** — AI agents (Agent Builder) that reason over tasks, coordinated by **Maestro** alongside existing RPA bots. The bots remain the execution layer for deterministic UI tasks; agents add a reasoning layer on top.

## Where UiPath is strong

* **UI automation** — automate apps without APIs by mimicking human clicks and keystrokes.
* **Mature platform** — large enterprise install base, process mining, document understanding.
* **Maestro orchestration** — coordinate agents, humans, and bots in one workflow.
* **Attended + unattended bots** — desktop assistants and back-office automation.
* **Enterprise governance** — centralized bot management, audit, and compliance tooling.
* **Action Center** — human tasks with a `taskId`; Wait For Form Task And Resume parks a job until a person acts.

## How Ballet is different

* **Automation surface** — UiPath: screen/UI (RPA bots); Ballet: APIs, webhooks, MCP tools.
* **Build model** — UiPath Studio + Agent Builder vs Ask Ballet + playbook editor.
* **Legacy apps** — UiPath is strong when no API exists; Ballet needs API, MCP, or HTTP access.
* **AI agents** — Agent Builder + Maestro vs console agent + playbook agent steps.
* **Infrastructure** — bot runners and orchestrator vs fully managed cloud + sandbox.
* **Best fit** — SAP screens / mainframe UI vs SaaS APIs, web research, and code steps.

UiPath wins when your process lives in **applications without APIs** — green-screen ERP, desktop legacy tools, "Open Outlook / Open SAP" desktop flows. Ballet wins when your systems expose **APIs, webhooks, or MCP connectors** and you want agent-driven ops without deploying a bot fleet. Ballet does **not** ship Power Automate–style desktop RPA steps.

## Durable wait / human tasks

Both park a job and wake it with a correlation token:

* **UiPath** — Job ID + Action Center `taskId` (Wait For Form Task And Resume).
* **Ballet** — `runId` + `requestId` on `state.resume` after `metaphor.waitForInput`.

Wake Ballet with Studio Continue or `POST /api/runs/:id/reply`. See [How do I wake a suspended run with reply or resume?](/articles/how-do-i-wake-a-suspended-run-with-reply-or-resume-EDYuheV1x4).

## When to choose UiPath vs Ballet

**Choose UiPath when:**

* You must automate through the UI because no API exists.
* You have a large RPA investment and want to add agentic layers via Maestro.
* Process mining and document understanding are core requirements.

**Choose Ballet when:**

* Your integrations are API-first (Slack, Zendesk, Salesforce, custom HTTP).
* You want Ask Ballet to build playbooks with code, MCP tools, and durable HITL pause/resume.
* You prefer agent ops over maintaining bot infrastructure and screen selectors.

The winning enterprise architecture often uses **both**: UiPath bots as the "hands" for legacy UI; Ballet playbooks as the "brain" for API-native agent workflows.

## Related articles

* [Why Ballet](/articles/why-ballet-Y3eZAkChuo)
* [Ballet vs Power Automate](/articles/ballet-vs-power-automate-Dreqn0oreO)
* [How do I pause and resume a playbook run?](/articles/how-do-i-pause-and-resume-a-playbook-run-TK6ueiBF0d)
* [Ballet vs Automation Anywhere](/articles/ballet-vs-automation-anywhere-aje6HAqyc8)
* [Ballet vs Workato](/articles/ballet-vs-workato-qLVlGlGMvu)
* [Playbook Recipes](/collection/playbook-recipes-vpHgCkHFZo)