# The automation that took a quarter, live this week | Ballet

> Canonical: https://ballet.dev/ballet-vs-uipath

No scripting, no 2 to 4 week RPA builds, no waiting on engineers. Ballet ships automation in hours and keeps it running when systems change.

Automation without the scripting or the wait.

Legacy RPA takes weeks and breaks on every screen change. Ballet ships the automation in hours, in plain language, and keeps it running when your systems change.

## Compare

| | Ballet | UiPath |
| --- | --- | --- |
| Approach | Deterministic workflows + agents, written as code | Visual RPA, recorded steps and scripting |
| New integration | Generated on demand against any API | Custom scripting, weeks per build |
| Complex multi-system work | Scales, written as code | Possible, but slow and brittle |
| Output when it matters | Deterministic, agentic where it help | Deterministic, breaks on UI change |
| Breakage | Evals on every step, auto-patched with a diff | Breaks when a screen or system changes |
| Review & version control | Generated code, version-controlled | After-the-fact auditing, bolt-on |
| Time to first workflow | 30 minutes | 2 to 4 weeks |


## Ballet vs UiPath, answered.

### Can Ballet do everything UiPath does?

For the cross-system automation teams get stuck on: yes, without scripting or weeks per bot.

### We already have UiPath bots. Do we rip them out?

No. Keep what works and bring Ballet in for the automations that are slow to build or break on every change

### Is the output reliable?

Yes where it matters, with agentic reasoning where judgment is needed, and it adapts instead of breaking on UI changes.

### How is it more reviewable than RPA?

Generated, version-controlled code with run history and evals on every step, not after-the-fact auditing.

## Next step

We’ll rebuild your most painful UiPath automation in Ballet, live.

[Book a demo](https://ballet.dev/signup)