License-Uipath

Help Studio
, , , , , ,
1

Hello @advanced @uipatth

I am trying to understand “on premises orchestrator” license and “standalone licesne”…

Can anyone help me explain both of these licenses?
Their differense and which one is better use??

Thanks in advance.

2

Hi @Vaibhav_Shukla

  1. On-Premises Orchestrator License:

    • The On-Premises Orchestrator license is associated with UiPath’s Orchestrator platform, which is a centralized server-based application used to manage and deploy automation processes.
    • The Orchestrator is typically installed on a server within your organization’s network (on-premises) or private cloud.
    • This license type allows you to connect multiple UiPath Robots to the Orchestrator and manage them centrally.
    • It provides features such as scheduling, monitoring, and reporting of automation processes across multiple machines.
    • With this license, you can deploy attended and unattended robots and orchestrate the entire automation workflow.

  2. Standalone License:

    • A Standalone license is associated with UiPath Studio and UiPath Robot installed on a single machine, which is not connected to a central Orchestrator server.
    • It is intended for individual developers or small teams who want to create and run automation processes locally without the need for centralized management.
    • A Standalone license allows you to create automation workflows using UiPath Studio and execute them using UiPath Robot on the same machine where Studio is installed.
    • This license type is suitable for scenarios where automation development and execution are done on the same machine without the need for a centralized server or coordination with other robots.

The main difference is that:

  • On-Premises Orchestrator License is used for centralized management and orchestration of multiple UiPath Robots across the organization. It provides a powerful automation platform with features like scheduling, monitoring, and reporting.

  • Standalone License is intended for individual developers or small teams who want to develop and execute automation processes on a single machine without the need for a central server.

If you have a larger automation infrastructure and want to manage and scale your robots efficiently, the On-Premises Orchestrator license would be more suitable. On the other hand, if you are an individual developer or have a small team working on automation, a Standalone license may be sufficient for your needs.

Hope it helps!!
Regards,

3

Hi @Vaibhav_Shukla

On-Premises Orchestrator License:
The On-Premises Orchestrator is part of the UiPath Orchestrator product, which is a web-based application that allows you to manage and monitor your UiPath robots and automation processes. It provides centralized control, scheduling, monitoring, and logging capabilities for your automation deployments. With an On-Premises Orchestrator license, you install and host the Orchestrator application on your own infrastructure (servers) within your organization’s network. It is suitable for organizations that prefer to keep their automation and robot management entirely on their premises, without relying on cloud-based services.

Standalone License:
A Standalone License refers to a license for UiPath Studio, which is the development environment used to design and build automation workflows. When you purchase a Standalone License, you get a license key that you can activate in UiPath Studio. With this license, you can use Studio to create automation projects and deploy them on your local machine or on any machine without needing a connection to an Orchestrator instance.

4

if you are talking about Orchestrator only then there are no differences between them.

Standalone License for Orchestrator where you have a single license code bundle with Robots, Studio, and Other and activate it on your local server or computer. it doesn’t matter whether cloud or not.

but if you are talking about Robot or Studio. a single license code only contains a single Robot or Studio. this case if you don’t want to centralize with Orchestrator because of security matters or other things. however, you still can be centralized with Orchestrator but not working for the Unattended Robot.

Cheers,
Indra