> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/gateway/es/readme/system-requirements.md).

# Requisitos del sistema

Consulte los requisitos del sistema de Devolutions Gateway, que varían en función de si se empareja con Devolutions Server o con Devolutions Cloud.

Antes de instalar Devolutions Gateway, compruebe si su entorno cumple los requisitos de su configuración, ya que el dimensionamiento del hardware, los sistemas operativos compatibles y los requisitos de TLS/certificados difieren ligeramente según si el gateway se empareja con Devolutions Server o con Devolutions Cloud. [Requisitos del sistema para Devolutions Server](/gateway/es/readme/system-requirements/system-requirements-for-devolutions-server.md) abarca lo necesario para los gateways desplegados junto a una instancia de Devolutions Server, incluidas las indicaciones para los MSP que ejecutan un gateway por cada sitio de cliente y las consideraciones sobre la ubicación en la red. [Requisitos del sistema para Devolutions Cloud](/gateway/es/readme/system-requirements/system-requirements-for-devolutions-cloud.md) abarca los requisitos equivalentes para los gateways que se conectan a un espacio de trabajo de Devolutions Cloud, junto con la accesibilidad de red que requiere específicamente.


---

# 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.devolutions.net/gateway/es/readme/system-requirements.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.