From 5dffde92fe9ca2e8be0ec9a7c1ed1d252483585d Mon Sep 17 00:00:00 2001
From: Dmitry Meyer <me@undef.im>
Date: Thu, 13 Nov 2025 11:58:50 +0000
Subject: [PATCH 1/2] [Docs] Describe some gateway options on Concepts/Gateways
 page

---
 docs/docs/concepts/gateways.md | 18 +++++++++++++++++-
 1 file changed, 17 insertions(+), 1 deletion(-)

diff --git a/docs/docs/concepts/gateways.md b/docs/docs/concepts/gateways.md
index 500d0d86cf..54886c2526 100644
--- a/docs/docs/concepts/gateways.md
+++ b/docs/docs/concepts/gateways.md
@@ -11,7 +11,7 @@ provide an HTTPS endpoint mapped to your domain, handle auto-scaling and rate li
 First, define a gateway configuration as a YAML file in your project folder.
 The filename must end with `.dstack.yml` (e.g. `.dstack.yml` or `gateway.dstack.yml` are both acceptable).
 
-<div editor-title="gateway.dstack.yml"> 
+<div editor-title="gateway.dstack.yml">
 
 ```yaml
 type: gateway
@@ -47,6 +47,22 @@ Provisioning...
 
 </div>
 
+## Configuration options
+
+### Backend
+
+Gateways are currently supported in `aws`, `azure`, `gcp`, and `kubernetes` backends, but it does not mean that services are limited
+to these backends, quite contrary, you can use a gateway deployed in any supported backend with a service deployed in any backend.
+
+??? info "Kubernetes"
+    Gateways in `kubernetes` backend require an external load balancer. Managed Kubernetes solutions usually include a load balancer.
+    For self-hosted Kubernetes, you must provide a load balancer by yourself.
+
+### Public IP
+
+If you don't need/want a public IP for the gateway, you can set the `public_ip` to `false` (the default value is `true`), making the gateway private.
+Private gateways are currently supported in `aws` and `gcp` backends.
+
 !!! info "Reference"
     For all gateway configuration options, refer to the [reference](../reference/dstack.yml/gateway.md).
 

From f61e1ff8057ecc660f88a8b73801d685ceee4eee Mon Sep 17 00:00:00 2001
From: peterschmidt85 <andrey.cheptsov@gmail.com>
Date: Thu, 13 Nov 2025 17:14:33 +0100
Subject: [PATCH 2/2] [Docs] Gateway docs

Minor edits
---
 docs/docs/concepts/gateways.md | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/docs/docs/concepts/gateways.md b/docs/docs/concepts/gateways.md
index 54886c2526..1435926810 100644
--- a/docs/docs/concepts/gateways.md
+++ b/docs/docs/concepts/gateways.md
@@ -51,8 +51,7 @@ Provisioning...
 
 ### Backend
 
-Gateways are currently supported in `aws`, `azure`, `gcp`, and `kubernetes` backends, but it does not mean that services are limited
-to these backends, quite contrary, you can use a gateway deployed in any supported backend with a service deployed in any backend.
+You can create gateways with the `aws`, `azure`, `gcp`, or `kubernetes` backends, but that does not limit where services run. A gateway can use one backend while services run on any other backend supported by dstack, including backends where gateways themselves cannot be created.
 
 ??? info "Kubernetes"
     Gateways in `kubernetes` backend require an external load balancer. Managed Kubernetes solutions usually include a load balancer.