UiPath Maestro Flow vs Maestro vs Orchestrator
On this page
Quick answer
Maestro Flow is a developer-first way to author a .flow orchestration artifact. Maestro is the orchestration engine and broader product family that also includes visual process and case-management approaches. Orchestrator remains an operational surface for automation resources and execution; do not assume a Flow artifact replaces every existing Orchestrator process, queue, robot, credential, schedule, or monitoring responsibility.
UiPath states that Maestro Flow runs on the same Maestro engine. It is currently public preview, so verify the exact relationship and tenant behavior before migration.
Placement questions
| Question | Start with |
|---|---|
| Developer builds mixed agentic and deterministic orchestration as code | Maestro Flow pilot |
| Process owner models a structured business process | Maestro visual/BPMN path |
| Long-running judgment-heavy case work | Maestro case-management path |
| Existing robot jobs, resources, queues, schedules, and operations | Review current Orchestrator ownership |
Map the current artifact, identities, resources, triggers, credentials, queues, SLAs, logs, and fallback before moving anything. Run both paths against representative cases and preserve rollback.
Continue with the public preview guide and governance guide.
Official sources
Source check: August 23, 2026. Verify current product boundaries, artifacts, clients, engine, Orchestrator dependencies, and preview lifecycle.