Keri Systems Support
Keri support should begin with the software, hardware, and migration path actually installed.
210 Solutions helps existing Keri owners with troubleshooting, takeover, expansion, authorized access, Doors.NET or Borealis decisions, documentation, and modernization planning.
Customer intent
Solve the owner’s problem before discussing products.
The useful questions are what the organization needs to accomplish, what is installed, what access and documentation exist, what currently fails, and what can be supported responsibly.
Identify the environment
Determine whether the system uses Doors.NET, Borealis, older Doors32 history, PXL, NXT, NXT-MSC, Mercury-related hardware, or another supported configuration.
Current and legacy status
Keri currently documents Borealis cloud access control and Doors.NET 6.x, while older Doors.NET 4.x and Doors32 paths have changed support status.
Troubleshooting
Review controllers, hubs or gateways, communications, server or cloud access, licensing, credentials, schedules, readers, doors, and event behavior.
Expansion
Verify controller, hub, software, license, site, door-capacity, and compatibility requirements before adding hardware.
Migration
Evaluate supported conversion paths, database and configuration transfer, hardware reuse, access rights, site structure, downtime, and training.
Takeover and planning
Recover documentation and authorized access, identify usable assets, and compare stabilization, expansion, Borealis migration, or broader replacement.
Technical verification
Current facts are separated from 210’s recommendation.
Current official Keri Borealis and Doors.NET knowledge-base, release, compatibility, conversion, and support information reviewed August 9, 2026.
The final recommendation remains 210 Solutions’ professional judgment based on the specific system, building, requirements, and verified product status.
Connected services
Support the system as part of the building.
Network, software, programming, field devices, power, documentation, user workflow, and ongoing support are reviewed together.
Explore related modernization services →Proof requirements
- Approved related project or field experience
- Verified current and legacy product context
- Labeled media placeholder until approved media exists
- No invented manufacturer relationship or customer result
Get Support
Tell us what system you have and what is happening.
Include the building, software or platform name, known versions, symptoms, available documentation, and the outcome you need.