A client/server Keri management platform for sites that require locally hosted access control, scalable hardware choices and advanced security workflows.
What this product family does
Doors.NET can manage Keri NXT and supported third-party controller platforms, including Mercury-based configurations. Keri lists multi-site connectivity, concurrent operators, local/global linkage, reporting, OSDP support with NXT-MSC, video integrations and optional web/backup tools. Edition and licensed-feature requirements must be confirmed against the project.
Products and decisions
| Product area | What it includes | Selection guidance |
|---|---|---|
| Core platform | Doors.NET server, communications gateway and operator clients | Sites that prefer local control and can maintain the required server, database and backup |
| Optional tools | Cloud Backup/Restore, Doors.WEB, Visual Doors and Telepathy map client | Choose only where remote supervision, simplified administration, recovery or graphic maps are required |
| Advanced rules | Dual verification, two-person rules, anti-passback, reporting and linkage | Validate licensing, controller support and the client’s written operating procedure |
| Integrations | Supported VMS, wireless locks, entry panels, elevators and directory services | Use current Keri integration documentation and test the actual versions |
Questions to answer before quoting
- Who owns Windows, SQL/database, patching and backup?
- How many doors, operators, sites and cardholders are required?
- Which advanced functions require a specific Doors.NET edition or module?
- Is a cloud migration expected during the equipment lifecycle?
- Who owns administration, backups, updates and recurring services?
- What must continue working during network, internet or power failure?
- Which opening, egress, accessibility and life-safety requirements apply?
- What training, documentation and preventive maintenance are required?
Request a product-specific site survey
Boston High Tech serves projects from our Charlotte headquarters and local client offices serving Massachusetts, New York and New Jersey.
Official manufacturer references
Capabilities and product families were checked against the manufacturer links below.
How to compare and specify this product family
For Keri Doors.NET Access Control Software, the right model and architecture depend on the site, existing infrastructure and operating policy. A proposal should clearly document the following electronic lock and door-hardware system decisions before equipment is ordered:
- Opening type, handing, frame and door condition
- Fire rating, egress, accessibility and code constraints
- Fail-safe or fail-secure operation and emergency release
- Credential, reader and controller compatibility
- Battery, wireless gateway and offline behavior
- Mechanical key override, maintenance and lifecycle support
Installation, testing and handoff
Each opening is surveyed as a complete assembly. We verify the door, frame, handing, existing prep, latching, closer, egress hardware, power path and the required emergency behavior before specifying a lock. Installation includes alignment and mechanical correction within scope, cable and power testing, credential enrollment, door-state and request-to-exit tests, and failure-mode verification. The owner receives opening schedules, administrator guidance and maintenance requirements; private credential data and certificate details are not published.
Frequently asked questions
Questions buyers ask about running Doors.NET on their own servers, its editions, and the controllers it can manage.
Is Doors.NET hosted for us, or does it run on our own server?
It runs on your own server. Doors.NET is a client/server platform built from a Doors.NET server, communications gateway and operator clients, all locally hosted. That suits sites that prefer local control, and it commits the organization to maintaining the server, database and backup. Sites that cannot carry that should say so early, since a later cloud migration changes the hardware choice.
Do advanced rules like anti-passback come with the base software?
Not automatically. Dual verification, two-person rules, anti-passback, reporting and linkage sit in the advanced-rules group, and each has to be checked against the specific Doors.NET edition or module the quote is built on. Controller support matters as much as licensing, and the client’s written operating procedure should exist before any of those rules is turned on.
We already have Mercury panels. Can Doors.NET run them?
Doors.NET can manage Keri NXT and supported third-party controller platforms, including Mercury-based configurations, so the real question is which panels and firmware versions are on your walls now. We list them, match that list against current Keri integration documentation, and test the actual versions rather than assuming a family name is close enough.
Which controller do we need if we want OSDP readers?
Keri lists OSDP support with NXT-MSC, so reader protocol gets decided together with the panel rather than after it. A door planned for OSDP is quoted on a controller carrying that support, and reader cable is pulled accordingly. Running some Wiegand and some OSDP openings on one site is workable, but the door schedule has to say which is which.
What does our IT department have to take on?
More than a network drop. The platform needs a Windows server, a SQL database, patching and backups, and the proposal has to answer who owns Windows, SQL/database, patching and backup before doors are commissioned. If in-house IT will not carry it, saying so early changes the hardware, the ownership model and the recurring services line in the quote.
What gets tested at each door before you hand the system over?
Each opening is surveyed as a complete assembly, then proved: alignment and mechanical correction within scope, cable and power testing, credential enrollment, door-state and request-to-exit tests, and failure-mode verification. The owner receives opening schedules, administrator guidance and maintenance requirements. Private credential data and certificate details stay out of the handover package.
Keri Systems owner, administrator and buyer resources
Discuss Keri Systems installation, maintenance or service
Detailed guides are maintained by 360TechnologyGroup.com, the parent-company knowledge center.
Official Keri Systems software, firmware and support
Official manufacturer resources. We link out rather than host firmware.
Before updating: confirm model, hardware revision, current version, entitlement and rollback plan, and schedule monitored or life-safety-adjacent systems with the administrator.