Kantech EntraPass and KT Controllers
Kantech supports small standalone doors and larger EntraPass-managed systems. The system engineering needs to match controller topology, readers, credentials, network ownership and growth to the client’s operations.
Architecture first, part counts second
Counting doors gets you part of the way. The rest comes from entry and exit readers, offline behavior, network routes, encryption, room to expand, integrations, and who will administer access.
Topology and controller family
KT-1 is useful for one-door IP deployments and supports entry and exit readers. Current KT-2 and KT-4 products address compact two- and four-door applications with their own supported operating modes. Existing sites may also contain KT-300 or KT-400 controllers, so expansions need a compatibility and lifecycle review rather than an automatic like-for-like order.
Building layout decides the balance here: distributed IP controllers can shorten long field runs, while centralized panels can make power and service easier to manage. Draw the controllers against doors, network closets and power locations, and write down the behavior when the server, the IP network or an upstream controller drops out.
- Reader count at each door
- Supported IP and RS-485 controller links
- Event storage, schedules and offline decisions
- Compatibility and lifecycle of installed controllers
Administering the EntraPass software
Site count, workstations, gateways, users, doors, integrations and remote-access needs set the current EntraPass edition and the licenses that go with it. Operators and permissions follow job roles. When administrators share one login, attributing a change or an investigation to a person gets hard.
Bulk enrollment depends on groundwork, so cardholder fields, access levels, schedules, holidays and expiration rules come first. Name the approver, name the person who enters changes, and agree the termination process. Reports and alarms earn their keep once someone owns them and reviews them on a routine.
- Licenses for edition, workstations, gateways
- Standards for cardholders, schedules, access levels
- Operators named, audit trail owned
- Workflow for approval, termination, periodic review
| Controller | Typical scope | Confirm before selection |
|---|---|---|
| KT-1 | One door with entry/exit readers | PoE, operating mode and expansion topology |
| KT-2 | Compact two-door applications | Standalone and integration requirements |
| KT-4 | Four-door distributed applications | Power, network and EntraPass system engineering |
| Existing KT family | Expansion or migration sites | Current support, firmware and compatibility |
Door hardware, readers and credentials
Coordinate reader technology with credential security, mobile plans and existing populations. Legacy proximity may be convenient for migrations but needs to not be confused with stronger encrypted smart-card technology. Verify the exact reader, credential, key management and controller support as one system.
Walk every opening and review both hardware and sequence: lock type, voltage, current, fail mode, door contact, request-to-exit, emergency release, accessibility, mechanical condition. Where separate or supervised power is called for, provide it, and calculate the standby load.
- Credential technology and reader protocol
- How enrollment and migration run
- Sequence across lock, contact, request-to-exit
- Egress, fire interface and power coordination
Functional Commissioning, backups and support
The test list runs granted, denied and expired credentials, schedule behavior, door held, door forced, request-to-exit and a network gone offline. Check event timestamps, alarm routing and reports. Integrated intrusion or video belongs in the same matrix; the access screen alone is not the test.
A backup of the EntraPass configuration is only half the job; the supported restore process gets documented alongside. Record firmware, addresses, MACs, door assignments and panel power for each controller. Software, firmware and documents come from Kantech official resources, and controller files never go out through public download pages.
- Door-state and credential scenarios
- Tests for offline, power, communication
- Database restore and backup, recorded
- Controller inventory checked against official lifecycle sources
How KSEDCO runs the project
The final system engineering depends on site conditions, existing systems, client policies and the selected manufacturer or platform.
Survey openings
Capture doors, hardware, readers, power, pathways and controllers already in place.
System Engineering topology
Controllers, network relationships, software and licenses get chosen.
Configure governance
Set up cardholders, operators, access levels, schedules and alarms.
Prove, then close
Run the door, credential, failure and reporting scenarios, then take the backup.
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.
- Schedule of openings and hardware
- Network and controller topology
- Migration plan for readers and credentials
- Operator roles, EntraPass edition and licenses
- What we test, back up, maintain
Questions clients ask
These are common engineering assessment questions. A site-specific answer needs to be confirmed during discovery and system engineering.
Does the KT-1 take only one reader?
No. Two readers are supported on a single controlled door, one for entry and one for exit, within the supported configuration.
What happens when the Kantech server is unreachable?
Supported controllers retain defined local functions, but exact offline behavior and event capacity needs to be documented for the selected architecture.
Is reusing a KT-300 or KT-400 a good idea?
Only once condition, current support, firmware compatibility and capacity check out and it suits the client’s lifecycle goals.
Are all credential technologies equally strong?
No. Key management and the underlying technology vary between credentials. Pick reader and credential together, as one end-to-end security decision.
Firmware, software and technical documents stay where the manufacturer publishes them. KSEDCO does not host copies of those files.
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.
Kantech owner, administrator and buyer resources
Use the parent-company knowledge center to prepare product, software, infrastructure and acceptance requirements before Georgia engineering and service.
Discuss Kantech installation, maintenance or service
Detailed guides are maintained by 360TechnologyGroup.com, the parent-company knowledge center.