- Introduction
- Getting started
- Understanding the solution development lifecycle
- Solution components - Studio Web and Orchestrator
- Overview of the Solutions UI
- Developing automations with and without solutions
- Solutions feature availability
- Managing solution projects and packages
- Managing solution deployments
Solutions user guide
Developing automations with and without solutions
UiPath automations can be developed and deployed either as standalone projects or as part of a Solution. Only Studio Desktop users can create standalone projects, while in Studio Web, every new automation is created within a Solution.
A project is the fundamental unit of automation development in Studio. You can build, publish, and deploy a project independently without using Solutions.
A Solution provides a structured way to design, debug, package, configure, deploy, and manage multiple related projects and resources together. Solutions are designed for controlled, repeatable, and scalable deployments across environments.
The following comparison table explains what changes when you use Solutions in addition to standard project development.
Packaging
Table 1. Packaging differences
| Concept | Build and deploy projects | Build and deploy solution |
|---|---|---|
| Packaging (produced by the Publish button in Studio Web) | Produces a nupkg file containing one project. | Produces a .zip Solution Package containing multiple projects, their resource definitions, and deployment configuration. |
| Deployment |
You create a project from a package using the Add Process button in Orchestrator.
|
You deploy a solution from a solution package via Tenant > Solutions > Packages.
|
| Folders |
Processes are added to folders.
|
Solutions are deployed to solution folders, and all resources from that solution are automatically included.
|
| Package Requirement Resolution (Bindings) |
Performed from the Package Requirements tab in Orchestrator.
|
For the moment, this can only be done via the Package Requirements tab in Orchestrator.
|
Publishing and deployment
| Deployed packages in Orchestrator | Deployed solutions in Orchestrator |
|---|---|
| Project logs, jobs, requirements, and upgrades are managed from the folder where the project is deployed. | Upgrades are handled from the Solutions tab. Project logs, jobs, and requirements continue to be accessible from the Solution Folder. |
How to upgrade a project:
 | How to upgrade a project:
 |
How to view project logs or jobs:
| How to view project logs or jobs:
|