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

# Frequently Asked Questions

Frequently asked questions about Servers: what they are and how they're billed, size and images, networks and security, and backups.

Each answer links to the concept, guide, or reference where the detail is.

<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 it is and how it is billed</strong></td><td>What a server is, the pay-as-you-go model, and the division of responsibilities.</td><td><a href="https://docs.plenit.com/docs-en/platform/billing/details/the-invoice.md">The Invoice</a></td></tr><tr><td><strong>Size and images</strong></td><td>How to size, scale resources, operating systems, and reusable images.</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>Networks and security</strong></td><td>Types of network, your own firewall with VNF, VPN, and load balancing.</td><td><a href="https://docs.plenit.com/docs-en/productos/servers/concepts/networks.md">Server Networks</a></td></tr><tr><td><strong>Backups</strong></td><td>Automatic backup, snapshots, protection against ransomware, and continuity.</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></tbody></table>

### What it is and how it is billed

<details>

<summary>What is a Plenit server?</summary>

It is a virtual machine, Windows or Linux, that runs on our infrastructure and that you deploy, scale, and manage from the panel. For your customer, it works like a dedicated server; for you, like a resource you activate in minutes and pay for as you use it, without buying or maintaining hardware. More in [What is a Server?.](https://docs.plenit.com/docs-en/productos/servers/concepts/what-it-is.md)

</details>

<details>

<summary>How is it billed?</summary>

Pay-as-you-go, in €/month or €/hour and with no commitment. Servers are grouped into subscriptions, which are your unit of organization and billing; within a subscription you deploy as many servers as you need.

</details>

<details>

<summary>What do you operate and what do I operate?</summary>

We operate the foundation: the host and virtualization, storage, network controls for the infrastructure, and the data center. You operate your server: the data, accounts and identities, the operating system, applications, firewall rules, and control of your backups. On Layer 2 networks or with Direct IP, you also manage the entire network stack with your own appliance.

</details>

<details>

<summary>In which data centers and with which certifications?</summary>

The infrastructure is our own and is certified (ISO 27001 and ENS, among others). Details on regions, availability zones, and certifications are in Details.

</details>

### Size and images

<details>

<summary>How do I choose the server size?</summary>

You decide CPU, RAM, and disk according to your customer's workload, from 1 vCPU / 1 GB to 32 vCPU / 128 GB. The recommendation is to start sized to what the workload needs today, not to overprovision: you pay for what you use and can scale later. You have a table of starting points by workload type in [Size your server.](https://docs.plenit.com/docs-en/productos/servers/concepts/size-cpu-ram-disk.md)

</details>

<details>

<summary>Can I expand resources later?</summary>

Yes, you add CPU, RAM, or disk live, without reinstalling or migrating. Expanding the disk does not stop the server; reducing it is more delicate and should be planned. The step-by-step guide is in [How-to.](https://docs.plenit.com/docs-en/productos/servers/how-to.md)

</details>

<details>

<summary>What operating systems can I deploy?</summary>

Windows Server and the main Linux distributions (Ubuntu, Debian, AlmaLinux, Rocky Linux, Oracle Linux, among others). Windows fits ERP and Windows business software; Linux, web, databases, containers, and appliances. The full catalog of versions is in Details, and the criteria for choosing is in [Images and applications.](https://docs.plenit.com/docs-en/productos/servers/concepts/images-and-applications.md)

</details>

<details>

<summary>Can I reuse a configuration across multiple customers?</summary>

Yes. You set up a server to your liking, turn it into your own image, and deploy as many identical copies as you need. You can save up to 12 images per subscription.

</details>

<details>

<summary>What's in the Marketplace?</summary>

Preconfigured appliances and software ready to deploy: 3CX (VoIP PBX), FortiGate VM and FireboxV (firewalls you operate as a VNF), and Pandora FMS (monitoring), among others.

</details>

### Networks and security

<details>

<summary>What network types do I have?</summary>

Four: Standard (a managed Virtual Router with DNS, DHCP, gateway, NAT, and firewall, the usual case), VPC (multi-tier and the only one with site-to-site IPSec VPN), Layer 2 (pure layer 2, you manage the entire stack with your VNF), and Direct IP (public IP without NAT). The criteria for choosing is in [Server networks.](https://docs.plenit.com/docs-en/productos/servers/concepts/networks.md)

</details>

<details>

<summary>Can I use my own firewall?</summary>

Yes, with a VNF: a network appliance that you deploy and operate yourself (FortiGate VM or FireboxV, from the Marketplace). The self-managed perimeter pattern combines Direct IP as WAN, your VNF as the firewall, and a Layer 2 network as LAN. In Layer 2 and Direct IP, you define and maintain the firewall rules.

</details>

<details>

<summary>Can I connect the cloud with the customer's office?</summary>

Yes, on a VPC network you set up site-to-site IPSec tunnels to connect the cloud with the office, and remote access VPN for users. Each gateway supports up to 10 VPNs, with IKEv1, IKEv2, or Auto, and split tunneling when you need it. The step-by-step configuration is in [How-to.](https://docs.plenit.com/docs-en/productos/servers/how-to.md)

</details>

<details>

<summary>How do I distribute the load across several servers?</summary>

With a load balancer on a Standard network. In addition to improving performance, it gives you a way to keep the service running while a machine is under maintenance.

</details>

### Backups

<details>

<summary>Do the servers include backup?</summary>

Yes, each server includes automatic scheduled backups: every hour, every day, and every week. They are configured per disk and per server, and retention is configurable. More in[ Backup and data protection.](https://docs.plenit.com/docs-en/productos/servers/concepts/backup-and-data-protection.md)

</details>

<details>

<summary>What's the difference between a backup and a snapshot?</summary>

The backup is automatic and saves versions of your disks according to the schedule. The snapshot is a manual snapshot of the entire machine that you take at a specific moment, for example just before a risky change, to roll back if something goes wrong.

</details>

<details>

<summary>Do backups protect me against ransomware?</summary>

Backups are stored as read-only: once created, they cannot be modified or encrypted from the server. If ransomware reaches the machine, it cannot affect the backups and you have somewhere to restore from.

</details>

<details>

<summary>Does backup guarantee that the service keeps running?</summary>

No. Backup is for recovering data and state, not for keeping the service available if a machine fails. That is continuity design, with several servers and the right architecture. Backup and continuity complement each other; they do not replace each other.

</details>

### Next steps

<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>Quick Start</strong></td><td>Create your first server step by step.</td><td><a href="https://docs.plenit.com/docs-en/productos/servers/quickstart.md">Quick Start</a></td></tr><tr><td><strong>Concepts</strong></td><td>Understand the service design decisions.</td><td><a href="https://docs.plenit.com/docs-en/productos/servers/concepts.md">Concepts</a></td></tr><tr><td><strong>How-to</strong></td><td>Step-by-step guides to deploy and operate your servers.</td><td><a href="https://docs.plenit.com/docs-en/productos/servers/how-to.md">How-to</a></td></tr><tr><td><strong>Details</strong></td><td>Specifications, networks, and certifications.</td><td><a href="https://docs.plenit.com/docs-en/productos/servers/details.md">Details</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/faq.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.
