> 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/servers/concepts.md).

# Concepts

Understand how a Plenit server works and decide how to set it up for each customer

Explanations and definitions of the key concepts of Servers: what it is, how it is sized, images, networks, access, and data protection.

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>What is a server?</strong></td><td>What a Plenit server is, the pay-as-you-go model, and the division of responsibilities between Plenit and the partner.</td><td><a href="https://docs.plenit.com/docs-en/productos/servers/concepts/what-it-is.md">What Is a Server?</a></td></tr><tr><td><strong>Size your server: CPU, RAM, and disk</strong></td><td>How to choose CPU, RAM, and disk according to the customer's workload, with starting points by usage type and tips for scaling.</td><td><a href="https://docs.plenit.com/docs-en/productos/servers/concepts/size-cpu-ram-disk.md">Size Your Server</a></td></tr><tr><td><strong>Images and applications</strong></td><td>Available operating systems, how to create reusable custom images, and which appliances the Marketplace offers.</td><td><a href="https://docs.plenit.com/docs-en/productos/servers/concepts/images-and-applications.md">Images and Applications</a></td></tr><tr><td><strong>Server networks</strong></td><td>The four network types (Standard, VPC, Layer 2, and Direct IP) and the criteria for choosing each one.</td><td><a href="https://docs.plenit.com/docs-en/productos/servers/concepts/networks.md">Server Networks</a></td></tr><tr><td><strong>Remote access</strong></td><td>The ways to connect to your servers and manage them: RDP, SSH, VPN, and console.</td><td><a href="https://docs.plenit.com/docs-en/productos/servers/concepts/remote-access.md">Remote Access</a></td></tr><tr><td><strong>Backup and data protection</strong></td><td>How automatic backups and snapshots work, retention, and protection against ransomware.</td><td><a href="https://docs.plenit.com/docs-en/productos/servers/concepts/backup-and-data-protection.md">Backup and Data Protection</a></td></tr><tr><td><strong>Glossary</strong></td><td>Definitions of the terms specific to Servers.</td><td><a href="https://docs.plenit.com/docs-en/productos/servers/concepts/glossary.md">Glossary</a></td></tr></tbody></table>


---

# 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/servers/concepts.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.
