Authorized dealer · Certified installers · Charlotte, NC headquarters
360 Technology Group is an authorized Keri Systems dealer and certified installer
We have been selling, installing, programming and servicing Keri Systems systems across North and South Carolina since 2018 — more than 8 years. Our scope covers Keri Borealis cloud access control, Doors.NET software, NXT and Mercury controllers, readers and credentials.
- Authorized Keri Systems dealer — we quote and supply genuine Keri Systems equipment, licensing and subscriptions.
- Certified Keri Systems installers — our technicians install, wire, program, commission and document the system.
- Repair and takeover — we service, troubleshoot, expand and take over existing Keri Systems installations we did not originally install.
- 24/7 emergency service — on-call service technicians for emergency repairs, plus scheduled preventive maintenance.
We cover every city in North Carolina and South Carolina from our Charlotte headquarters. Request a quote or service call Call 704-726-4254
North Carolina and South Carolina planning guide
Keri Systems Products, Software, Controllers, Readers and Mobile Access Guide
Use this Keri Systems Products, Software, Controllers, Readers and Mobile Access Guide guide to move the discussion beyond a feature list. Compatibility, infrastructure, administration, failure behavior, testing and lifecycle ownership should be settled before equipment or subscriptions are ordered.
Start with the decision, not the catalog
360 Technology Group evaluates Keri Systems Products, Software, Controllers, Readers and Mobile Access Guide as part of a complete software, integration and automation initiative. The recommendation should follow a field-verified problem statement, not a presumption that every published feature belongs in the project.
Discovery documents the current equipment, affected users, desired workflows, required integrations, security and privacy expectations, project constraints and measurable acceptance criteria. That evidence creates a fair basis for comparing reuse, migration and replacement.
For Carolina facilities, the scope should also account for occupied work areas, weather exposure, lightning and surge conditions, local construction coordination, network readiness, service access and the owner’s long-term administration model.
Detailed product and planning guides
Each card below opens a published guide with deeper product-family, design or implementation information.
Keri Systems Access Control Installation, Repair, Dealer, Reseller and Maintenance
Open the detailed product, design or implementation guide.
Keri Borealis Cloud Access Control
Open the detailed product, design or implementation guide.
Keri Doors.NET Access Control Software
Open the detailed product, design or implementation guide.
Keri NXT and Mercury Controllers, Readers and Credentials
Open the detailed product, design or implementation guide.
Capabilities and selection checkpoints
The cards in this section summarize information to evaluate; they are not separate pages. Availability and compatibility can change, so final models and releases must be confirmed against current manufacturer resources.
Keri Systems product guide
Confirm which current models, editions, licenses and dependencies support this requirement before procurement.
Borealis Connect
Confirm which current models, editions, licenses and dependencies support this requirement before procurement.
Doors.NET
Treat this as a design checkpoint; the final selection depends on field conditions and supported releases.
Doors32 legacy environments
Treat this as a design checkpoint; the final selection depends on field conditions and supported releases.
Keri controller platforms
Confirm which current models, editions, licenses and dependencies support this requirement before procurement.
KB controller line
Treat this as a design checkpoint; the final selection depends on field conditions and supported releases.
Legacy controller support and retrofit planning
Confirm which current models, editions, licenses and dependencies support this requirement before procurement.
Readers, credentials and user-facing products
Connect this capability to a named user workflow and a testable result at the actual facility.
Keri readers
Review compatibility, capacity, infrastructure and lifecycle implications with the complete system design.
Cards, fobs and credentials
Compare retained equipment, migration effort, subscription impact and replacement options for this topic.
Entry panels and wireless locking
Compare retained equipment, migration effort, subscription impact and replacement options for this topic.
GeoKey mobile access
Review compatibility, capacity, infrastructure and lifecycle implications with the complete system design.
Evidence to collect before design
A useful survey and stakeholder review should produce the following project evidence for Keri Systems Products, Software, Controllers, Readers and Mobile Access Guide:
- Users, roles, tasks, exceptions and measurable operating outcomes.
- Source systems, APIs, data ownership, quality, retention, migration and synchronization.
- Authentication, authorization, encryption, logging, privacy and compliance requirements.
- Availability, performance, device, browser, accessibility and offline expectations.
- Development, testing, production, deployment, rollback, backup and recovery responsibilities.
- Acceptance scenarios, training, administration, monitoring, support and enhancement ownership.
Architecture and integration review
Bounded outcome
Define the user task and measurable result before selecting a platform or model.
Data boundary
Document sources, ownership, consent, retention, quality and permitted uses.
Integration contract
Specify APIs, events, failure handling, reconciliation and responsible system owners.
Security model
Design identity, roles, secrets, logging, backups and recovery into the architecture.
Evaluation
Test representative workflows, edge cases, accessibility, performance and abuse scenarios.
Operating model
Assign releases, monitoring, support, documentation and future improvement decisions.
Compare proposals on the same evidence
Product names and device counts do not make competing proposals equivalent. Ask each bidder to identify assumptions, exclusions, supported versions, owner responsibilities and the proof that will be delivered at acceptance.
| Comparison area | Evidence a complete proposal should provide |
|---|---|
| Fit for the operating need | A written explanation of how Keri Systems Products, Software, Controllers, Readers and Mobile Access Guide supports the required users, events and workflows. |
| Compatibility | A supported-parts, software, license and integration matrix tied to the proposed architecture. |
| Infrastructure | Documented power, network, pathways, environmental and owner-furnished dependencies. |
| Acceptance | Named tests, expected results, exception handling and responsibility for correcting deficiencies. |
| Lifecycle | Current support status, update approach, warranty, subscriptions, spares and replacement planning. |
Deployment and acceptance sequence
- Discovery: agree on users, operating outcomes, retained systems, constraints and acceptance criteria.
- Field validation: verify dimensions, infrastructure, environmental conditions, pathways, power, network and integration points.
- Documented design: name the architecture, supported components, licenses, responsibilities, assumptions and change process.
- Staging and implementation: prepare configuration, backups, labels and test scripts before controlled field deployment.
- Operational acceptance: exercise normal use, exceptions, outages and recovery; then deliver training and system records.
Software, firmware and lifecycle responsibility
Record the installed model, hardware revision, software or firmware release, license or subscription, warranty and administrator ownership at handoff. Those details make later troubleshooting and upgrade planning materially safer.
Downloads, release notes, advisories and manuals should come from the manufacturer’s official portal. 360 Technology Group links to official resources and does not host firmware files locally. Some portals require an authorized customer, dealer or support entitlement.
Before any update, confirm the exact model and region, prerequisites, supported intermediate releases, backup, maintenance window, integration compatibility, rollback limits and post-update test plan. Cloud-managed products may control release timing differently from locally managed systems.
Build a project-specific comparison
Share the facility type, Carolina location, existing platform, approximate device count, operating problem, required integrations and target schedule. 360 Technology Group can use that context to determine whether Keri Systems Products, Software, Controllers, Readers and Mobile Access Guide deserves a detailed site and design review.
Keri Systems owner, administrator and buyer resources
Use these owner and buyer resources to connect product research with surveyed design, installation, software setup, commissioning, maintenance and support in North and South Carolina.
Official Keri Systems software, firmware and support
Use these manufacturer-owned portals for current downloads, release notes, manuals, advisories and technical resources. 360 Technology Group links to official sources and does not copy or host firmware files.
Update carefully: confirm the exact model, region, hardware revision, installed version, prerequisites, required intermediate releases, support entitlement, integrations, backup, maintenance window, rollback limitations and post-update tests. The wrong package or sequence can interrupt service or prevent a downgrade.
Some portals require a customer, dealer, certified-technician or active-support login. Cloud-managed products may update automatically and may not offer a public firmware file.