> 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/cc-software/reference/command-centre-compatibility-matrix.md).

# Command Centre compatibility matrix

Check supported platforms, hardware, and upgrade paths for each Command Centre version.

### What is the Command Centre Compatibility Matrix?

The **Command Centre Compatibility Matrix** is the resource for rapidly checking what a given Command Centre version supports, and for finding **upgrade paths** when bringing older sites up to current versions.

For each Command Centre version, the matrix covers:

* Upgrade paths
* Release dates for all versions
* Supported operating systems
* Supported hardware
* Supported .NET versions
* SALTO versions
* Third-party hardware support
* Default licence options
* PIV-approved versions

The matrix is updated with each new Command Centre release.

📄 [**CC Compatibility Matrix (XLSX)**](https://github.com/GGLSecDev/gitbook-spaces/tree/main/tech-support/products/.gitbook/assets/SECHUB-CCS-VER-compatibility-matrix.xlsx). This matrix is updated with each Command Centre release; for the current version check the live source: [media.gallagher.com](https://media.gallagher.com/asset/97e522a3-f16b-4e3d-ba13-b8e8248f1028/CC-Compatibility-Matrix.xlsx)

{% hint style="info" %}
**When planning a multi-version upgrade**, plan the SQL version path as deliberately as the Command Centre path, and always check the matrix for which SQL versions a given Command Centre version supports.
{% endhint %}

***

🔗 **Related**

* [Command Centre - Release Dates](/knowledge-hub/products/cc-software/reference/command-centre-release-dates.md). The release cadence and support lifecycle.
* [Command Centre - Feature Introduction](/knowledge-hub/products/cc-software/reference/command-centre-feature-introduction.md). Which version introduced a given feature.


---

# 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/cc-software/reference/command-centre-compatibility-matrix.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.