Software upgrade for the access control you already own For integrators[email protected]
GateStride

Systems / DSX WinDSX

DSX WinDSX and WinDSX SQL: versions, controllers, integration and upgrade options

DSX Access Systems (Texas)GateStride: Not yet scheduledReviewed October 2026

By Tom Jin

WinDSX is the access-control software from DSX Access Systems, a Texas manufacturer. It comes in two forms. WinDSX uses a Microsoft Access database and suits a single location with roughly 1 to 32 doors and up to three PCs. WinDSX SQL uses Microsoft SQL Server, with a separate CommServer, and DSX describes growth from 10 doors to more than 400 across multiple sites. Both run DSX's 1040-series controllers.

You typically find WinDSX in small and mid-size offices, and WinDSX SQL in larger facilities such as hospitals, college campuses, school districts and airports, which DSX names as targets. It is an on-premise, Windows-based system serviced by local integrators. DSX also offers DSX-Cloud, a browser-based subscription service that works with the same controller family. Unlike many systems in its class, DSX publishes several integration documents openly.

How to recognise DSX WinDSX

WinDSX runs on a Windows PC or server, and operators use the WinDSX program, whose title or about information shows whether it is WinDSX or WinDSX SQL and which version is installed. Larger sites have a separate CommServer PC that talks to the controllers, plus a SQL Server PC. In the panel enclosures you will find DSX-branded 1040-series boards, usually a DSX-1040PNV processor with door, input or output modules. Some staff may use the DSX Mobile Command app on a phone.

  • A Windows program named WinDSX or WinDSX SQL, with the version (current releases 5.1.17 and 6.1.17) in its about information.
  • A CommServer PC on SQL sites, which polls the controllers and passes events to the database.
  • DSX controller boards labelled DSX-1020, DSX-1022, DSX-1042, DSX-1043, DSX-1044 or DSX-1048, often with a DSX-1040PNV processor.
  • The DSX Mobile Command app on iOS or Android, used for predefined commands such as door unlock and lockdown.
  • Schlage AD-series or LE/NDE wireless locks, or L85 locksets, connected through DSX.

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

Versions and editions

NameDetailsStatusSource
WinDSX 5.1.17Current release of the Microsoft Access database version. Single location, 1 to 32 doors, expandable to 3 PCs.currentsource
WinDSX SQL 6.1.17Current release of the SQL Server version, with CommServer, SQL Server and client PCs. DSX describes growth from 10 doors to more than 400, across multiple locations.currentsource
DSX Mobile CommandPhone app for iOS and Android with predefined commands such as door lock and unlock, emergency lockdown, alarm control and event monitoring.currentsource
DSX-CloudBrowser-based subscription service through a Cloud Adapter. Up to 25 locations and 128 doors per location. Needs controller firmware 3217. A public API is not confirmed.currentsource
Older WinDSX releasesDSX does not publish end-of-support dates for older WinDSX versions in the pages we reviewed.unconfirmedsource

Hardware

NameDetailsStatusSource
DSX-1020One-door controller.currentsource
DSX-1022Two-door controller with built-in power supply.currentsource
DSX-1042Two-door controller module.currentsource
DSX-1043 and DSX-1044I/O modules: 16 outputs (1043) and 32 inputs (1044).currentsource
DSX-1048Eight-door package.currentsource
DSX-1040PNV processorProcessor for the 1040 series. Current controller firmware is 3217, which DSX-Cloud requires.currentsource
DSX-CRTConverts OSDP to Wiegand and lets another system inject a card read into a DSX door.currentsource

What is ending, and when

In the pages we reviewed, DSX does not publish dated end-of-sale or end-of-support notices for WinDSX, WinDSX SQL or the 1040-series controllers. The current software releases are WinDSX 5.1.17 and WinDSX SQL 6.1.17, and the current controller firmware is 3217. Because we found no dated notices, we do not mark any DSX product as ended, and older releases are listed as unconfirmed rather than unsupported.

The practical lifecycle question on DSX sites is usually the Windows PC and database rather than the controllers. WinDSX uses a Microsoft Access database, which DSX positions for single locations; sites that grow past that, or want multiple locations, move to WinDSX SQL with a CommServer and SQL Server. DSX-Cloud is the third option and needs firmware 3217 on the controllers. For dated notices on other brands, see 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 device or push bar with no credential, so the log shows who came in but not who went out.
  • The plain WinDSX edition uses a Microsoft Access database and is positioned for a single location. Multi-site offices need WinDSX SQL or DSX-Cloud.
  • Everything on the on-premise versions runs through Windows PCs in the office (client, CommServer and, on SQL, a database server). Patching and backups are the office's job.
  • Phone use is through DSX Mobile Command, which runs predefined commands. A phone-as-credential product is not confirmed in the pages we reviewed.
  • Integration tools are on-premise and handled through DSX technical support, so an outside service needs a connector on the local network.

Integration options

DSX publishes more about integration than most systems in this class. Event Cast polls the CommServer and forwards events to a serial port or an IP address, so another system can receive card reads and alarms as they happen. Soft I/O maps another system's inputs and outputs to DSX virtual points, which DSX linking logic can then act on. A Database Management API, which DSX calls DSX Markup Language and documents publicly as a card holder management API, handles cardholders and ships in the API folder of the install. DSX tech support also provides a video SDK on request.

For door control, the DSX-CRT converts OSDP to Wiegand and lets another system inject a card read. That route keeps DSX's own access rules and audit trail in force, because the door still decides whether the credential is valid. DSX also publishes solution sheets for Schlage AD-300 and AD-400, Schlage LE and NDE locks, and L85 locksets, plus documents on linking logic, virtual outputs and emergency lockdown configuration. All of these are on-premise, so a cloud service needs a small connector inside the office network.

Upgrade paths

Keep WinDSX and add features in software

DSX controllers are current and DSX documents Event Cast, Soft I/O, DSX-CRT and the cardholder API. That makes it realistic to keep the doors and add what is missing, such as exit tracking or a live list of who is inside, through software on the local network.

Grow within DSX

Move from WinDSX to WinDSX SQL when you outgrow a single location or the Access database, or look at DSX-Cloud if you would rather not run servers. Check the controllers are on firmware 3217 before a DSX-Cloud move, and keep the software on the current 5.1.17 or 6.1.17 release.

Replace the platform

A full replacement means new controllers, often new readers and credentials, and re-commissioning every door. DSX's published material gives no lifecycle date that forces it, so it usually makes sense only during a renovation, a move, or when the system no longer fits the business.

Compare the routes over three years in the savings calculator.

GateStride and DSX WinDSX

Not yet scheduled DSX WinDSX and WinDSX SQL are Not yet scheduled on the GateStride compatibility list. They are not on our roadmap yet, and GateStride does not work with DSX today. GateStride is in early access. DSX's published integration tools make it a reasonable candidate, but no work has started. If your office runs WinDSX, tell us; demand from real sites decides what we build next.

Full compatibility list · Tell us you run DSX WinDSX

Questions about DSX WinDSX

What is the difference between WinDSX and WinDSX SQL?
WinDSX uses a Microsoft Access database and suits a single location with roughly 1 to 32 doors and up to three PCs. WinDSX SQL uses Microsoft SQL Server with a separate CommServer and scales from about 10 doors to more than 400 across multiple sites. The current releases are 5.1.17 and 6.1.17.
Does DSX have an API?
Yes, in several parts. DSX documents a cardholder Database Management API, Event Cast for sending events to an IP address, Soft I/O for linking another system's inputs and outputs, and the DSX-CRT for injecting card reads. A video SDK is available from DSX tech support. All of them work on the office's own network.
Can I move my DSX system to the cloud?
DSX offers DSX-Cloud, a browser-based subscription that connects through a Cloud Adapter. DSX lists up to 25 locations and 128 doors per location, and the controllers need firmware 3217. Ask your integrator whether your existing 1040-series hardware and firmware qualify before planning a move.
Are DSX controllers end of life?
We found no dated end-of-sale or end-of-support notice for the DSX 1040-series controllers. The DSX-1020, 1022, 1042, 1043, 1044 and 1048 are on DSX's current hardware page, with firmware 3217. If you are told otherwise, ask for the written DSX notice.

Related systems: Keri Doors.NET · Keyscan Aurora · Paxton Net2

Sources

Last reviewed October 2026. DSX WinDSX 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.