Is Doors.NET 4 still supported?

No. Keri ended support for Doors.NET 4.x and all earlier releases, through 4.9.0, on 15 September 2026. Keri says it no longer provides technical support, bug fixes or diagnostics for those versions and will require an upgrade first. Its named options are Doors.NET 5.2.0 or later, or a move to the Borealis cloud platform.

Will my PXL-500 controllers work with Doors.NET 6?

No. Doors.NET 6.0, released 13 August 2025, ended support for PXL and Entraguard controllers, and v5.4.0.8 is the last version that runs them. Your options are to stay on a supported 5.x release, replace the PXL boards with NXT-MSC controllers, or move to Borealis, which Keri says still supports PXL-500.

I still run Doors32. What now?

Doors32 was discontinued in 2020, and Keri's Doors32-to-Doors.NET conversion service ended on 1 November 2025. Keri now points Doors32 sites to Borealis. Depending on your controllers, a replacement system may also be worth pricing. Either way, the software no longer receives updates on modern Windows.

Is a Keri NXT-MSC a Mercury controller?

Keri says the NXT-MSC runs the same firmware as a Mercury EP1502, so it uses the Mercury protocol. Keri also resells genuine Mercury LP and MP panels. That can widen your hardware options later, but the panel is still managed by its head-end software, Doors.NET or Borealis, not addressed directly by outside systems.

Systems / Keri Doors.NET

Keri Doors.NET: versions, controllers, end of life and upgrade options

Keri SystemsGateStride: Not yet scheduledReviewed October 2026

By Tom Jin

Doors.NET is the client-server access-control software from Keri Systems. It runs on a Windows server, manages Keri's NXT controllers and genuine Mercury panels, and keeps the cardholder database and event history. It comes in a Standard Edition and a Professional Edition, and the current release line is 6.x (Keri's news section mentions v6.1.0). Keri also sells Borealis, a cloud platform that works with existing Keri hardware.

You typically find Doors.NET in small and mid-size offices, schools and multi-site businesses, installed by a local security integrator. Keri has a long history, so many sites still carry older pieces: Doors32 software, PXL-500 controllers or NXT Standard boards. Several of those have now reached end of life, and Doors.NET 4.x and earlier reached end of support on 15 September 2026, which is why many Keri sites are reviewing their options this year.

How to recognise Keri Doors.NET

Doors.NET runs on a Windows server, and the operator uses the Doors.NET client to manage cardholders, schedules and reports. The program's about information shows the version, which matters a great deal on Keri sites because support depends on it. In the panel enclosure you will usually find Keri NXT controllers (NXT-MSC on newer installs) or, on older sites, PXL-500 or NXT Standard boards. Some Keri sites run genuine Mercury LP or MP panels instead, because Keri resells them.

A Windows program named Doors.NET, with Standard or Professional edition and a version number in its about information.
Keri NXT-MSC two-door or four-door controllers, sometimes with NXT-4X4, NXT-RM3 or NXT-WI Plus add-on boards.
Older Keri controllers: PXL-500P or PXL-500W boards on an RS-485 network, or NXT-2D / NXT-4D standard controllers.
On very old sites, the Doors32 program instead of Doors.NET.
Mercury LP or MP panels in a Keri enclosure, which Doors.NET also manages.

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

Versions and editions

Name	Details	Status	Source
Doors.NET 6.x (Standard and Professional)	Current line. 6.0 was released 13 August 2025 and added Aperio Gen 5 AH30 hub support with Mercury MP controllers, more Local Linkage triggers for NXT-MSC and Mercury, and licence enablement for non-Keri Mercury hardware. Keri's news section mentions v6.1.0. Standard Edition starts at 256 readers and Professional at 512, with larger capacities available.	current	source
Doors.NET 5.2.0 to 5.x	Named by Keri as currently supported versions. v5.4.0.8 is the final version that supports PXL and Entraguard controllers.	current	source
Doors.NET 4.x and earlier (through 4.9.0)	End of support 15 September 2026. Keri discontinued all technical support, including bug fixes and diagnostics, and requires an upgrade before it will help. Upgrade to 5.2.0 or later, or migrate to Borealis.	end of life	source
Doors32	Discontinued in 2020, when Windows 7 support ended. The Doors32-to-Doors.NET conversion service (DNET-CONV500) ended 1 November 2025. Keri's migration path is Borealis.	end of life	source
Borealis (cloud)	Keri's cloud platform with KB controllers. Keri says it is compatible with existing Keri hardware and still supports PXL-500. A public API is not confirmed.	current	source

Hardware

Name	Details	Status	Source
NXT-MSC (2-door and 4-door)	Current Keri controller. Runs the same firmware as a Mercury EP1502, so it is Mercury-protocol hardware. Add-ons: NXT-4X4, NXT-RM3, NXT-WI Plus.	current	source
Mercury LP / MP panels	Genuine Mercury panels resold by Keri. Since Doors.NET 6.0, non-Keri Mercury hardware needs licence enablement.	current	source
NXT Standard (NXT-2D, NXT-4D)	Keri firmware controllers. Keri lists them as obsolete, available for legacy installations only.	legacy	source
PXL-500 (PXL-500P, PXL-500W)	Legacy RS-485 controller. Not supported in Doors.NET 6.0 and later (last supported in v5.4.0.8); still supported on Borealis. Keri publishes a PXL-500 Upgrade Advisor.	legacy	source
Entraguard	Keri Entraguard controllers. Support in Doors.NET ended with 6.0; v5.4.0.8 is the last version that supports them.	legacy	source
KB controllers (2-door, 4-door)	Controllers for the Borealis cloud platform (PN 02466-001 and 02465-001).	current	source

What is ending, and when

Keri has several dated changes, and they interlock. Doors.NET 4.x and every earlier release, through 4.9.0, reached end of support on 15 September 2026. Keri says it has discontinued all technical support for those versions, including bug fixes and diagnostics, and will require an upgrade before helping, without exception. Its two named routes are Doors.NET 5.2.0 or later, or a move to Borealis. Doors32 was discontinued in 2020, and the conversion service from Doors32 to Doors.NET ended on 1 November 2025, so Borealis is now Keri's path for those sites.

The hardware trap is in Doors.NET 6.0, released 13 August 2025: it ended support for PXL and Entraguard controllers. v5.4.0.8 is the last Doors.NET version that runs them, while Borealis still supports PXL-500. NXT Standard boards are listed as obsolete. So a site with PXL-500 controllers that upgrades straight to 6.x will lose those doors; it should either stop at a supported 5.x release, replace the controllers, or move to Borealis. Every dated notice is also in our end-of-life tracker.

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

What offices commonly miss

No record of who left. Like most card systems, exits usually release through a request-to-exit sensor or push bar with no badge, so the log shows who came in but not who went out unless exit readers are installed.
Version decides support. On Doors.NET 4.x or earlier, Keri requires an upgrade before it will provide any technical help.
Upgrading to Doors.NET 6.x drops PXL-500 and Entraguard controllers. Check every panel before upgrading.
No public API documentation. Keri's downloads portal needs a login, so outside software generally needs a Keri partner relationship.
Non-Keri Mercury hardware needs licence enablement from Doors.NET 6.0, which can add cost when expanding with third-party Mercury panels.

Integration options

Keri does not publish an API or SDK for Doors.NET on its public site, and its downloads portal requires a login, so integration details are not public. Keri does list partner integrations, including video systems (Milestone, Exacq, Hanwha, Digital Watchdog, OpenEye and others), wireless locks (Allegion, ASSA ABLOY Aperio, SimonsVoss) and Mercury hardware. The Doors.NET product page also mentions LDAP directory services, elevator control, SMS and email alerts, and time-in-building tracking.

On the hardware side, the NXT-MSC runs the same firmware as a Mercury EP1502, which means Keri sites share a substrate with many other Mercury-based systems. That does not open a back door for outside software: the head-end software still owns the panel, so any integration has to work through Doors.NET or Borealis. A Borealis API is not confirmed. Keep Doors.NET on a supported release; on 4.x or earlier you no longer receive security fixes or support from Keri.

Upgrade paths

Keep Doors.NET and add features in software

If your controllers are NXT-MSC or Mercury and your server is on a supported release, you can keep the doors and add what is missing through software. For Doors.NET this currently depends on a Keri partner route, because there is no public API. Get the version supported first.

Upgrade within Keri

Move from 4.x to 5.2.0 or later. If you still have PXL-500 or Entraguard controllers, stop at a 5.x release that supports them, or replace them with NXT-MSC before moving to 6.x. Sites on Doors32 or with mostly PXL hardware can look at Borealis, which Keri says works with existing Keri hardware.

Replace the platform

If the hardware is mostly PXL or NXT Standard and the software is several versions behind, a full replacement may cost little more than catching up. It means new controllers, often new readers and credentials, and re-commissioning every door, so compare it carefully with the Keri routes above.

Compare the routes over three years in the savings calculator.

GateStride and Keri Doors.NET

Not yet scheduled Keri Doors.NET is Not yet scheduled on the GateStride compatibility list. It is not on our roadmap yet, and GateStride does not work with Doors.NET today. GateStride is in early access. Keri does not publish a public API, so any future work would need a partner arrangement with Keri. If your office runs Doors.NET, tell us; demand from real sites decides what we build next.

Full compatibility list · Tell us you run Keri Doors.NET

Questions about Keri Doors.NET

Is Doors.NET 4 still supported?: No. Keri ended support for Doors.NET 4.x and all earlier releases, through 4.9.0, on 15 September 2026. Keri says it no longer provides technical support, bug fixes or diagnostics for those versions and will require an upgrade first. Its named options are Doors.NET 5.2.0 or later, or a move to the Borealis cloud platform.
Will my PXL-500 controllers work with Doors.NET 6?: No. Doors.NET 6.0, released 13 August 2025, ended support for PXL and Entraguard controllers, and v5.4.0.8 is the last version that runs them. Your options are to stay on a supported 5.x release, replace the PXL boards with NXT-MSC controllers, or move to Borealis, which Keri says still supports PXL-500.
I still run Doors32. What now?: Doors32 was discontinued in 2020, and Keri's Doors32-to-Doors.NET conversion service ended on 1 November 2025. Keri now points Doors32 sites to Borealis. Depending on your controllers, a replacement system may also be worth pricing. Either way, the software no longer receives updates on modern Windows.
Is a Keri NXT-MSC a Mercury controller?: Keri says the NXT-MSC runs the same firmware as a Mercury EP1502, so it uses the Mercury protocol. Keri also resells genuine Mercury LP and MP panels. That can widen your hardware options later, but the panel is still managed by its head-end software, Doors.NET or Borealis, not addressed directly by outside systems.

Related systems: DSX WinDSX · Keyscan Aurora · Paxton Net2

Sources

Last reviewed October 2026. Keri Doors.NET 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.