Kisi Controller, Reader and Terminal Hardware
Kisi combines cloud-managed controllers, readers and entry terminals with conventional door hardware. The correct deployment design accounts for door count, credential methods, lock power, life-safety interfaces, network reachability, offline behavior and legacy migration.
Select the complete system, not one headline feature
Match devices, software, licensing, infrastructure, retention, integrations and support to the operating requirement before finalizing the deployment design.
Map each opening and hardware interface
Survey every opening for lock type, voltage/current, fail-safe or fail-secure behavior, door position, request to exit, fire-alarm release, accessibility and mechanical condition. Group doors by controller location, cable route and backup-power requirement. Confirm elevator or special-opening needs separately.
Discovery must 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 and life-safety behavior
- Door inputs and REX
- Controller grouping and pathways
- Elevator/special interfaces
Select controllers and readers
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 must include a security and lifecycle review.
Coordinate network addressing, PoE or low-voltage power, pathways, environmental ratings, mounting, door or camera interfaces and backup power. Verify exact model compatibility and supported software before ordering; similar product names can conceal different capacity, license or integration limits.
- Reader versus Terminal use
- Indoor/outdoor environment
- Credential and migration method
- Accessories and expansion
| 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 |
Network, power and cloud readiness
Provide approved power, battery backup, Ethernet/PoE or supported connectivity, DNS, DHCP, NTP and outbound firewall access. Establish the customer organization and named administrators before activation. Document offline expectations and the recovery owner for network or cloud interruptions.
Use named administrators, least privilege and multifactor authentication where supported. Establish backup, update, health-monitoring and escalation ownership. Firmware and software must come from the manufacturer portal after compatibility and release-note review, with rollback or recovery prepared before change.
- Power and battery load
- Ethernet, PoE and firewall
- Organization ownership
- Offline and recovery plan
Commission doors and administration
Test card, mobile, QR and denied access; forced/held door; REX; schedules; lockdown; fire release where applicable; event history and offline operation. Reconcile reader-to-door assignments and labels. Deliver wiring, network, firmware, administrator and support records without publishing credentials.
Acceptance must 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.
- Positive and denied entry
- Door alarm conditions
- Cloud and offline events
- Protected as-built handoff
How we plan and deliver the work
The final deployment design depends on site conditions, existing systems, client policies and the selected manufacturer or platform.
Discover
Document people, assets, workflows, risks and existing systems.
Deployment Design
Select the supported architecture, devices, licenses and integrations.
Install
Stage, label and commission through controlled changes.
Validate
Exercise operating scenarios and deliver lifecycle records.
Information to gather before deployment design
Good decisions are easier when the site program team starts with complete operational and technical information. The following items help reduce assumptions, change orders and avoidable return visits.
- Operational use cases and response
- Device and software compatibility
- Power, network and physical interfaces
- Licensing, identity and cybersecurity
- Acceptance, support and lifecycle
Frequently asked questions
These are common deployment planning questions. A site-specific answer must be confirmed during discovery and deployment design.
Can Kisi reuse existing door locks?
Often, if voltage, current, operation and code interfaces are compatible and verified.
Is Terminal Pro required at every door?
No. Use it where its QR or visitor workflow is needed.
Can a Wiegand migration retain existing readers?
Supported deployment designs may do so, but compatibility and security limitations need review.
Does cloud management eliminate local backup power?
No. Controllers, readers and locking hardware still need an appropriate power deployment design.
Manufacturer software, firmware and technical files remain on the manufacturer’s official website. We do not mirror firmware files locally.
Discuss a commercial security site program
Tell us about the doors, buildings, users, existing equipment, operational requirements and desired completion date. We will help organize the right discovery and deployment design conversation.
Kisi owner, administrator and buyer resources
Georgia and Southeast clients can use these Kisi guides to prepare scope, budget, credentials, identity workflows and acceptance requirements before deployment.
Discuss Kisi installation, maintenance or service
Detailed guides are maintained by 360TechnologyGroup.com, the parent-company knowledge center.