> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/products/integrations/video-management-systems/milestone/milestone-set-up-with-multiple-milestone-servers-on-remote-sites.md).

# Set up multiple Milestone servers at remote sites

Plan a multi-site Milestone deployment that sends camera events to a central Command Centre.

Scenario: **100 or more sub-sites**, each with its own Milestone server, all feeding one central Command Centre that collects camera event data.

* **Performance** depends on total camera count, deployment architecture (federated versus singular), and server resources. Each camera behaves like an "input"; load is driven by event volume per camera and the number of FMF/FTCAPI connections. **Gallagher suggests not receiving motion-detection events**, and instead creating specific alarm events from the cameras, to cut event volume.
* **Middleware recommendation:** prefer **multiple Milestone systems** connected to Gallagher over one large consolidated system. This distributes load (multiple FMF/FTCAPI connections versus one) and improves fault tolerance. There is **no known limit** on the number of Milestone systems.


---

# 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://help.security.gallagher.com/knowledge-hub/products/integrations/video-management-systems/milestone/milestone-set-up-with-multiple-milestone-servers-on-remote-sites.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.