> 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/details/technical-specs.md).

# Technical Features

The specifications of a Plenit server: compute, storage, hardware, virtualization, and physical network

The specifications of a Plenit server. To decide what size you need, go to [Size your server](/docs-en/productos/servers/concepts/size-cpu-ram-disk.md) in Concepts.

### Compute

|           |                           |
| --------- | ------------------------- |
| vCPU      | Up to 32                  |
| RAM       | Up to 128 GB              |
| Processor | Intel Xeon Scalable       |
| Scaling   | Hot, without reinstalling |

### Storage

|             |                                 |
| ----------- | ------------------------------- |
| Technology  | NVMe · NetApp All-Flash (ONTAP) |
| System disk | From 60 GB                      |
| Data disks  | Additional, each with backup    |
| Resizing    | Hot expansion                   |

Shrinking a disk is more delicate than expanding it; the procedure is in How-to.

### Hardware

|              |                         |
| ------------ | ----------------------- |
| Servers      | Dell                    |
| Processor    | Intel Xeon Scalable     |
| Memory       | DDR5 ECC                |
| Redundancy   | N+1 cluster             |
| Power        | Dual power supply (PSU) |
| Host network | Aggregated links (LAG)  |

If a cluster host fails, its virtual machines restart on another available host. This is the resilience of the physical infrastructure; the zone-based high availability design is up to you (you'll see it in Concepts when it's available).

### Virtualization

|               |                   |
| ------------- | ----------------- |
| Hypervisor    | KVM               |
| Orchestration | Apache CloudStack |

### Physical network

|                        |            |
| ---------------------- | ---------- |
| Architecture           | Spine-leaf |
| Network virtualization | VXLAN      |

### Where to go next

* For regions and zones: [Regions and availability zones](/docs-en/productos/servers/details/regions-and-availability-zones.md).
* For the availability commitment: [Service availability](/docs-en/productos/servers/details/service-availability.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/servers-2/details/technical-specs.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.