> 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/what-it-is.md).
# What is Remote Desktop?
Remote Desktop is a centralized, remote and secure work environment. Your users access their applications and desktop from anywhere and any device, and you offer it to your client as a service managed by you.
### How it fits
The client no longer depends on local devices with everything installed. The applications and data live in the environment, and each employee accesses their workstation from the office, from home or on the go, with the same experience. You decide what each user sees, which applications they use and how they connect.
### What makes up an environment
A Remote Desktop environment brings together three pieces within a subscription:
* **Servers (hosts)**: one or more Windows servers that serve the sessions. You start with one and grow to multi-server when the load requires it.
* **Users**: the people in the organization whom you give access to, each with their connection mode and permissions.
* **Applications**: the software you publish in the environment and assign to each user.
### Two subscriptions for the same environment
* **Remote Desktop subscription**: you manage users, permissions, connection modes, applications and concurrent access licenses.
* **Server subscription**: you manage the server underneath, with Server-specific tasks: expansions, restarts, firewall and backups.
Day-to-day operations are centralized from the Remote Desktop card in the panel.
### What you manage and what we manage
Remote Desktop is a managed service, but the division is clear
| You manage | We manage |
| ---------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- |
| Users and access | The infrastructure on which the environment runs: virtualization, storage and network |
| Applications you publish | The data center and its physical security |
| Environment data | The management tools integrated into the panel |
| Server operating system: updates (with the Windows Updates feature in the panel) and antivirus | |
| Environment configuration: connection modes, permissions and printing | |
> #### 📘 You handle the operating system
>
> As in Servers, the operating system of the hosts is your responsibility. We make the task easier with tools in the panel (for example, Windows Updates), but you decide and apply the OS updates and protection.
### How it is billed
Remote Desktop is billed by **concurrent users**: the number of users who can have a session open at the same time, not the total number of users registered. You can give access to more people than those who connect at the same time and size according to that peak.
### Where to go next
* How your users connect: [Connection modes and permissions.](/docs-en/productos/remote-desktop/concepts/connection-modes.md)
* How you onboard users and publish applications: [Users and applications.](/docs-en/productos/remote-desktop/concepts/users-and-applications.md)
* How you choose the environment resources: [Size your environment.](/docs-en/productos/remote-desktop/concepts/size-your-environment.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 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/concepts/what-it-is.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.