> 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-release-dates.md).
# Command Centre release dates
Review Command Centre release dates, platform support, and lifecycle milestones.
#### How often does Command Centre release?
Command Centre releases new versions twice a year. Support is measured from the date of **Full Release**.
***
#### How long is each version supported?
| Period after Full Release | Support provided |
| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **0–24 months** | **Full Technical and Software Support.** Gallagher provides version Maintenance Releases for issues and vulnerabilities, and development teams assist with resolving specific site issues. |
| **24–36 months** | **Full Technical Support only.** Gallagher provides assistance plus existing off-the-shelf utilities and patches (no new Maintenance Releases). |
| **36 months onwards** | **Best-endeavours** technical support. Gallagher reserves the right to charge for this service. |
#### **What support types are available?**
* **Software Support:** resolution of software anomalies, which may include new software fixes.
* **Technical Support:** verbal / written support for install, configuration, and operational use, using existing knowledge and anomaly resolutions. It does **not** include new anomaly resolutions (software fixes).
**Operating-platform support windows** (Gallagher tracks Microsoft's lifecycle):
| Platform | Support starts | Support ends (first CC version released with support removed) | Notification |
| -------------------- | -------------------------- | ------------------------------------------------------------- | ------------------------ |
| Windows Server | Within 6 months of release | **3 years** after Microsoft's mainstream support end date | 12 months before removal |
| Microsoft SQL Server | Within 6 months of release | **2 years** after Microsoft's mainstream support end date | 12 months before removal |
Gallagher may remove SQL Server support earlier if an older version limits system performance. Support ideally starts within 6 months of a platform's release, by best endeavours, subject to release timings.
**Policy points:**
* The **cost of operating-platform upgrades** required to support a new Command Centre version is the **customer's responsibility**.
* Gallagher chooses the supported operating platform(s) for each version. See that version's release notes for the definitive list.
* Alternative-language OS variants (and their later versions) count as a new operating platform per local variant.
* Command Centre **is supported on Virtual Server environments**. If fault resolution is inconclusive, Gallagher may request replication on non-virtual hardware.
* Gallagher may **recommend a site upgrade** (Command Centre and/or operating platform, within full support) to resolve performance anomalies or close cyber-security risk.
### Platform support changes (Microsoft) - v9.50
Command Centre **v9.50 (2026 release) removes support** for platforms reaching Microsoft's end of extended support, and **drops all 32-bit operating systems**:
| Platform | Microsoft Extended-Support end |
| ----------------------- | ------------------------------ |
| Windows 10 Professional | 14 October 2025 |
| SQL Server 2016 | 14 July 2026 |
| SQL Server 2017 | 12 October 2027 |
| Windows Server 2016 | 12 January 2027 |
Plan upgrades to supported Windows Server / SQL Server / 64-bit OS before moving to v9.50.
***
## Command Centre version release history
Release dates, software-support end dates, and full-technical-support end dates for every Command Centre version. The most recent supported versions are at the top. Dates are current as at the source export; check the Compatibility Matrix for the live position.
| Version | Release Date | Software Support End Date | Full Tech Support End Date |
|---|
| v9.40 | November 2025 | November 2027 | November 2028 |
| v9.30 | May 2025 | May 2027 | May 2028 |
| v9.20 | October 2024 | October 2026 | October 2027 |
| v9.10 | May 2024 | May 2026 | May 2027 |
| v9.00 | November 2023 | November 2025 | November 2026 |
| v8.90 | May 2023 | Out of Support | May 2026 |
| v8.80 | October 2022 | Out of Support | Out of Support |
| v8.70 | May 2022 | Out of Support | Out of Support |
| v8.60 | November 2021 | Out of Support | Out of Support |
| v8.50 | May 2021 | Out of Support | Out of Support |
| v8.40 | Nov 2020 | Out of Support | Out of Support |
| v8.30 | June 2020 | Out of Support | Out of Support |
| v8.20 | December 2019 | Out of Support | Out of Support |
| v8.12 | May 2019 | Out of Support | Out of Support |
| v8.10 | May 2019 | Out of Support | Out of Support |
| v8.00 | October 2018 | Out of Support | Out of Support |
| v7.90 | April 2018 | Out of Support | Out of Support |
| v7.80 | November 2018 | Out of Support | Out of Support |
| v7.70 | April 2017 | Out of Support | Out of Support |
| v7.60 | October 2017 | Out of Support | Out of Support |
| v7.50 | April 2016 | Out of Support | Out of Support |
| v7.40 | October 2015 | Out of Support | Out of Support |
| v7.30 | February 2015 | Out of Support | Out of Support |
| v7.21 | September 2014 | Out of Support | Out of Support |
| v7.20 | May 2014 | Out of Support | Out of Support |
| v7.10 | March 2013 | Out of Support | Out of Support |
| v7.05 | August 2012 | Out of Support | Out of Support |
| v7.02 | March 2012 | Out of Support | Out of Support |
| v7.01 | December 2011 | Out of Support | Out of Support |
| v7.00 | 2011 | Out of Support | Out of Support |
| v6.10 | November 2010 | Out of Support | Out of Support |
| v6.02 | May 2010 | Out of Support | Out of Support |
| v6.01 | October 2009 | Out of Support | Out of Support |
| v6.00 (GGL only) | March 2009 | Out of Support | Out of Support |
| v5.21 | October 2008 | Out of Support | Out of Support |
| v5.20 | April 2008 | Out of Support | Out of Support |
| v5.10 | July 2007 | Out of Support | Out of Support |
| v5.01 | July 2006 | Out of Support | Out of Support |
| v4.20 | October 2005 | Out of Support | Out of Support |
| v4.10 | September 2004 | Out of Support | Out of Support |
| v4.02 | October 2003 | Out of Support | Out of Support |
| v3.00 | December 2002 | Out of Support | Out of Support |
| v2.10 | October 2002 | Out of Support | Out of Support |
| v1.22 | March 2002 | Out of Support | Out of Support |
| v1.20 | October 2001 | Out of Support | Out of Support |
| v1.02 | April 2001 | Out of Support | Out of Support |
> **Note:** the source table lists v7.80 (November 2018) below v7.90 (April 2018), and v7.60 (October 2017) below v7.70 (April 2017). Reproduced as published; treat the Compatibility Matrix as authoritative if the exact early-version dates matter.
***
🔗 **Related**
* [Command Centre - Compatibility Matrix](/knowledge-hub/products/cc-software/reference/command-centre-compatibility-matrix.md). Per-version OS / hardware / SQL / upgrade-path detail.
* [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-release-dates.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.