> For the complete documentation index, see [llms.txt](https://docs.dryad.app/dryad-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dryad.app/dryad-documentation/site-planning/planning-guidelines/gateway-ratios.md).

# Gateway ratios

The amount of Mesh Gateways supported by Border Gateways is variable but should not exceed on Border Gateway for every 20 Mesh Gateways.

For every **one Border Gateway** deployed, up to **20 Mesh Gateways** can be deployed, depending on the Site's topology. However, as Mesh Gateways act as repeaters, any number of Mesh Gateways can be deployed on a Site.

Ensure each Mesh Gateway can communicate with at least two other Mesh Gateways. This ensures a reliable Mesh Network in the forest.

{% hint style="info" %}
Additional Border Gateways can be deployed as a backup for the Mesh Network.
{% endhint %}

In the following figure, one Border Gateway (plus a backup Border Gateway) receives communication from 20 Mesh Gateways. Note the connectivity paths between Mesh Gateways. With a few exceptions, each Mesh Gateway connects with at least two other Mesh Gateways.

<figure><img src="https://2403147378-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKqvtUjx9C2FEFg7nicAx%2Fuploads%2FgBSjaWOEHWs81CDsVvmd%2Fgateway-ratios.png?alt=media&amp;token=600fcb80-1ebe-454a-9061-77930aa49eab" alt="" width="375"><figcaption><p>Ratio of Border Gateways to Mesh Gateways</p></figcaption></figure>

When using the [Planning tool](/dryad-documentation/site-planning/coverage-estimation.md), the **Connectivity tool** helps to ensure Mesh Gateways have multiple paths to the Border Gateway.

<figure><img src="https://2403147378-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKqvtUjx9C2FEFg7nicAx%2Fuploads%2Fw6g4z7qEFA4GTmEYjCxF%2Fpt-3rd-mesh-gateway.png?alt=media&amp;token=da5806c5-df13-4734-b415-f69df867263c" alt="" width="563"><figcaption><p>Mesh Gateway deployment plan using the Planning tool.</p></figcaption></figure>


---

# 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.dryad.app/dryad-documentation/site-planning/planning-guidelines/gateway-ratios.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.