> 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/sensor-ratios.md).

# Sensor ratios

## **Ratio of Wildfire Sensors to Mesh Gateways**

**100 sensors to 1 Mesh Gateway**

For every 100 Wildfire Sensors deployed, use at least one Mesh Gateway or more, if necessary. This is dependent on Site topology which may or may not interfere with connectivity to Mesh Gateways.

## **Ratio of Wildfire Sensors to Border Gateways**

**No limit but must be in range:**

The Border Gateway does not have a limit on the number of Wildfire Sensors it can support. However, it can support sensors that are within range of the Border Gateway.

{% hint style="warning" %}
**Use of Mesh Gateways**

Do not deploy Wildfire Sensors without the use of Mesh Gateways.
{% endhint %}


---

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