> 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). # Licensing and Billing Remote Desktop is measured by **concurrent users**: those with a session open at the same time, not the total number of registered people. 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 sessions open at the same time | | Licenses | The maximum allowed concurrent users | > #### 📘 Why it is 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 by the simultaneous peak, and not by the total, aligns the cost with actual usage. For example: a client 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 staff | | Usage profiles | Distinguish regular users from occasional users | | Margin | Leave some slack above the usual peak for peak days | ### Where it is controlled The maximum number of concurrent users is defined in the section **Licenses** of the Remote Desktop subscription. There you adjust it as the client's demand evolves. ### How billing works | Aspect | Detail | | ------------------- | ------------------------------------------------------------------------ | | Billing unit | Concurrent users | | It is not billed by | Total registered users | | Adjustment | You increase or decrease the concurrent count according to actual demand | ### Best practices * Size it by the peak of simultaneous sessions, with a small margin for peak days. * Review the concurrent count when the client grows or changes shifts, instead of overprovisioning 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.plenit.com/docs-en/productos/remote-desktop/details/licensing-and-billing.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.