Orchestrator Tenants and Licensing?

Help
1

So I’ve seen a few different posts here regarding multi-tenancy and their impact on licensing, what I’m not sure I understand is it’s relationship to license cost.

To add multi-tenancy to Orchestrator, if I’m understanding the posts here correctly, we how have to have a separate license for each tenant, and the maximum number of bots that were originally assigned to the first license must now be distributed across both the “original” default tenant and the new one… yes?

How does this impact licensing COSTS? Would we have to pony up additional $$$ for the new tenant licenses? Or do additional costs only come into play if you have to increase the number of total bots you can have connected to the multiple tenants?

Thanks in advance.

2 Likes
2

Anyone? I am trying to propose a multi-tenant concept to my RPA team (with separate tenants for DEV, TEST and PROD environments), but cannot do so without understanding potential cost impacts… UiPath staff? Anything?

3

Hi Thomas,

That’s right.

No. So when you first create a tenant it is unlicensed until you add a license file. The same applies with the default tenant. If you don’t add a license file on it, it will remain unlicensed. Each license file that you add to your tenants has a number of Robots that you bought and you as a customer decided before how to distribute across tenants.

Let’s say you have the DEV tenant that will be used by RPA developers. On that one you will have a license file with 5 Development Robots for example.
On the PROD tenant you will have a different license file with 3 Attended and 2 Unattended Robots.

I will continue with the example above. Let’s say you now want to move 1 Attended and 1 Unattended Robot to a new tenant PROD2. You can do this at no costs(but you will have to contact our support team to make this change).

That’s true. If you want more Robots you will have to pay for the extra licenses.

I hope it’s more clear for you now.

Thanks,
Viorela

4

Thanks, Viorela … that helps a lot. Much appreciated!

5

So if I may paraphrase (just to make sure I understand correctly), if we wanted to ADD A TENANT to our existing default Orchestrator tenant, we could do that at no cost, as long as we are not ADDING new bots to the license.

We would contact you for a new license for the additional tenant, and have you move some number of bots from the original default tenant to the new one.

We wouldn’t incur additional costs until we actually ADDED new bots, either to the original default tenant or the new one.

Is this accurate?

6

Yes, that’s true. Moving Robots from one tenant to another implies no costs.

7

Hello,
I am reviewing the new licence model I see there is now Orchestrator Standard with limited tenants and an Orchestrator entreprise.
How many tenants can be created with the standard licence?

Many Thanks in advance

8

What’s the answer. An Licence FAQ would be nice

9

Hey @ovi,

The answer is informative.I need some more information in exchanging robots among tenants.

Say I have Prod1 and Prod2 tenants for production environment and 2 unattended robots.
Will I be able to schedule 2 robots on single tenant and change accordingly whenever required?

I mean connecting single robot to both tenants.If yes, is orchestrator smart enough to check if robot is available at scheduled time?

10

Can some one who achieved this help me with the solution?

11

I have a question regarding licensing. So I have 4 tenants but only 2 licenses, how am I suppose to distribute/ allocate these 2 license files among 4 tenants?