> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/smb/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/smb/gallagher-smb-solution/system-overview.md).
# System Architecture
Our security solution is built on a **cloud-based architecture**, hosted by Amazon Web Services (AWS). This means there’s no need for on-site servers, everything runs securely in the cloud, giving you flexibility and reducing infrastructure costs.
The following diagram shows the architecture for the Gallagher SMB solution. The system is a collection of hardware and software items, tightly integrated to provide a seamless intruder alarm monitoring system. The Gallagher Cloud server is hosted on AWS, Amazon web cloud servers.
The design allows integration with a range of external systems to provide the user with a single point of control for building security management.
### Secure communications
The diagram above illustrates the secure nature of the Controller's communications with the internet. The key takeaway is that the Controller is isolated from the internet – it accepts no inbound traffic.
All communications between the Controller and the Cloud server are encrypted using AES encryption.
If the Controller loses connection to the Cloud server, it will continually try to reconnect, in order that the system handles temporary network/internet outages. If the Controller is offline for a predefined period of time, an alarm is raised, notifying the appropriate users of the outage.
### Data storage
Customer data (site data) is replicated across multiple data centres in Sydney, Australia. Customer data is backed up nightly, and the backups replicated across the data centres.
All historical events are stored within their own event database.
---
# 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/smb/gallagher-smb-solution/system-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.
