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

# Primeros pasos

Esta sección abarca la implementación y la conexión de Devolutions Gateway, tanto si está alojado a través de [Devolutions Cloud](/gateway/es/getting-started/devolutions-cloud.md) o [Devolutions Server](/gateway/es/getting-started/devolutions-server.md), como si está instalado directamente en [Linux](/gateway/es/getting-started/devolutions-gateway-configuration-on-linux.md). Devolutions Gateway permite conexiones justo a tiempo a nivel de sesión sin cambiar la configuración de red global de un sistema, lo que ofrece una alternativa flexible y segura a las VPN.

Los primeros pasos consisten en instalar el componente Gateway para su entorno y, a continuación, vincularlo a Remote Desktop Manager para que las sesiones puedan enrutarse a través de él. A partir de ahí, los conjuntos de reglas de Gateway le permiten restringir y segmentar el acceso a la red en [Devolutions Cloud](/gateway/es/getting-started/devolutions-cloud/gateway-ruleset-configuration-in-devolutions-cloud.md) o [Devolutions Server](/gateway/es/getting-started/devolutions-server/gateway-ruleset-configuration-in-devolutions-server.md), permitiendo o denegando conexiones por IP, subred, rango de IP o dominio, y aplicando el acceso a nivel de usuario, grupo o bóveda, sin necesidad de desplegar una instancia de Gateway independiente. Para las implementaciones que necesitan gestionar un mayor volumen de sesiones o evitar puntos únicos de fallo, las [granjas de Devolutions Gateway](/gateway/es/getting-started/devolutions-cloud/devolutions-gateway-farms.md) agrupan varios gateways para distribuir la carga de sesiones y mantener la disponibilidad si uno de los gateways deja de funcionar.


---

# 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.devolutions.net/gateway/es/getting-started.md?ask=<question>&goal=<endgoal>
```

`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.