> 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/concepts/size-your-environment.md).

# Size Your Environment

How the number of users, concurrency, and applications translate into the environment's resources, and when to move to multi-server

Sizing an environment means translating three things into resources: how many users it has, how many work at the same time, and which applications they use.

### What determines the size

* **Concurrent users**: what determines the load is how many users work at the same time, not the total number of registered users.
* **Application profile**: a light office workstation does not use the same resources as one with a demanding ERP. The heavier the applications, the more resources per user.

### The platform's recommendation

When deploying, we propose a starting size based on the users and applications planned. It's a sensible starting point: you can accept it or choose another configuration. With demanding applications, it's a good idea to test with a group and monitor actual usage before rolling it out broadly.

### One server or several

An environment starts with one server. When the load grows, you add servers and the environment becomes **multi-server**.

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-e3b2ba3e04f7664e36a5f09c6e9c78f074aed671%2Fdiagram-multiservidor-balanceador-er.png?alt=media" alt=""><figcaption></figcaption></figure>

* Users are distributed among the servers by means of a **load balancer**, which distributes the sessions.
* That way you add capacity without rebuilding the environment: you grow as your client grows.

### Adjust when the load changes

Sizing is not final. You adjust the server resources from the **Servers subscription** associated with the environment, or you add servers as demand evolves and without starting from scratch. The number of users who can log in at the same time is controlled from the section **Licenses** of the Remote Desktop subscription.

### Templates to repeat

If you set up similar environments for several clients, the **server templates** let you reuse a base configuration and deploy consistent environments, without redoing the work each time.

### Where to follow

* Who connects and how: [Connection modes and permissions.](https://docs.plenit.com/docs-en/productos/remote-desktop/concepts/connection-modes.md)


---

# 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/concepts/size-your-environment.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.
