There’s an old Tecom Challenger controller in the comms room. It’s been running the site’s intrusion detection for years, and depending on how the site has grown, it may also be handling door access, expansion hardware, and a fair amount of the building’s day-to-day security administration. Someone has raised the question of whether it’s time to replace it.
On a residential alarm, that question has a fairly short answer. On a Challenger site, it doesn’t — because the obvious next question, “what replaces the box?”, is the wrong one to start with. The right one is: what’s actually connected to it, and which of those components does Aritech, the current manufacturer, still document as compatible with the current platform? The Challenger platform itself hasn’t gone anywhere — Aritech has formally ended support for the older V8 generation and superseded Challenger10 with ChallengerPlus for new orders, but older installations still need to be judged by the specific controller and the ecosystem actually connected to it, not by age alone.
What Does “Aging Out” Actually Mean for Challenger?
It helps to separate this by generation, because “Challenger” doesn’t mean one status.
Challenger10 (TS1016) has an explicit manufacturer statement behind it. Aritech’s own announcement states that “the Challenger10 control panel (part number TS1016) has been superseded by the ChallengerPlus control panel (part number TS-CHPLUS),” and that all new Challenger10 orders are now fulfilled with ChallengerPlus instead. That’s a real, documented supersession — but it’s specifically about what’s sold as new. It isn’t a statement that installed Challenger10 units have reached end of life or lost support.
Challenger V8 has reached a different, more formal milestone. Aritech’s own discontinued-products notice states that, effective 1 October 2024, “Tecom are discontinuing the Challenger V8 product,” listing the TS0816 Challenger V8 control panel as End of Life, with support “no longer available via Aritech or Tecom distributors.” That notice recommends transitioning V8 systems to either ChallengerPlus or the Discovery control panel — Aritech’s other current platform.
That’s worth sitting with, because it’s a genuinely different status from Challenger10’s: superseded for new orders is not the same as formally end of life. Both are real, both are official, and they point to different next steps — which is exactly why lumping “old Challenger” together as one status is the wrong starting point.
The takeaway: the Challenger family hasn’t aged out as a platform — ChallengerPlus and Discovery are both current, actively supported products. What’s aged out is specific to the controller. A V8 site has a formal end-of-life notice and two named successor paths to choose between. A Challenger10 site has a documented direct successor without a declared end-of-life status. Either way, the exact migration decision depends on which controller is actually installed.
ChallengerPlus (TS-CHPLUS) is the current Challenger control panel, actively maintained, with the most recent compatibility documentation dated May 2026 — it’s the direct successor named for Challenger10, and one of the two successor paths named for V8.
Why Replacing a Challenger Controller Is Not Just a Panel Swap
A Challenger controller is typically the hub for more than intrusion detection alone. Depending on the site, it can also be managing door access, input and output expansion, and administrative software — not just alarm zones.
The connected hardware typically includes: DGPs (Data Gathering Panels — expansion units that add extra zone inputs and outputs beyond what the controller handles on its own), RAS units (Remote Arming Stations — interfaces used for functions such as arming and disarming), alongside the site’s readers and door access hardware, and NACs (Network Access Controllers — the door controllers managing electric locks and access permissions). On top of that sits management software handling users, schedules and reporting across the site.
That’s why replacing the controller on a Challenger site involves a wider dependency map than swapping a standalone alarm panel — the same platform may sit behind access control, expansion hardware and site-management functions, not just alarm zones. Deciding what to do next without first mapping what’s actually connected to it means making compatibility decisions blind. Sites using integrated security and access control solutions tend to have exactly this kind of layered dependency, which is exactly why the inventory step below matters before any scope gets defined.
What Aritech Actually Documents as Compatible
This is where the article can move past a vague “legacy compatible” claim. Aritech doesn’t just say ChallengerPlus is backwards compatible in general terms — its current compatibility matrix, issued May 2026, names specific older hardware by model number.
A few examples pulled directly from that matrix:
That last row matters as much as the others — and it’s worth being direct about it: some components have their own individual end-of-life notices layered on top of the broader V8 or Challenger10 status, as the door-controller row above shows. The matrix doesn’t treat compatibility as a blanket property of “an old Challenger site” — it documents specific products, sometimes with specific conditions or separate lifecycle notices attached. The formula worth holding onto: Aritech documents specific compatible legacy products. Compatibility is item-by-item, not a blanket property of an old Challenger installation.
Migration Doesn’t Mean Everything Stays
Backwards compatibility reduces how much of a site may need to change — it doesn’t remove the need to actually check what’s installed against what’s currently documented.
A few things worth being precise about, because it’s easy to over-read the compatibility evidence:
The matrix shows Challenger10 and ChallengerPlus supporting an identical 48-bit card data length. That’s a genuine continuity signal, but it isn’t proof that every installed reader, credential type or user database transfers unchanged — it confirms a technical format match, not a guaranteed migration of every card on site.
Door hardware itself — locks, strikes, the physical devices at each door — sits outside the compatibility matrix altogether. Aritech’s documentation covers controllers and expansion hardware; it doesn’t establish blanket compatibility for site-specific field devices, so those still need separate assessment.
And as the IP LAN Adaptor example above shows, “listed in the matrix” doesn’t always mean “fully supported” — some items carry limited or qualified support notes that only make sense once you’re looking at the exact model and firmware version installed on site.
None of this undoes the value of the compatibility evidence — it’s genuinely strong for the items it covers. It just means the matrix is a starting point for an audit, not a substitute for one.
On the controller itself, Aritech’s own support documentation is direct about what the upgrade path actually is. In an article titled “Upgrade Challenger10 to ChallengerPlus,” Aritech states that “existing Challenger10 customers can protect their hardware investment and upgrade to a ChallengerPlus,” with the upgrade carried out as a firmware process through Aritech’s CTPlus software — and the same documentation notes the reverse is also supported, letting a panel run existing Challenger10 firmware where that’s preferred. That’s a specific, sourced answer to whether an existing Challenger10 controller can become a ChallengerPlus — not an assumption extended from the peripheral compatibility evidence.
Before You Migrate, Inventory the Site
Given how conditional the compatibility picture is, the practical starting point is a straightforward inventory — not opening equipment or attempting any firmware work, just recording what’s actually there:
- The exact controller model and current firmware version.
- DGP models in use, and how many.
- RAS/keypad models at each entry point.
- NAC or door-controller models, and how many doors they manage.
- Reader models where known.
- Any communication modules fitted.
- The management software currently in use.
- Any site-specific integrations (CCTV, lifts, or similar).
That list is what makes the compatibility matrix actually usable — checking it against a specific, known inventory rather than a general sense of “the system is old.”
Service, Component Upgrade, Migration or Redesign?
Once the site is properly mapped, most situations fall into one of four categories.
Service applies when the controller and platform stay as they are, and a specific, identifiable component has failed and needs repair — a fault on a single DGP or reader, for instance, rather than anything to do with the wider architecture. This is the least disruptive outcome and doesn’t require touching the compatibility matrix at all, because nothing is changing at the platform level.
Component upgrade covers a narrower change — a communications module, a software version, or a specific peripheral — without touching the controller itself. This sits between straightforward service and a full migration, and is worth considering whenever the inventory turns up one clearly outdated or unsupported item rather than a pattern across the whole site.
In-family migration covers moving an older Challenger installation toward a current Tecom controller while retaining only the components confirmed compatible for that path. For Challenger10, Aritech explicitly documents the move to ChallengerPlus, including the firmware-based upgrade process described above. For V8, Aritech’s own end-of-life notice points customers toward either ChallengerPlus or Discovery — which path fits depends on the installed ecosystem and site requirements, not a single default route.
Redesign is the right conversation when the site’s requirements, integrations, or unsupported legacy components make an in-family migration unsuitable after a proper assessment — not a default outcome, and not something to assume just because the installation is old.
FAQ
Is Tecom Challenger discontinued?
Not as a platform. The TS0816 Challenger V8 control panel is formally End of Life, effective October 2024, with Aritech support no longer available — V8 sites are pointed toward ChallengerPlus or Discovery. Challenger10 is a different case: it has been superseded by ChallengerPlus for new orders, but that announcement doesn’t declare installed Challenger10 units end of life. Current Tecom platforms remain available and actively supported, including ChallengerPlus and Discovery.
What replaced Challenger10?
ChallengerPlus. Aritech’s own announcement states Challenger10 orders are now fulfilled with ChallengerPlus, and its current documentation describes ChallengerPlus as built on the foundations of Challenger10 and Challenger V8.
Can Challenger10 be upgraded to ChallengerPlus without replacing everything?
Potentially, significant parts of the existing ecosystem may remain, because Aritech documents backwards compatibility with specific Challenger10 and V8-era peripherals, and its own support documentation describes upgrading an existing Challenger10 controller to ChallengerPlus as a firmware-based process. But the site still needs to be checked against the current compatibility matrix component by component — compatibility isn’t automatic for every connected device.
Which old Challenger hardware can still be compatible with ChallengerPlus?
Aritech’s current matrix names several examples directly: specific V8-era DGPs, the Challenger10 DGP, several door and lift controller models, and the Network Access Controller. Exactly which of these apply depends on the models actually installed on site, so they still need checking against the current documentation rather than assumed.
Does an old Challenger panel need the whole site replaced?
Not automatically. The controller, any confirmed-compatible peripherals, and any site-specific hardware outside the compatibility matrix are three different questions, and they don’t all move together.
The most useful first step on an older Challenger site usually isn’t requesting a quote for a full replacement — it’s inventorying the installed controller, access-control hardware, expansion devices and software, and checking that inventory against Aritech’s current compatibility matrix. SIPKO can assess the site and map what can reasonably carry forward before a migration scope is defined, through our integrated security and access control solutions.
