Build, connect, and deploy — all in one place.
For years, building automations meant focusing on one workflow at a time.
If your business process was complex, you had to develop multiple automations separately, keep them aligned manually, and document every dependency yourself.
Deployment meant juggling resources and double-checking configurations — every single time.
Those days are over.
One Studio. Every automation.
With the Unified Developer Experience, you can now design, connect, and deploy entire business processes from a single Studio instance.
You can build side by side:
- RPA Workflows
- Agents
- Agentic Processes
- Apps
- API Workflows (Preview)
- and more automation types that will soon be available.
- And all their platform resources — Queues, Assets, Storage Buckets, Connections, and more
Everything lives in one shared context, so your automations can seamlessly invoke one another and reuse the same resources.
Try it out now on studio.uipath.com !
Learn more in our documentation
From isolated automations to connected Solutions
This is more than a design-time update — it’s a new development model.
When you publish, everything is bundled into a single Solution package: automations, agents, resources, and configuration, all packaged together.
Deployment becomes a predictable, one-step process. No more manual setup, no more missing dependencies — just click Deploy and go live.
The experience, your way
Whether you use the Web version Studio or the Desktop one, the unified experience adapts to your workflow.
In the Web version of Studio
Every new automation you build uses the new experience by default.
Mix and match scenarios that were never possible before — like designing in the same context an Agent with the Windows automations tools, or an Agentic Process with the implemented RPA workflow.
In the Desktop version of Studio
You can keep working as you always have, or opt in to the new experience for Windows and Cross-Platform workflows.
And when you’re ready to publish, you can seamlessly switch to Studio Web to deploy the full Solution.
Why it matters
- Faster design: Build multiple automations and their dependencies together.
- Simpler debugging: All resources are in place — no need for manual setup.
- Predictable deployment: Publish once, deploy once, everything included.
- Cross-tool collaboration: Move freely between Studio Web and Desktop.
Hands-on
Design Time
You can now design Agents and Agentic Processes alongside other automations.
For example:
- Build an Agent together with its tools.
- Develop an Agentic Process and its implementation in one environment.
Debugging ensures all defined resources exist and are ready for execution.
When you’re done, publishing bundles everything into a Solution — the complete, ready-to-deploy package.
In the Web version of Studio
Every new automation automatically uses this unified experience.
This unlocks new combinations like:
- Agents that use automations as tools, even Windows-based automations.
- Agentic Processes that are implemented using workflows and now they can be developed together
In the Desktop version of Studio
You can still use the unified experience, but with a few differences:
- Resource definitions can only be copied from existing ones in the UiPath Platform.
- Only RPA Workflows (Windows or Cross-Platform) can be directly edited. The other automation types can be edited in the Web version of Studio
- Resource provisioning and Deployment configuration are available only in the Web version of Studio.
- Publishing from the Desktop version of Studio publishes the current automation; publishing the full Solution package must be done in the Web version of Studio.
You can freely switch between Web and Desktop Studio to collaborate on different parts of a Solution (e.g., build an Agent in Web, edit its Windows tools in Desktop).
Publishing and Deployment
Publishing now creates a Solution package — a complete unit that contains:
- All automations
- All required platform resources
- Configuration for deployment
You can use the Notification area of the platform to keep track of the publishing process.
Deployment happens in two steps:
- The Solution package is created and published.
- The Solution package is deployed at the folder level.
When publishing to your Personal Workspace, both steps happen automatically — just as before.
Each deployed Solution creates its own folder with:
- The defined automations and resources
- The corresponding NuGet feeds are aligned to that folder scope
For more details, see the Solutions Management documentation.
Final Takeaway
This new, unified developer experience brings everything together — automations, agents, and resources — in one design and deployment flow.
It simplifies collaboration, eliminates manual setup, and makes building complex business processes in UiPath faster, cleaner, and more predictable.
