> 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-2/concepts/what-it-is.md).
# What is a Server?
A Plenit server 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 by usage.
> #### 📘 Key idea
>
> You do not buy or maintain hardware. You activate a server, load your customer's workload onto it, and scale it when needed. The infrastructure is our responsibility.
### How it works
You don't manage physical equipment. We operate the physical servers, virtualization, and the network; you work on a virtual machine with its assigned resources — CPU, RAM, and disk — and its operating system.
Under the hood, each server runs on our virtualization layer, with NVMe storage and VXLAN networking, on certified proprietary infrastructure (ISO 27001 and ENS, the National Security Framework). You get recent-hardware performance without buying or maintaining equipment.
### Where it fits in your customer's infrastructure
A server can stand alone or be part of a larger architecture. Some common uses:
* The customer's ERP (for example Sage or SAP Business One) on Windows Server, with its database.
* Web or business applications that need to be continuously available.
* Databases, mail, or DNS on Linux.
* A dedicated firewall (FortiGate VM, FireboxV) as the gateway to the customer's network.
You combine several servers, connect them via private network, and design the topology each customer needs.
### Subscription and billing
The servers are grouped into **subscriptions**, your organization and billing unit. Within a subscription you can deploy as many servers as you need.
You pay per usage — in €/month or €/hour — with no commitment. You scale resources live: if a server runs short, you add CPU, RAM, or disk without reinstalling.
### What we operate and what you operate
A server follows our shared responsibility model for infrastructure (IaaS):
* **We operate the foundation**: the host and virtualization, storage, infrastructure network controls, and the data center.
* **You operate your server**: the data, accounts and identities, operating system, applications, network controls and firewall rules, and the recovery and control of your backups and configurations.
In Layer 2 networks or with Direct IP, you also manage the entire network stack through your own appliance (FortiGate VM, FireboxV).
In short: we provide and maintain the infrastructure; you design and operate what runs on top.
### Next steps
* Create your first server with [Quick Start](/docs-en/productos/servers/quickstart.md)
* Choose the size in [Size your server.](/docs-en/productos/servers/concepts/size-cpu-ram-disk.md)
* Design connectivity in [Server networking.](/docs-en/productos/servers/concepts/networks.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/servers-2/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.