Kisi Controller, Reader and Terminal Hardware
Kisi combines cloud-managed controllers, readers and entry terminals with conventional door hardware. The correct system engineering accounts for door count, credential methods, lock power, life-safety interfaces, network reachability, offline behavior and legacy migration.
A headline feature is not the choice; the complete system is
Match devices, software, licensing, infrastructure, retention, integrations and support to the operating requirement before finalizing the system engineering.
Document every opening and its interfaces
Nothing is ordered until each opening has a record: lock type, voltage and current, fail-safe or fail-secure behavior, door position plus request to exit, fire-alarm release, accessibility and mechanical condition. Doors group by cable route, backup-power requirement and where the controller sits. Elevators and special openings get confirmed separately.
Discovery needs to identify protected areas, users, schedules, response procedures, privacy expectations, existing equipment and the party who will administer the finished system. Product claims only become useful after they are translated into measurable coverage, capacity, availability and response requirements.
- Lock behavior and life-safety release
- REX and door input points
- Pathways and controller groupings
- Elevator/special interfaces
Which controller, which reader
Assign Controller Pro capacity and expansion, then select Reader Pro or Terminal Pro by credential, environment, mounting and visitor workflow. Verify exact ports, wiring, accessories and supported third-party hardware. A Wiegand migration may preserve assets but needs to include a security and lifecycle review.
Nothing is ordered until the exact model is checked against supported software, since names that look alike can hide differences in license, capacity and integration limits. Pathways, mounting, environmental ratings, network addressing, PoE or low-voltage power, backup power and the door or camera interfaces all have to be coordinated.
- Reader or Terminal per door
- Indoor/outdoor environment
- Credential type and migration path
- Expansion and add-on accessories
| Component | Role | Confirm |
|---|---|---|
| Controller Pro 2 | Door relays and inputs | Capacity, power and interfaces |
| Reader Pro | Mobile/card presentation | Environment and credential fit |
| Terminal Pro | QR and visitor entry | Workflow, mounting and network |
| Wiegand board | Legacy interface option | Compatibility and security tradeoff |
Power, network and cloud prerequisites
Activation waits on services and the account. Services: approved power, battery backup, Ethernet/PoE or another supported connection, DNS, DHCP, NTP and outbound firewall access. Account: the customer organization with its administrators named. Record the expected offline behavior and who owns recovery when the network or cloud is interrupted.
Use named administrators, least privilege and multifactor authentication where supported. Establish backup, update, health-monitoring and escalation ownership. Firmware and software needs to come from the manufacturer portal after compatibility and release-note review, with rollback or recovery prepared before change.
- Load on power and batteries
- Firewall rules, Ethernet and PoE
- Organization ownership
- What happens offline, and recovery
Proving doors and administration
Exercise every entry path: card, mobile and QR, a denied attempt, forced and held door alarms, REX, schedules, lockdown, fire release where it applies, event history and offline operation. Confirm reader-to-door assignments and labels match. Hand over wiring, network, firmware, administrator and support records without credentials in them.
Acceptance needs to test normal use, denied or alarm conditions, loss of network or power, notification, audit history and administrator recovery. Deliver protected configuration records, licenses, serials, diagrams, test evidence, support links and clearly owned exceptions.
- Entry granted and entry refused
- Alarms at the door
- Event handling in the cloud and offline
- As-built handoff, kept protected
The stages we work through
The final system engineering depends on site conditions, existing systems, client policies and the selected manufacturer or platform.
Discover
Documentation covers assets, people, workflows, risks and systems already in place.
System Engineering
Choose an architecture, devices, licenses and integrations that are supported.
Install
Staging, labeling and commissioning happen under change control.
Validate
Run the operating scenarios, then hand over lifecycle records.
Information to gather before system engineering
Good decisions are easier when the security engagement team starts with complete operational and technical information. The following items help reduce assumptions, change orders and avoidable return visits.
- Use cases and how staff respond
- Whether devices and software match
- Physical interfaces plus power and network
- Licenses, identity and security posture
- Sign-off, support and system lifecycle
Common questions
These are common engineering assessment questions. A site-specific answer needs to be confirmed during discovery and system engineering.
Do existing door locks work with Kisi?
In many cases, once voltage, current, operation and code interfaces have been checked as compatible.
Does every door need a Terminal Pro?
No. It belongs at the doors where the QR or visitor workflow matters.
Does a Wiegand migration keep the readers in place?
Supported system engineerings may do so, but compatibility and security limitations need review.
With cloud management, is local backup power still needed?
No. Controllers, readers and locking hardware still need an appropriate power system engineering.
Firmware, software and technical files are hosted by the manufacturer on its own site. We do not mirror those files here.
Discuss a commercial security engagement
Tell us about the doors, buildings, users, existing equipment, operational requirements and desired completion date. We will help organize the right discovery and system engineering conversation.
Kisi owner, administrator and buyer resources
Use the parent-company Kisi knowledge center to research current hardware, software, integration and ownership questions before Georgia field design begins.
Discuss Kisi installation, maintenance or service
Detailed guides are maintained by 360TechnologyGroup.com, the parent-company knowledge center.