> For the complete documentation index, see [llms.txt](https://docs.plenit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plenit.com/docs-en/productos/remote-desktop/details/licensing-and-billing.md).

# Licenses and Billing

Remote Desktop is measured by **concurrent users**: those who have a session open at the same time, not the total number of registered users. Understanding this difference is what allows you to size and budget without overshooting or falling short.

### Licensing concepts

| Term             | What it is                                 |
| ---------------- | ------------------------------------------ |
| Registered users | All people with access to the environment  |
| Concurrent users | Users with a session open at the same time |
| Licenses         | The maximum allowed concurrent users       |

> #### 📘 Why it's counted this way
>
> In most organizations, not everyone works at the same time: there are shifts, split schedules, or roles that only log in occasionally. Charging for the simultaneous peak, rather than the total, aligns the cost with actual usage.

For example: a customer with 50 registered employees, of whom at most 20 are connected at the same time, needs **20 licenses**, not 50.

### How to estimate the peak

| Signal               | What to look at                                                                      |
| -------------------- | ------------------------------------------------------------------------------------ |
| Shifts and schedules | If the team works in shifts, the peak is the largest shift, not the entire workforce |
| Usage profiles       | Distinguish regular users from occasional users                                      |
| Margin               | Leave some buffer above the usual peak for busy days                                 |

### Where it is managed

The maximum number of concurrent users is defined in the section **Licenses** of the Remote Desktop subscription. There you adjust it as the customer's demand evolves.

### How it's billed

| Aspect                 | Detail                                                                   |
| ---------------------- | ------------------------------------------------------------------------ |
| Billing unit           | Concurrent users                                                         |
| You are not billed for | Total registered users                                                   |
| Adjustment             | You increase or decrease the concurrent count according to actual demand |

### Best practices

* Size it for the peak of simultaneous sessions, with a small margin for busy days.
* Review the concurrent count when the customer grows or changes shifts, instead of oversizing from the start.

Current rates are outside this documentation: check them in the platform's pricing section.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.plenit.com/docs-en/productos/remote-desktop/details/licensing-and-billing.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
