For IT, security and facility leaders
Keyscan Access Control System Our field review of Dormakaba Aurora
If you are evaluating Keyscan—or already responsible for one—this page explains what your team will operate: Aurora software, door controllers, readers, credentials, servers, integrations and support.
The short version: Keyscan is dependable commercial access control when the controller layout, server environment, credentials and daily administration are planned together.
Real Keyscan Installations, Not Product Renderings
These Umbrella field images show the cabinets, readers and door hardware your integrator and facility team must install, document and support. The tabs below explain the decisions behind that work.
Quick Answer
Is Keyscan a Good Access Control System?
Yes, for the right operating environment.
A Keyscan access control system is a strong option when you want hardwired door control, local controller operation, an established Windows-based management platform and room for functions such as lockdown, anti-passback, elevator control and system integrations.
It is especially relevant if you already have Keyscan controllers, wiring or readers worth keeping. It can also make sense for schools, manufacturing facilities, commercial buildings and multi-building campuses with an IT team or service partner prepared to support Aurora.
Keyscan is less compelling when your main goal is mobile-first administration, minimal server responsibility or one cloud interface for access control, video, intercom and visitor management.
Keyscan makes sense when
- You want door controllers to keep making local access decisions if the management server is unavailable.
- Your facility has many hardwired openings, gates or elevator floors.
- You need to repair or expand an existing Keyscan installation without replacing serviceable infrastructure.
- Your IT team accepts responsibility for the Aurora server, database, backups and upgrades—or you have a defined hosted-services plan.
- Your security team needs more than basic lock and unlock schedules.
Verify before you approve it
- Which controller and communication module serves every door.
- Whether current readers support the cards, fobs and mobile credentials you intend to use.
- Where Aurora, its database and its communication services will run.
- Which features require separate licenses, modules or integrations.
- Whether your administrators can produce the reports and emergency actions they need without calling a technician.
- Who owns first-line support after the installer leaves.
Our verdict
We do not consider Keyscan obsolete. We also would not keep or select it simply because it is familiar. Choose it when reliable controller-based access control and direct system control matter more than having the newest cloud interface. Compare other platforms when simplified remote administration, mobile credentials or a unified cloud security experience leads the project.
Product and Brand Clarity
Dormakaba, Keyscan and Aurora Are Related—but They Are Not the Same Term
Search note: “Key Scan” is a common spaced search variation, but the product family is styled Keyscan.
Buyers commonly use “Kaba access control,” “Dormakaba access control,” “Key Scan access control” and “Keyscan Aurora” as if they mean the same product. They do not.
dormakaba
dormakaba is the parent manufacturer. Its portfolio includes electronic access, door hardware, locks, readers, credentials, lodging products and other access solutions.
Keyscan
Keyscan is the commercial access-control family covered here. A Keyscan system may include door or elevator controllers, network and communication hardware, readers, credentials, power supplies and related components.
Keyscan Aurora
Aurora is the management software. Your administrators use it to manage people, credentials, access groups, schedules, doors, alarms, event history, reports and supported integrations.
This page is therefore about Dormakaba Keyscan access control systems running Aurora. It is not a review of every dormakaba or former Kaba access-control product.
For current product specifications, use dormakaba's Keyscan Aurora software page, CA Series door-controller page and the exact product data for your proposed hardware.
Our Review Position
Keyscan Is Better Than Its Age Suggests—and More Involved Than Its Sales Story Suggests
This Keyscan access control review does not grade the system on age. Keyscan is often dismissed as an older on-premises platform, but that is an incomplete reading of the product.
Aurora supports the everyday work expected from commercial access control and can extend into lockdown, anti-passback, elevator control, Active Directory, video, intrusion, visitor management, wireless locks, web access and custom integrations. Current Aurora 2.x documentation also includes newer controller support and mobile-credential options.
The part a feature list does not show is what your team must own. Keyscan may involve controllers, network modules, communication wiring, Windows services, a database, client access, optional web modules and licensed integrations. Those pieces can work well, but they must be documented and supported as one system.
Tom's buyer-level view is simple: Keyscan deserves consideration when you want durable commercial access control and are willing to support the system behind the doors. Zach's field view is equally direct: the hardware is understandable and serviceable, but technicians need an accurate controller and communication map before they touch a live site.
That is the balance of this review—solid field hardware and useful access-control depth, with more IT and administrative responsibility than most cloud-first alternatives.
Evidence Register
What Umbrella Has Actually Done With Keyscan
We distinguish installed work from service work and design work. A proposal is not an installation.
| Evidence type | Umbrella experience | What you can take from it |
|---|---|---|
| Training and certification | Formal Keyscan product and technician training | We understand the intended design, programming and support model |
| Installation and expansion | Multi-door school expansion with conduit, cabling, readers, locks, door preparation, controllers and Aurora activation | Direct evidence of field sequencing, compatibility and expansion dependencies |
| Inherited-system service and migration | Commercial and nonprofit sites where controller hardware remained while management, communications or lifecycle problems had to be evaluated | Direct evidence of takeover risk, live-door continuity and migration planning |
| Engineering and preconstruction | Multi-site industrial design covering controllers, anti-passback, mustering, directory integration and reporting | Evidence of requirements and architecture work—not production performance |
Evidence boundary
The large industrial design discussed below was postponed before installation. We use it to explain requirement discovery and system design. We do not present it as a completed Keyscan installation.
That distinction protects you from a common problem in manufacturer content: proposals, training and completed projects are often blended into one vague claim of “experience.”
Field Experience 1
Expanding Keyscan in an Active School
Umbrella expanded an operating school system with new controlled openings, conduit, cabling, readers, locking hardware, door preparation and controller work tied into the existing Keyscan environment.
The important lesson was not whether the reader could be mounted. It was whether the entire opening could be turned over and administered on schedule.
- Existing Wiegand readers could remain in service with the right configuration, but that did not give them new Bluetooth or mobile-credential capabilities.
- Board capacity, Aurora readiness and activation timing had to be confirmed before new doors became usable.
- A wired opening was not finished until the controller, software and locking hardware were commissioned together.
- One missing strike component delayed completion even though the access-control design was otherwise sound.
For a security manager, this means the door schedule must include hardware, controller and software status—not just an installation percentage. For IT, it means the Aurora and communication path must be ready before field crews call the opening complete.
Our takeaway: Keyscan expansion is manageable. The risk comes from treating an existing system as fully documented when it is not.
Field Experience 2
When the Keyscan Hardware Is Still Working but the System Is Not Healthy
At an inherited commercial site, Keyscan controller hardware continued to operate while the management side of the system no longer worked correctly. Some doors still recognized existing credentials, which made the system look healthier than it was.
The problem became obvious when the customer needed to administer it. Could they add or remove a person? Change a schedule? Retrieve reliable event history? Diagnose a communication failure? Recover the database?
This is a critical point for IT directors and business owners: doors unlocking today is not proof that the access-control system is supportable. Local controllers can continue using downloaded rules while the server, software or communication path is failing.
We evaluated whether repair would create a stable lifecycle path or merely postpone a migration. The customer ultimately chose another platform. That was not a blanket verdict against Keyscan. It was the right decision for an inherited system whose complete operating environment no longer matched the customer's needs.
Field Experience 3
Migrating a Live Facility Without Losing Door Control
Umbrella also migrated a nonprofit facility away from an inherited Keyscan system. The work included existing communication wiring, controller replacement, reader changes, programming and keeping critical openings available through the cutover.
The migration could not be planned only at the head end. Main entrances, internal shelter doors, stairs, staff-controlled areas and basement access had different operational importance. Each door needed a cutover sequence, a test and a fallback.
Three lessons apply whether you keep Keyscan or replace it:
- Keyscan field hardware can remain operational for years after the original installation.
- Good labels, drawings and credential records determine whether another integrator can take over safely.
- Migration risk lives at each opening—not just in the server room.
Our takeaway: Before replacing an existing Keyscan access control system, document what is healthy, what can be reused and what the facility must support for the next five to ten years.
Field Experience 4
Engineering Keyscan for a Regulated Multi-Site Industrial Environment
Umbrella designed a Keyscan Aurora approach for a multi-site industrial customer after a lighter cloud system could not meet the customer's operating requirements.
The discussion covered multiple controller locations, anti-passback, emergency mustering, Active Directory, reporting, database access, inter-site communications and planned downtime. Keyscan gave us a more appropriate platform for that level of design work.
But a product page saying “anti-passback” or “reporting” was not enough. The customer's written security procedure depended on exact behavior: how presence was calculated, who could reset status, what data was available in real time and what happened if the server or network was unavailable.
The project was postponed before installation, so we do not claim field performance. The lesson remains useful: if a Keyscan feature supports a regulated, emergency or compliance process, make the integrator demonstrate the complete procedure before the purchase order is approved.
Strengths
Where Keyscan Access Control Performs Well
Practical controller hardware
Keyscan door controllers follow familiar commercial access-control logic. Readers, locks, contacts, request-to-exit devices, inputs, outputs, power and communications are visible and serviceable. Zach considers the hardware understandable to install and troubleshoot when the cabinet and documentation are clean.
Local door operation
Controllers store rules and can continue making local access decisions when the management workstation is unavailable. That resilience matters in schools, factories and other facilities where a server interruption should not stop normal badge access.
It does not eliminate the need to monitor communications, recover event history or maintain the server. It protects door operation; it does not remove system administration.
A good path for existing Keyscan sites
If your panels, wiring, locks and readers are healthy, an Aurora upgrade or controlled expansion may cost less and disrupt less than a complete replacement. A lifecycle assessment should come before a rip-and-replace recommendation.
Depth beyond basic card access
Current dormakaba documentation lists lockdown, elevator control, VMS, visitor and intrusion integrations, Active Directory, mobile credentials, wireless and offline locks, web access, SQL expansion and API/SDK options. Those capabilities give Keyscan room to serve more demanding facilities.
Treat each as a configuration to verify—not a promise that every installed system already includes it.
Direct IT control
Some IT departments prefer to control the server, database, backups, network access and upgrade timing. Keyscan fits that operating model better than systems that place most control in a manufacturer's cloud.
For customers who do not want to host Aurora themselves, dormakaba also documents Keyscan Hosted Services. Hosted Aurora and a cloud-native product are not the same design; compare responsibilities and administrator capabilities carefully.
Cautions
Where We Slow Down With Keyscan
Readers and credentials
An existing panel accepting a reader connection does not prove that the reader will support your cards, fobs or phones. Panel interface, reader technology, credential frequency and credential format are separate decisions.
The current K-SMART3 reader is a 13.56 MHz smart-card and mobile-ready reader. If your facility still uses legacy 125 kHz prox cards, plan for a different reader, a multi-technology transition or new credentials. Do not discover that conflict after readers are mounted.
Server and database responsibility
The traditional Aurora deployment places real work on IT or the service provider:
- Windows and database support
- Backups and recovery testing
- Aurora services and version compatibility
- Network and firewall coordination
- Client and web access
- Upgrade planning and software licensing
- Secure custody of administrative credentials
A server migration is an access-control project. It should have a rollback plan, verified backups, controller communication tests and door-by-door acceptance—not just a new virtual machine.
More components to document
Depending on the system, Keyscan may include door controllers, communication modules, inter-controller wiring, servers, databases, client workstations, web modules and integration services. The design can be dependable, but undocumented dependencies make future service slower and riskier.
A more traditional administrator experience
Aurora can manage serious access-control work, but its screens and reporting process may feel more deliberate than a newer cloud platform. That is not automatically a problem. It becomes one when administrators were promised consumer-app simplicity and were never trained on the real workflows.
Before selection, have the person who will run the system add a user, revoke a credential, change a schedule, respond to a door alarm and produce an investigation report.
“Integration” needs a defined outcome
An integration name does not tell you what appears on screen, how failures are reported or which system is authoritative. Define whether you need event linking, live video call-up, synchronized playback, visitor synchronization, directory provisioning or a true unified workflow. Then test that exact outcome.
Controllers and Architecture
Keyscan's Hardware Is Straightforward; the System Topology Needs Engineering
Keyscan CA Series controllers are available for different door and reader counts, and the controller handles local door decisions from downloaded programming. That part is straightforward. The communication and support path around it is where inherited systems often become difficult.
What should be documented
- Every controlled opening and the controller serving it
- Used and reserved controller capacity
- Reader, lock, contact and request-to-exit connections
- Input/output and relay assignments
- Controller-to-controller and network communication paths
- Cabinet power, battery and grounding
- IP addresses, network modules and firewall requirements
- Aurora server, database, services and client locations
- Software, firmware, licensing and backup status
Communication planning
Some Keyscan environments use shared buses or chained communication arrangements. Those designs can work well, but a bad termination, failed device or undocumented field change may affect more than one controller. A technician needs the topology before troubleshooting begins.
The cabinet still matters
Clean wire routing, labels, service loops, documented power and an accurate door schedule determine whether the system can be supported quickly. No software feature can compensate for a cabinet nobody can trace.
Readers and Credentials
Keyscan Credential Planning Must Start Before Reader Selection
Do not choose readers by appearance or by the word “compatible.” Start with the credentials your people use today and the credentials you want them to use later.
Inventory:
- Every card, fob and mobile credential in circulation
- Credential frequency, technology and bit format
- Readers that must remain during a phased migration
- Employees, students, contractors, visitors and temporary users
- Phone replacement, revocation and offboarding procedures
- Higher-security areas that need card-plus-PIN or stronger credentials
The K-SMART3 issue in plain English
K-SMART3 supports current Keyscan smart-card and mobile-credential options. It is not a legacy 125 kHz prox reader. If you replace old readers without addressing credentials, existing badges may stop working.
The right transition may be new credentials, multi-technology readers or a staged conversion. Decide that before procurement.
Wiegand compatibility is not the finish line
An older reader may communicate with a Keyscan controller through Wiegand. That does not make the credential more secure, add mobile access or guarantee future portability. Reuse can protect the schedule and budget, but it should support a defined credential plan rather than preserve an old technology indefinitely.
Aurora Software
Aurora Is Capable, but the Administrator Experience Is Traditional
Aurora is the management layer.
Controllers keep making local door decisions; Aurora is where administrators manage people, rules, events and reports.
Keyscan Aurora access control software manages people, credentials, access groups, schedules, doors, alarms, transactions, maps, reports and supported integrations across Keyscan controllers and sites.
What we like
- Central administration across multiple controllers and locations
- Local controller operation when the management workstation is unavailable
- Detailed access groups, schedules and door commands
- Event history and reporting for investigations and audits
- Paths for web access, SQL expansion and third-party integrations
- Support for current CA and KC controller families, subject to version and hardware validation
What we test with the actual administrator
- Adding a new employee and assigning the correct doors
- Disabling a person immediately
- Replacing a lost card or phone
- Creating a temporary contractor schedule
- Locking or unlocking a group of doors
- Finding a door-forced or access-denied event
- Exporting an executive, HR or compliance report
- Confirming the response after a server or communication interruption
If those tasks require undocumented technician knowledge, the project is not ready for turnover.
Reporting reality
Aurora can produce useful reports. The practical test is whether your administrator can produce the required report accurately and quickly.
A monthly audit report is different from a report requested during an employee investigation or emergency. Build representative reports during acceptance testing. Do not wait for the first incident to find out that fields, filters or permissions were misunderstood.
Emergency Functions and Integrations
Anti-Passback, Lockdown and Mustering Must Be Defined as Workflows
These terms sound complete in a proposal. They are not complete until the people, doors, exceptions and failure conditions are defined.
Anti-passback
Specify entry and exit readers, local or global behavior, reset authority, time-based forgiveness, multi-site rules and emergency exceptions. Then test the behavior with real credentials.
Lockdown
Specify which doors lock, which remain accessible, who can initiate and clear the command, how readers communicate status, how first responders enter and what happens during a communication failure.
Emergency mustering
Specify how the system determines who is present, whether exit reads are reliable, how visitors are handled, where the roll-call report is available and what staff do if the primary server or network is unavailable.
Video integration
Decide whether the security team needs event links, live camera call-up, synchronized playback, alarm verification or one combined investigation screen. Those are different deliverables.
Directory integration
Define which fields enter Aurora, how often they synchronize, which system is authoritative, how terminated users are disabled and how a failed synchronization is reported.
Keyscan may provide the building blocks. Your acceptance test must prove the finished procedure.
Training and Support
Keyscan Is Supportable When the Integrator and Documentation Are Strong
Zach found the controller logic learnable and practical through Keyscan training. Certification helps, but the long-term support quality still depends on the site documentation and the integrator's field discipline.
Your turnover package should include:
- As-built drawings and a door schedule
- Controller, communication and network topology
- Server, database and service documentation
- Reader and credential inventory
- Software, firmware and licensing records
- Backups and a tested recovery procedure
- Administrative credentials held under customer control
- Manufacturer and integrator escalation contacts
- Administrator training based on your real operating procedures
A generic manual is not training. Your administrator should be able to issue and revoke credentials, change access, handle a lost badge, investigate events and escalate a problem without guessing.
Best Fit
Who Keyscan Aurora Usually Fits Best
Schools and institutional facilities
Keyscan can fit campuses that want hardwired doors, local controller operation, schedules, lockdown functions and a system that can grow in place. Confirm emergency procedures, expansion capacity and credential strategy before standardizing.
Industrial and manufacturing sites
Gates, restricted rooms, shift schedules, anti-passback and detailed reporting can make Keyscan relevant. Regulated requirements should be demonstrated with the exact controller and software configuration.
Existing Keyscan customers
Healthy panels, wiring and locks may justify an upgrade or expansion rather than replacement. Start with controller health, Aurora version, server support, reader compatibility, credentials, documentation and the next five years of requirements.
Commercial buildings with stable IT support
Keyscan fits companies comfortable supporting a Windows and database-based system or contracting that responsibility to a qualified provider.
Multi-building environments
Aurora can manage multiple controllers and sites. Confirm network communications, remote administration, database location and the support response for each facility.
Poor Fit
When We Would Compare Other Platforms First
Mobile-first administration is the top priority
If leaders expect most user and administrator work to happen in a polished mobile app, compare Keyscan with cloud-native access-control platforms before deciding.
Nobody owns the server
If IT does not want responsibility for Windows, the database, backups, services or upgrades, a traditional Aurora deployment creates an avoidable support gap. Compare hosted Aurora with true cloud-native systems and document who owns each task.
One unified cloud interface is mandatory
If access control, video, intercom and visitor management must operate in one modern cloud interface, verify the actual Keyscan integration experience. A supported integration is not always a unified operating screen.
The project is very small and simple
Keyscan may be more system than a single small office needs. A simpler platform can reduce infrastructure and training if the customer does not need Aurora's depth.
Leadership expects plug-and-play expansion
Keyscan can expand, but controller capacity, communications, server readiness, licensing, credentials and commissioning still have to be planned. Expansion is not just adding another reader.
Comparison
Keyscan Compared With Other Access Control Platforms
| Comparison | The buyer decision |
|---|---|
| Keyscan vs. Avigilon Alta | Choose Keyscan for conventional controller ownership and an established on-premises path. Put Alta ahead when mobile-first cloud administration and a modern reader experience are more important. |
| Keyscan vs. Brivo | Brivo offers a more cloud-native management model. Keyscan gives IT more direct control of the traditional system environment. |
| Keyscan vs. Axis | Axis is compelling when IP architecture, cybersecurity, cameras and open infrastructure shape the project. Keyscan is more familiar to teams that want conventional access-control panels and Aurora administration. |
| Keyscan vs. Genetec Synergis | Genetec is the deeper enterprise and unified-security platform. Keyscan can be easier to own where that scale and complexity are unnecessary. |
| Keyscan vs. LenelS2 OnGuard | Both can serve on-premises environments. OnGuard belongs in larger enterprise and complex installed-base decisions; Keyscan often fits small and mid-sized institutional or commercial environments. |
| Keyscan vs. PDK | PDK is lighter and cloud-first. Keyscan brings a more traditional controller and software environment with greater IT and administrative responsibility. |
Continue comparing
- Avigilon Access Control Review
- Brivo Access Control Review
- Axis Communications Access Control Review
- Genetec Security Center and Synergis Review
- LenelS2 OnGuard Access Control Review
- PDK Access Control Review
Decision-Team Questions
What Each Department Should Ask Before Choosing Keyscan
Facilities and security
- Which doors, gates, elevators and restricted areas are included?
- Which openings must keep operating during a network or server interruption?
- What must happen during lockdown, anti-passback and emergency exceptions?
- Is mustering part of a written procedure?
- Which alarms and reports must be available during an incident?
IT and cybersecurity
- Where will Aurora, its database and communication services run?
- Who owns backups, patching, recovery and upgrades?
- Which ports, services and remote connections are required?
- Which administrator roles, authentication controls and directory integrations are included?
- How will controller and software vulnerabilities be communicated and remediated?
HR and administration
- Who creates, changes and terminates credentials?
- What happens when an employee changes phones or leaves?
- Which reports are needed, how often and for how long?
- Which departments can see people, credentials and event history?
- Can administrators complete common tasks without technician support?
Procurement and leadership
- Which features are included, licensed separately or dependent on another system?
- Who provides first-line support and what response is contracted?
- Who controls the software licenses, passwords, backups and documentation?
- Can serviceable readers, wiring, locks or controllers be reused?
- What condition would force a future migration?
Installation and Expansion Checklist
What Umbrella Would Verify Before Installing or Expanding Keyscan
- Survey every opening and door-hardware condition
- Inventory panels, modules, readers, locks and power supplies
- Document credential technologies, frequencies and formats
- Confirm controller capacity and expansion reserve
- Map controller, network and communication topology
- Validate the Aurora server, database and client design
- Confirm the software version, licenses and upgrade path
- Build and test required reports
- Demonstrate lockdown, anti-passback and mustering procedures
- Define video, intrusion, directory, visitor and elevator integrations
- Confirm mobile-credential issuance, phone replacement and revocation
- Plan cutover and rollback by door priority
- Deliver labels, as-builts, passwords, backups and administrator training
Use Umbrella's Access Control System Planning Guide and Commercial Access Control Installation Guide to turn those checks into a project scope.
What Has Changed
Keyscan Is Adding Modern Options Without Abandoning Its Traditional Core
Do not evaluate current Keyscan only from an old System VII or early Aurora installation.
Current dormakaba material describes Aurora 2.x, CA and KC controller support, mobile credentials, Aurora Web, hosted services, updated reader options and a broad set of integrations. Those improvements matter.
They do not automatically modernize an installed site. Your building may still have discontinued panels, legacy readers, 125 kHz credentials, unsupported Windows versions or undocumented communication hardware. In March 2026, dormakaba published an updated list of discontinued Keyscan software and hardware, which makes installed-base verification more important.
Always answer two questions separately:
- What does current Keyscan support?
- What does this specific installed or proposed system include?
The second answer is the one your team will operate.
Final Verdict
Our Honest Assessment of Dormakaba Keyscan Access Control
Keyscan remains a capable commercial access-control system. Its practical controller hardware, local door operation and Aurora feature set can serve schools, manufacturers, commercial buildings and existing Keyscan customers well.
The decision turns on responsibility. Someone must own the Aurora server or hosted-service relationship, database, communications, readers, credentials, reports, backups, documentation and support path. When those responsibilities are clear, Keyscan can remain stable and useful for years.
When they are not clear, the customer inherits a system that still opens doors but becomes harder to administer, investigate and recover.
Our recommendation is therefore conditional, not vague:
- Keep or expand Keyscan when the installed hardware is healthy, the credential plan is sound, the system is documented and the operating model fits your IT and security teams.
- Specify new Keyscan when you want established controller-based access control and accept the infrastructure that supports Aurora.
- Compare other platforms first when mobile-first administration, minimal IT overhead or one unified cloud security interface is the leading objective.
Keyscan earns a place in the shortlist. It does not earn the project until the exact system is proven against your doors, users, emergency procedures and support expectations.
Continue the Access Control Decision
- Independent Access Control System Manufacturer Reviews — compare Keyscan with other access-control platforms.
- Commercial Access Control Systems — understand the complete system beyond the manufacturer.
- Access Control System Planning Guide — define doors, credentials, users, schedules, integrations and support ownership.
- Access Control System Installation — plan readers, controllers, wiring, door hardware and commissioning.
- Cloud Access Control Systems — compare Aurora with cloud-first ownership.
- Physical Security System Manufacturer Reviews — connect access control with video, intercoms, alarms and infrastructure.
FAQs
Dormakaba Keyscan Access Control FAQs
What is a Keyscan access control system?
A Keyscan access control system is dormakaba's commercial controller-based platform for securing doors, gates and elevator floors. A complete system may include Keyscan controllers, communication hardware, readers, credentials, locking hardware, power supplies and Aurora management software.
What is Keyscan Aurora?
Keyscan Aurora is the software administrators use to manage people, credentials, access groups, schedules, doors, alarms, event history, reports and supported integrations across Keyscan controllers and sites.
Is Keyscan the same as Kaba access control?
Not exactly. Kaba was one of the companies that formed dormakaba. Today, dormakaba is the parent manufacturer, Keyscan is a commercial electronic access-control family and Aurora is the Keyscan management software. Searches for “Kaba access control” can also refer to other or older product families.
Is Keyscan access control cloud-based?
Traditional Aurora is Windows and database based. Aurora Web and Keyscan Hosted Services provide browser and hosted-management options, but they are not identical to a platform designed entirely around a manufacturer's cloud. Confirm who hosts, maintains and supports each component.
Can Keyscan work without the internet?
Keyscan controllers can use downloaded programming to make local door decisions, so normal badge access does not require a continuous internet connection. Test event storage, synchronization, alarms and administrator access during server, network and controller-communication failures.
Can existing readers and credentials be reused with Keyscan?
Sometimes. Existing wiring, locks and compatible readers may remain, but the controller interface, reader technology, credential frequency and credential format must all match. Compatibility should be confirmed by model and credential—not assumed from the existing brand name.
Does the Keyscan K-SMART3 reader support legacy 125 kHz prox cards?
K-SMART3 is a 13.56 MHz smart-card and mobile-ready reader. A site using 125 kHz prox credentials should plan for another reader, a multi-technology transition or new credentials rather than assuming existing cards will work.
Does Keyscan support mobile credentials?
Yes. Current Keyscan documentation includes mobile credentials for compatible readers and Aurora versions. Confirm reader models, credential type, enrollment, licensing, phone replacement and revocation before deployment.
Does Keyscan support anti-passback and lockdown?
Keyscan supports advanced access-control functions including anti-passback and lockdown capabilities. Document and demonstrate the required reset authority, exceptions, door behavior, reader feedback and failure response in the proposed configuration.
Can Keyscan be used for emergency mustering?
Keyscan events and integrations may support a mustering process, but a life-safety or regulated procedure requires more than a feature name. Validate entry and exit assumptions, visitor handling, report access, real-time availability and failure procedures.
Is Keyscan good for schools?
It can be. Keyscan fits schools that want hardwired controller-based access, local door operation, schedules and lockdown functions. Verify expansion capacity, emergency procedures, credentials, server responsibility and administrator training.
Is Keyscan good for manufacturing facilities?
It can be. Keyscan can support gates, restricted areas, shift schedules, anti-passback and reporting. Demonstrate contractor handling, emergency accountability and required reports before approval.
Is Keyscan better than Brivo or Avigilon Alta?
Not universally. Keyscan is the more traditional controller and Aurora-based option. Brivo and Avigilon Alta are more cloud-forward. The better choice depends on IT responsibility, mobile use, integrations, existing infrastructure and the desired administrator experience.
Should an existing Keyscan system be replaced?
Not automatically. Assess controller health, Aurora and server condition, readers, credentials, documentation, supportability, expansion needs and future operating goals. A healthy system may justify repair or expansion; an unsupported or poorly aligned system may justify migration.
Who should install and support Keyscan?
A qualified Keyscan access control installer should understand Keyscan controllers, Aurora, reader and credential compatibility, commercial door hardware, networking, databases and live-system migration. Keep licenses, passwords, backups and as-built documentation under customer control.
Final CTA
Already Have Keyscan—or Trying to Decide Whether You Should?
Umbrella can assess an existing Keyscan system, validate a proposed Aurora design, plan an expansion or compare Keyscan with cloud and enterprise alternatives.
We start with the work your people need to perform: securing doors, issuing credentials, investigating events, supporting the server and responding during an emergency. The manufacturer recommendation comes after those requirements.
Primary CTA: Request a Keyscan Access Control Assessment
https://umbrellasecurity.com/get-in-touch/
Secondary CTA: Compare Access Control Manufacturers
https://umbrellasecurity.com/access-control-system-manufacturer-reviews/
Phone: 630-270-3313
A manufacturer comes after the requirements
Already Have Keyscan—or Trying to Decide Whether You Should?
Umbrella can assess an existing Keyscan system, validate a proposed Aurora design, plan an expansion or compare Keyscan with cloud and enterprise alternatives.
We start with the work your people need to perform: securing doors, issuing credentials, investigating events, supporting the server and responding during an emergency. The manufacturer comes after those requirements.