Is the Gallagher Controller 6000 end of life?

Gallagher lists the Controller 6000 as superseded by the Controller 7000, but the page we read gives no end-of-sale or end-of-support date. A working C6000 does not need replacing today. Ask Gallagher or your installer about spare parts and support before planning a swap.

What Command Centre version do I need for the Controller 7000?

Gallagher states the Controller 7000 requires Command Centre v9.0 or later. If your server runs an 8.x release, the software has to be upgraded before new C7000 controllers can be added. Check the version on your Command Centre server first.

Does Command Centre have an API?

Yes. Gallagher publishes a REST API reference and an OpenAPI specification covering events, alarms, cardholders and door status and overrides. Using it requires a Technology Partner Agreement for the developer and per-feature REST licences, such as RESTEvents and RESTStatus, on the customer's server.

Can I use other brands of controller with Command Centre?

Command Centre runs Gallagher's own controllers, such as the Controller 7000 and Controller 6000. It is not a Mercury-based platform. That keeps hardware refreshes within Gallagher's range, so a move to another software platform usually also means new controllers.

Systems / Gallagher Command Centre

Gallagher Command Centre: versions, controllers, end of life and upgrade options

Gallagher SecurityGateStride: Not yet scheduledReviewed October 2026

By Tom Jin

Command Centre is Gallagher's on-premise security management software. It runs on Windows Server and manages Gallagher controllers, readers, alarms and cardholders from one server. Gallagher sells it to mid-market and enterprise organizations and to government, and the base licence includes 16 doors, so a smaller single-site office can run it without buying extra door licences up front.

Command Centre is a closed-hardware system in the sense that it runs Gallagher's own controllers, not third-party Mercury boards. In exchange, Gallagher publishes unusually detailed integration documentation: a public REST API reference, an OpenAPI specification and a cloud gateway guide. For an office manager, that means two things. Hardware choices are made within the Gallagher range, and connecting other software is well documented but licensed feature by feature.

How to recognise Gallagher Command Centre

Command Centre is easy to recognize from its software name on the server and workstation. In the comms room, Gallagher controllers carry Gallagher branding and product codes. The two current controller families are the Controller 7000 (product code C400100) and the older Controller 6000 (C300100). Gallagher readers on the doors are another clue, but check the model on the label rather than relying on appearance.

The management software is called Command Centre, running on a Windows Server (2016, 2019 or 2022 per Gallagher).
Controllers are Gallagher-branded: Controller 7000 (C400100) on newer sites, Controller 6000 (C300100) on older ones.
Controller 6000 variants include Standard, Enhanced and 2-Door; they connect readers over Gallagher's HBUS or GBUS RS-485 buses.
Gallagher T-series readers are common on these sites; we did not verify the reader model list in this review.

Still not sure? Follow how to identify your access control system.

Versions and editions

Name	Details	Status	Source
Command Centre (C201311)	Windows Server 2016/2019/2022. Base licence includes 16 doors. Gallagher's REST documentation lists API changes through v9.70, the latest documented release.	current	source
Command Centre v9.0 and later	Required for the Controller 7000.	current	source
Command Centre 8.60 and later	Adds the Cloud API Gateway for remote API access.	current	source
Older releases (before 9.x)	Gallagher's end-of-support dates for older Command Centre releases were not confirmed in this review.	unconfirmed

Hardware

Name	Details	Status	Source
Controller 7000 (C400100)	Latest controller generation. Requires Command Centre v9.0 or later. Has a native controller API that third-party systems can use without the server. Variants include the C7000 Standard; the full variant list was not confirmed.	current	source
Controller 6000 (C300100)	Standard, Enhanced and 2-Door variants. Up to 10 doors. HBUS/GBUS RS-485. Has a Controller API. Superseded by the Controller 7000; Gallagher does not state a date.	legacy	source
T-series readers (T10, T11, T12, T15, T20, T21, T30)	Model list not verified in this review.	unconfirmed

What is ending, and when

Gallagher lists the Controller 6000 as superseded by the Controller 7000 but does not give an end-of-sale or end-of-support date on the page we read. Superseded is not the same as unsupported: a working C6000 site is not forced to change today. We found no dated end-of-life notice for Command Centre itself.

The practical dependency to watch is software version. The Controller 7000 needs Command Centre v9.0 or later, so a site on an 8.x release has to upgrade the server software before it can add new controllers. If you are planning an expansion or a controller swap, confirm your Command Centre version first.

See every dated notice in the end-of-life tracker.

What offices commonly miss

Exits are usually free: people push a bar or trip a request-to-exit sensor. The system logs the door opening but not who left, so it cannot say who is still inside unless exits are badged.
Integration is licensed per feature. Gallagher's REST API needs licences such as RESTEvents, RESTCreateEvents, RESTStatus and cardholder licences on the customer's server, and the integrator must sign a Technology Partner Agreement first.
Hardware is Gallagher-only. You cannot drop in Mercury or other third-party controllers, so hardware refreshes stay within Gallagher's range.
New controllers need new software. The Controller 7000 requires Command Centre v9.0 or later.

Integration options

Gallagher publishes its Command Centre REST API documentation openly, including an OpenAPI specification. The API covers events and alarms (with a long-poll updates feed), cardholders, and the status and overrides of doors, zones, inputs, outputs and macros. Since Command Centre 8.60 a Cloud API Gateway can expose the API remotely. The Controller 7000 and Controller 6000 also have a controller-level API.

Reading the documentation is free, but using it is not. A Technology Partner Agreement is required to obtain integration licences and portal access, and the customer's server needs feature licences such as RESTEvents and RESTStatus (available since v8.00). The name of the licence that allows door overrides was not confirmed. Budget for these licences in any integration project.

Upgrade paths

Keep Command Centre and add features as software

If the controllers and readers work, keep them. Features such as phone unlock or exit tracking can be added by software that connects through Gallagher's REST API, once the partner agreement and the customer-side REST licences are in place.

Upgrade software, then controllers

Move the server to a current Command Centre release (v9.0 or later), then replace Controller 6000 units with Controller 7000 units as they need attention. Doors, wiring and cardholders typically stay.

Full replacement

A move to another platform means new controllers, because Gallagher hardware runs only on Command Centre. Price that carefully against a software and controller refresh before deciding.

Compare the routes over three years in the savings calculator.

GateStride and Gallagher Command Centre

Not yet scheduled GateStride has not scheduled a Gallagher Command Centre integration. It is not on our roadmap yet, and we do not support Command Centre today. GateStride is in early access and currently works with Kantech EntraPass. If your office runs Command Centre, tell us your version and door count. Demand decides what we build next, and we will only call an integration Verified after testing it ourselves on a live system.

Full compatibility list · Tell us you run Gallagher Command Centre

Questions about Gallagher Command Centre

Is the Gallagher Controller 6000 end of life?: Gallagher lists the Controller 6000 as superseded by the Controller 7000, but the page we read gives no end-of-sale or end-of-support date. A working C6000 does not need replacing today. Ask Gallagher or your installer about spare parts and support before planning a swap.
What Command Centre version do I need for the Controller 7000?: Gallagher states the Controller 7000 requires Command Centre v9.0 or later. If your server runs an 8.x release, the software has to be upgraded before new C7000 controllers can be added. Check the version on your Command Centre server first.
Does Command Centre have an API?: Yes. Gallagher publishes a REST API reference and an OpenAPI specification covering events, alarms, cardholders and door status and overrides. Using it requires a Technology Partner Agreement for the developer and per-feature REST licences, such as RESTEvents and RESTStatus, on the customer's server.
Can I use other brands of controller with Command Centre?: Command Centre runs Gallagher's own controllers, such as the Controller 7000 and Controller 6000. It is not a Mercury-based platform. That keeps hardware refreshes within Gallagher's range, so a move to another software platform usually also means new controllers.

Related systems: Genetec Synergis · AMAG Symmetry · Hirsch Velocity

Sources

Last reviewed October 2026. Gallagher Command Centre and other product names are trademarks of their respective owners. GateStride is independent and not affiliated with, endorsed by or a dealer for any manufacturer.