Installation, service, maintenance and support
Keri Borealis vs Doors.NET: Login, Download, Migration and Support Guide
Keri owners often need to identify whether a site uses browser-based Borealis or a locally hosted Doors.NET server before they can solve login, software, controller or database problems. This guide separates those architectures and explains a controlled support path.
We install, configure, service, maintain and support Keri Systems products and software. Our work includes site surveys, system design, authorized product procurement, commissioning, training, troubleshooting, repair and lifecycle planning.
Borealis and Doors.NET software: what owners and buyers should evaluate
Borealis cloud management
Browser-based access management with Keri hub/controller connectivity, multi-site administration, schedules, events, users and compatible mobile workflows. Confirm subscription, tenant ownership, supported hardware and WAN dependencies.
Doors.NET on-premises
Windows/server-based management for supported NXT, authentic Mercury and related hardware. Plan SQL/database backup, server lifecycle, client versions, licenses, services, ports and recovery credentials.
Legacy migration
Doors32, PXL, Entraguard and older Doors.NET estates require version- and controller-specific assessment. Preserve database and credential records, test conversion and confirm the target platform before field changes.
Scope the complete system
| Planning area | What to verify |
|---|---|
| Ownership and login | Tenant or license owner, administrator accounts, MFA/recovery, installer access, offboarding and documented emergency access. |
| Software and database | Exact Doors.NET version/edition, Windows and SQL versions, backups, license records, clients, services and supported upgrade sequence. |
| Hardware path | NXT, NXT-MSC, KB, PXL or authentic Mercury models, reader protocols, expansion modules, firmware and target-platform compatibility. |
| Operations | Schedules, holidays, access groups, elevator control, alerts, reporting, badging, integrations and outage behavior. |
Installation, upgrade and acceptance workflow
- Survey every opening and document door construction, handing, egress, fire-rating, locking hardware, power, pathways, network and accessibility requirements.
- Inventory the exact software edition, licenses, controllers, readers, credentials, integrations and current firmware before proposing additions or migration.
- Build a model-specific bill of materials and coordinate electrical, network, life-safety and door-hardware responsibilities before installation.
- Configure roles, schedules, holidays, credential workflows, alarms, integrations, backups and administrator recovery using least-privilege practices.
- Commission authorized, denied, forced, held, request-to-exit, fire-release, network-loss and power-loss behavior at every affected opening.
- Deliver as-builts, device and version records, administrator training, warranty information and a preventive-maintenance plan.
Keri Systems installation, maintenance, service and support
We troubleshoot Borealis and Doors.NET systems, install supported Keri and Mercury hardware, configure databases and users, stage authorized upgrades, migrate eligible legacy systems, restore documented operation and provide recurring maintenance.