Door-controller, reader and credential choices for new Keri systems and responsible upgrades of existing Keri hardware.
What this product family does
Keri offers NXT controller families, NXT-MSC Mercury-powered controllers, supported Authentic Mercury hardware and expansion/I/O options. The correct panel is chosen by software platform, door count, reader protocol, elevator or automation needs, enclosure/power design and the features required at the edge.
Products and decisions
| Product area | What it includes | Selection guidance |
|---|---|---|
| NXT / KB | Keri controller paths for Borealis and selected Keri deployments | Check cloud/software compatibility; the KB controller is Borealis-specific and does not simply substitute in every Doors.NET design |
| NXT-MSC | Mercury-powered Keri controller architecture with OSDP support in applicable designs | Useful where Mercury interoperability and advanced reader communications are project priorities |
| Readers | Keri and compatible Wiegand/OSDP reader families, including mobile-capable choices | Select by credential, environmental rating, mounting, keypad and secure-channel requirements |
| I/O and elevators | Expansion modules and supported elevator/control interfaces | Build an input/output schedule instead of assuming every panel supports every workflow |
Questions to answer before quoting
- List panel and module part numbers before recommending reuse
- Verify standby power and lock-power calculations
- Plan a credential-security upgrade rather than preserving weak badges by default
- Confirm supervised inputs, OSDP secure channel and offline behavior
- 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 NXT and Mercury Controllers, Readers and Credentials, the right model and architecture depend on the site, existing infrastructure and operating policy. A proposal should clearly document the following access-control system decisions before equipment is ordered:
- Number and type of controlled openings
- Controller, reader, lock and credential compatibility
- Cloud or on-premise administration and ownership
- Offline behavior, backup power and emergency operation
- Directory, HR, video, visitor and elevator integrations
- Licensing, cybersecurity, training and lifecycle support
Installation, testing and handoff
A site survey records each opening, door hardware, cable path, power, network, credential policy and integration requirement. The design then maps readers, controllers, locks, inputs, outputs and administrator roles to the operational workflow. Commissioning includes door-by-door functional tests, failure-mode and backup-power checks, permission and schedule tests, event verification, administrator training and as-built documentation. Product availability, subscriptions and supported integrations are confirmed for the current project before procurement.
Frequently asked questions
Questions that come up when specifying Keri panels, readers and credentials, or when deciding whether existing hardware can stay.
NXT or NXT-MSC: which controller belongs in our quote?
It depends on the software platform and on what you need at the reader. NXT and KB are Keri controller paths for Borealis and selected Keri deployments, and the KB controller is Borealis-specific rather than a drop-in for every Doors.NET design. NXT-MSC is the Mercury-powered architecture, chosen where Mercury interoperability and advanced reader communications are project priorities.
Can the Keri panels already in our closets stay?
Possibly, but not on a walk-through impression. We list panel and module part numbers before recommending reuse, because controller paths differ by software platform and a KB controller does not simply substitute in a Doors.NET design. Enclosure condition, power capacity and available expansion then decide whether reuse saves money or just relocates the problem.
Can staff keep the badges they carry today?
Sometimes they can, but the better opening question is whether they should. The approach here is to plan a credential-security upgrade rather than preserving weak badges by default, then select readers by credential, environmental rating, mounting, keypad and secure-channel requirements. Where old and new credentials must coexist through a transition, the reader choice has to allow for both.
Can the same panels handle elevator control?
That depends on the panel and the modules paired with it. Expansion modules and supported elevator/control interfaces exist in the Keri line, but the workflow has to be drawn first: which floors are restricted, at which times, and what feedback the cab needs. Build an input/output schedule instead of assuming every panel supports every workflow.
How is power for panels and locks worked out?
By calculation, not by rule of thumb. We verify standby power and lock-power calculations from the actual lock current at each opening, the number of locks that can release at once, and the standby duration the site requires. Enclosure and power design then feed back into panel choice, since a board that fits electrically may not fit the can it was meant to share.
Will doors still work if a panel loses its network connection?
That depends on the controller and how the design configures it, which is why supervised inputs, OSDP secure channel and offline behavior are confirmed in writing before panels are ordered. Commissioning then proves the answer with door-by-door functional tests, failure-mode and backup-power checks, and permission and schedule tests, with results written into the as-builts.
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.