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

# Getting started

Get started deploying Devolutions Gateway through Devolutions Cloud, Devolutions Server, or Linux, then configure rulesets and gateway farms.

This section covers deploying and connecting Devolutions Gateway, whether it's hosted through [Devolutions Cloud](/gateway/getting-started/devolutions-cloud.md) or [Devolutions Server](/gateway/getting-started/devolutions-server.md), or installed directly on [Linux](/gateway/getting-started/devolutions-gateway-configuration-on-linux.md) or in a [Docker container](/gateway/getting-started/devolutions-gateway-configuration-in-docker.md). Devolutions Gateway enables just-in-time, session-level connections without changing a system's global network configuration, offering a flexible and secure alternative to VPNs.

Getting started involves installing the Gateway component for your environment, then linking it to Remote Desktop Manager so sessions can be routed through it. From there, Gateway rulesets let you restrict and segment network access in [Devolutions Cloud](/gateway/getting-started/devolutions-cloud/gateway-ruleset-configuration-in-devolutions-cloud.md) or [Devolutions Server](/gateway/getting-started/devolutions-server/gateway-ruleset-configuration-in-devolutions-server.md), allowing or denying connections by IP, subnet, IP range, or domain, and enforcing access at the user, group, or vault level, without standing up a separate Gateway instance. For deployments that need to handle more session volume or avoid single points of failure, [Devolutions Gateway farms](/gateway/getting-started/devolutions-cloud/devolutions-gateway-farms.md) group multiple gateways together to distribute session load and maintain availability if one gateway goes down.


---

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