Licensing¶
Reemo offers two licensing models for Remote Desktop and one model for Containers. The goal is to adapt either to stable teams (reserved licenses) or to on-demand usage (floating/concurrent licenses).
Plans, features and prices are described on the Reemo pricing page.
Terminology¶
Take a license: a unit is counted as in use.
Release a license: the unit becomes available again in the pool.
Pool: the set of available licenses.
Connection capacity: the user can open a session on at least one machine (direct right, via group/role, or admin rights that include connection).
Remote Desktop¶
Remote Desktop offers two license models:
For a stable team and a fixed fleet, for example 25 people with 25 units. The cost is predictable and nobody waits at peak hours.
For many users and fewer simultaneous connections, for example 500 people and 100 connections at most. Sharing 100 units optimizes the cost.
Per-user license¶
Important
This model is available starting with the Teamwork plan.
A license is taken as soon as the user has the connection capacity, that is when:
The user is associated with at least one machine.
Or the user has a Support role granting remote control of machines.
Or the user is an organization administrator with connection capacity (except the Owner).
The Owner (the primary administrator of the organization) takes a license only if resources are assigned to them. A disabled user does not take a license. To release a license, remove the machine associations and the roles that grant connection capacity, or disable or delete the account.
Note
Usage restrictions (schedules, policies) limit access. They do not change the basic rule: a license is taken if the user can connect to at least one machine.
Edge cases:
A member of a group without accessible machines does not take a license.
An organization administrator without connection rights does not take a license.
A role that grants connection takes a license as long as it is active, even temporarily.
Floating license¶
Important
This model is available with the Enterprise plan (private cloud and on-premise).
If the pool is exhausted, opening a session fails. This model suits rotating teams, shared workstations and activity peaks. Monitor the number of simultaneous sessions allowed per user to control consumption.
Best practices¶
Limit the roles that grant connection to control license consumption “per user”.
Prefer floating when concurrency is lower than the total number of users.
Adjust your pools as closely as possible to your actual concurrency.
Important
The choice of model (per-user or floating) for Remote Desktop is set in your contract.
Containers¶
Concurrent container license¶
Important
Containers are available starting with the Enterprise plan.
Containers always use the concurrent model. If the pool is exhausted, starting a container fails. Stop inactive environments to release licenses quickly, and adjust your pools as closely as possible to your actual concurrency.
Quick comparison¶
Remote Desktop |
Containers |
|
|---|---|---|
Counting unit |
User or Active session |
Concurrent container |
License taken |
When the user can connect (per-user license) or at session start (floating license) |
At container start |
Release |
Removal of connection capacity or end of session |
At container stop |
Several licenses per user |
Yes with the floating license (concurrent sessions) |
Yes if multiple containers run in parallel |
Primary administrator of the organization (Owner) |
Only if resources are assigned |
Applies if the primary administrator of the organization starts containers: counts against the container pool |