> 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/silvanet-deployment/overview.md). # Deploy Silvanet Learn how to deploy Silvanet Gateways and Sensors at their planned locations in a Site. ## In this section


Deployment guidelines	Review these guidelines before starting the deployment of Silvanet Gateways and Sensors.	card-preparation-guidelines.jpg
Deployment preparation	Ensure you have the right tools to deploy Silvanet Gateways and Wildfire Sensors.	card-deployment-tools.jpg
Deploy Border Gateways (Gen 2/3)	Deploy the Silvanet Border Gateway to ensure it reliably communicates with the Mesh Network and Silvanet Cloud.	card-deploy-border-gateways.jpg
Deploy Mesh Gateways (Gen 2/3)	Deploy Mesh Gateways to allow extensive deployments of Wildfire Sensors using the Silvanet Mesh Network.	card-gen3-mg.jpg
Deploy Wildfire Sensors	Install Wildfire Sensors using tree nails or garden wire, then let them calibrate for 14 days before they they are ready to detect fires.	card-deploy-wildfire-sensors.jpg
Relocate a Silvanet Sensor or Gateway	When a Silvanet device is relocated, update the longitude and latitude settings in the Site Management app.	card-silvanet-device-relocation.jpg

--- # 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/silvanet-deployment/overview.md?ask=&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.