Licensing¶

Overview¶

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).

Terminology¶

Take a license: a unit is counted as in use.
Release a license: the unit becomes available again in the pool.
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¶

Per-user license¶

Important

This model is available starting with the Teamwork plan

Principle

1 license = 1 user who has the ability to access at least one machine.

When a license is taken

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 administrator with connection capacity.

Exceptions

An Organization Owner never consumes a license.
A disabled user does not consume a license.

Releasing the license (if not Owner)

Remove all associations with machines and/or roles that grant connection capacity.
Or disable the account.
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 (summary)

Member of a group without accessible machines: does not take a license.
Admin without connection rights: does not take a license.
Temporary assignment of a role granting connection: takes a license as long as the role is active.

Floating license¶

Important

This model is available starting with the Enterprise plan

Principle

1 license = 1 active Remote Desktop session.
The license is taken when the session starts and released when it ends.

Consequences

The same user may consume multiple licenses if several concurrent sessions are allowed.
If the pool is exhausted, session opening fails.

Good usage

Ideal for rotating teams, shared workstations, peak activity.
Monitor the number of concurrent sessions allowed per user to control consumption.

Containers¶

Concurrent container license¶

Important

Containers are available starting with the Enterprise plan

Principle

1 license = 1 running container.
The license is taken when the user container starts and released when it stops.

Consequences

A user may consume N licenses if they start N containers in parallel.
If the pool is exhausted, container startup fails.

Quick comparison¶

	Remote Desktop	Containers
Counting unit	User or Active session	Concurrent container
License taken	When the user can connect (per-user model) or at session start (floating model)	At container start
Release	Removal of connection capacity or end of session	At container stop
Multi-consumption per user	Yes in floating (multi- concurrent sessions)	Yes if multiple containers run in parallel
Organization Owner	Never consumes	Applies if Owner starts containers: counts against container pool

Reference scenarios¶

Fixed team of 25 people / stable fleet - Choose Per-user license with 25 units. - Advantage: predictable cost, no waiting at peak hours.
Floor of 500 people, max 100 simultaneous connections - Choose Floating license with 100 units. - Advantage: cost optimization through license sharing.
Isolated browsing with 10 parallel container sessions - Choose 10 concurrent container licenses. - Add more if the number of simultaneous sessions increases.

Best practices¶

Limit roles that grant connection to control license consumption “per user”.
Prefer floating when concurrency is lower than the total number of users.
For containers, stop inactive environments to release licenses quickly.

Important

The choice of model (per-user vs floating) for Remote Desktop is set in your contract. Containers always use the concurrent model. Adjust your pools as closely as possible to your actual concurrency.