Questions about Licenses while creating development, UAT & Production Environment

Help Robot
,
1

HI Guys,
So the scenario is now we have 1 orchestrator license, 1 Automation Developer License (Studio) and 2 unattended robots. But We want to build 3 environments (Development, UAT & Production) for better production

So right now, we are thinking purchase extra license. Originally, I was thinking to purchase 1 more non-production robot and 1 on-premise orchestrator license and the setting would be.
Dev Envir: 1 x Studio license.
UAT Envir: 1 x non-production license. 1x orchestrator license (control DEV + UAT)
Production : 1 x unattended robot. 1 x orchestrator (Control Production)

Does it makes sense? If no, please suggest, also let me know what types of license should I purchase.

Also I would like to ask For Orchestrator License:
Do we need to purchase the license separately? Or already include when we purchase robot license ?

1 Like
2

Hi Gary, what is the architecture that you currently have? I understand currently you have 2 environments, 1 Development and 1 Production.

The setup would very much depend on you are currently in the new licensing model of UiPath or the older one.

3

When did you get this license? is it just recently or have long been a UiPath end customer? This is because licensing model changed this year.

4

I have brought the licenses on March 2022. May I ask the differences of new and old license?

Actually, we decided the restructure the architecture, meaning we will create new architecture from zero. That’s why I would like to ask the best practice for building those environments.

5

Hi Gary, I’m assuming it is the old licensing Model due to the new model being introduced after March. For this, it is best to speak to the vendor you worked with. They will be able to confirm.

As for Architecture, it is best practice to have different environments. One for Dev/UAT/Prod.
Some even have more than 3, such as Staging, Pre-Prod, etc… it really depends on the sensitivity and controls involved.

Please refer to the UiPath documentation related to Architecture.

6

Thanks. But may I ask what the is main difference between old and new license? Or anywhere I can find related information?

And also, assume that we confirm to build 3 environments(Dev/UAT/Prod). What type of licenses would you suggest us to purchase? Or at least we should look for?

7

Hi Gary,

Main difference relies on the flexibility of the new licensing model to be deployed on any available environment without worrying about cost difference.

The new licenses are called “Flex” License due to it can be setup either on Automation Cloud, Automation Suite, or On-Premise without having to worry about price changes.
Also, how i see it is any license that you purchase will be able to connect to a UiPath Orchestrator Service without having to worry if you will be buying an Orchestrator license. This is because any license purchased will come with a UiPath Orchestrator Service. It just depends on whether you want it hosted via UiPath Automation Cloud, Automation Suite, or On-Premise.

The old licensing model, you have different license options and you have to think of whether you need to buy UiPath Orchestrator as well. If you buy an automation developer, that is it, you have an automation developer. In the event you want to have a UuPath Orchestrator, then you need to buy a UiPath Orchestrator License (Non-Prod). I hope this clarifies.

1st one will include UiPath Orchestrator even if you want it or not, it does not matter if you are not going to use it. You will be able to have access to it.

2nd one, you need to consider. If you need it, then you have to buy it. If not, then you dont need to buy any.

Please refer to the licensing guide for more information. Feel free to ask me if there are other questions.

https://licensing.uipath.com/

For your 2nd point, note, this is my opinion only and not given by UiPath.

New Licensing:

Development Environment - UiPath - Flex - Automation Developer - Named User
Non Production Environment - UiPath Flex - Unattended Robot - Non Production
Production - UiPath - Flex - Unattended Robot, UiPath - Flex - Attended - Named User

Again, the license types I listed here are based on licensing.uipath.com and is only for basic RPA implementation.

There are many more licenses available depending on the services that you would want to consume. As for the quantity, it depends on how many you require. I leave that up to you. I believe there is a minumum number of licenses required. This is something your vendor would be able to cover :slight_smile:

Hope this helps!

Sean

8

Thanks a lot. @seanrockvz13

9

Btw, I have asked and seems I have 2 unattended robot and Orchestrator - Standard Licenses. And the unattended robot description stated that require Orchestrator

image
image1328Ă—106 2.95 KB

So does it mean:

  1. Even when I purchase Flex license, for example, Unattended/non-production, do I need to still install orchestrator and manage those 2 unattended robots?
    Or I can use Automation Cloud/Suite/on-premise to mange all?
10

@seanrockvz13

11

Hi Gary,

If you are using on premise, you will need to set it the Orchestrator up still and make sure the licenses of unattended robot are with the orchestrator license.

However, if you are using automation cloud, the unattended robot licenses should be connected to your cloud support id.

Take note that without Orchestrator, the unattended robots are merely like attended robots. Orchestrator is the key to life of unattended robots.

also, you mentioned flex licenses, pls ensure your licenses are compatible. If you are using old skus vs new skus, you might need to raise a UiPath support ticket.

Just check with your vendor first.

12

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.