> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/command-centre/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/command-centre/command-centre-releases/release-history/supported-gallagher-command-centre-releases.md).
# Supported Gallagher Command Centre Releases
Explore the evolution of Gallagher’s industry-leading security platform through our comprehensive release history for versions 9.20 to 9.50. This site provides high-level insights into each version’s enhancements, maintenance updates, and critical bug fixes. Whether you're upgrading your system, troubleshooting, or planning future deployments, you'll find everything from controller firmware improvements and server-side performance optimisations to expanded third-party integrations and security enhancements.
| **Command Centre:** | **Status** | **First Full Release:** | **Current / Latest Version:** | **Release Type:** |
| ------------------- | ---------- | ----------------------- | ----------------------------- | --------------------- |
| v9.50 | Current | Jun 2026 | vEL9.50.2223 | Maintenance Release 2 |
| v9.40 | Supported | Nov 2025 | vEL9.40.3733 | Maintenance Release 4 |
| v9.30 | Supported | May 2025 | vEL9.30.4561 | Maintenance Release 6 |
| v9.20 | Supported | Oct 2024 | vEL9.20.4900 | Maintenance Release 8 |
The table below lists supported Command Centre versions and their bundled controller software by release date.
---
# 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 dynamically 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/command-centre/command-centre-releases/release-history/supported-gallagher-command-centre-releases.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 `build a script that syncs our docs to a CMS` 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.