> 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/system-requirements.md).

# System requirements

Review Devolutions Gateway system requirements, which vary depending on whether it pairs with Devolutions Server or Devolutions Cloud.

Before installing Devolutions Gateway, check your environment against the requirements for your setup, as hardware sizing, supported operating systems, and TLS/certificate requirements differ slightly depending on whether the gateway will pair with Devolutions Server or Devolutions Cloud.

To use Devolutions Gateway, your system must meet the following requirements.

### Hardware requirements

<table><thead><tr><th width="185">Implementation size (concurrent sessions)</th><th width="245" align="right">vCPUs</th><th width="245" align="right">RAM</th></tr></thead><tbody><tr><td>Minimal (1–5)</td><td align="right">2</td><td align="right">4 GB</td></tr><tr><td>Small (5–15)</td><td align="right">4</td><td align="right">8 GB</td></tr><tr><td>Medium (15–75)</td><td align="right">8</td><td align="right">16 GB</td></tr><tr><td>Large (more than 75)</td><td align="right">Deploy multiple Devolutions Gateway instances.</td><td align="right">Deploy multiple Devolutions Gateway instances.</td></tr></tbody></table>

{% hint style="info" %}
A Gigabit Ethernet controller is recommended for optimal performance.
{% endhint %}

### Software requirements

* Windows 10 (version 20H2, 21H1, and 21H2), or Windows 11 (version 21H2)
* Windows Server 2016, 2019, 2022, or 2025 with .NET Framework 4.8
* Ubuntu Linux 18.04, 20.4, 22.4, and later
* Red Hat Enterprise Linux (RHEL) 8 and later
* Rocky Linux 8 and later
* PowerShell 7 (required only for using the [Devolutions Gateway PowerShell module](https://www.powershellgallery.com/packages/DevolutionsGateway/2025.1.0) on Linux)
* **Devolutions Cloud only**: Devolutions Gateway must be able to reach Devolutions Cloud at the network level.

### Certificate requirements

Devolutions Gateway supports TLS 1.2 and TLS 1.3 as well as the following cipher suites:

* AES\_256\_GCM\_SHA384
* AES\_128\_GCM\_SHA256
* CHACHA20\_POLY1305\_SHA256
* ECDHE\_ECDSA\_AES\_256\_GCM\_SHA384
* ECDHE\_ECDSA\_AES\_128\_GCM\_SHA256
* ECDHE\_ECDSA\_CHACHA20\_POLY1305\_SHA256
* ECDHE\_RSA\_AES\_256\_GCM\_SHA384
* ECDHE\_RSA\_AES\_128\_GCM\_SHA256
* ECDHE\_RSA\_CHACHA20\_POLY1305\_SHA256

### Basic infrastructure (Devolutions Server)

For MSPs, one Devolutions Gateway can be deployed per customer site. All you need is to keep the Devolutions Gateway servers reachable by both Devolutions Server and Remote Desktop Manager. Devolutions Gateway only needs to accept inbound connections coming from them. No outbound connections to Devolutions Server and Remote Desktop Manager are required.

When installing Devolutions Gateway, it is essential to consider the location of the resources you need to access and the location of the users requiring access to those resources. Devolutions Gateway can be deployed on an internal or a remote network.

#### **Internal network**

Devolutions Gateway is installed on the same internal network as Devolutions Server, its SQL Server database, and the target hosts.

<figure><img src="https://762787125-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjzRy2HAXK8qgJafbcosL%2Fuploads%2F1PYocXRWbwQV63v6amr0%2FMARKETING_Gateway-internal-network-revised.png?alt=media&amp;token=9a4593a7-976e-4b60-88b6-fb1b87e6ad51" alt=""><figcaption></figcaption></figure>

#### **Remote network**

Devolutions Gateway is installed on a separate network — closer to the target hosts — while Devolutions Server and its SQL Server database remain on the internal network.

<figure><img src="https://762787125-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjzRy2HAXK8qgJafbcosL%2Fuploads%2FvhYD7Zeylswwc4cD0fqS%2FMARKETING_Gateway-remote-network-revised.png?alt=media&amp;token=c2c8f89a-2c50-4434-8369-3aa772c4f833" alt=""><figcaption></figcaption></figure>

In both cases, the same connections and default ports apply:

* The client browser connects to Devolutions Server over port **443** (default ports).
* Devolutions Server connects to Devolutions Gateway over port **7171** (default ports).
* Remote Desktop Manager connects directly to Devolutions Gateway over ports **7171/8181** (default ports) — this connection bypasses Devolutions Server entirely.
* Devolutions Gateway connects to the target remote host using the protocol's default port (for example, 3389 for RDP, 22 for SSH).

The communication between Devolutions Remote Desktop Manager / Devolutions Server and the gateway is encrypted to ensure secure data transfer. However, between the gateway and the target host, the connection will use the default protocol associated with the connection type, such as RDP or SSH. It is important to ensure that these protocols are properly secured. The default port for HTTP(s) communication with the gateway is **7171**, while the default port for TCP communication is **8181**. These ports should be open and not blocked by firewalls to allow proper communication.

The interaction between Remote Desktop Manager and Devolutions Gateway is direct and does not pass through Devolutions Server. Security is maintained through the use of a user token, which is encrypted and authenticated using a PEM file to verify that the token was generated by Devolutions Server. This ensures the integrity of the connection and protects against unauthorized access.

For optimal performance, the gateway should be installed as close as possible to the resources it accesses. Additionally, administrators should regularly monitor and update firewall rules to allow the required ports (7171 and 8181) and ensure secure configurations for the protocols in use. Proper handling of the PEM file is critical to maintaining a secure setup.


---

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