A keypad on the storeroom door and a card system across a whole building both decide who gets in, but they answer very different questions after the fact. Standalone vs networked access control is the choice between a lock that makes every decision on its own and a system where controllers, software and a database decide for many doors at once. This guide sets out what each can do, where each fits, and what stays the same either way.
What is the difference between standalone and networked access control?
A standalone lock stores its codes or cards in the device and is programmed at the door, so each door is managed separately. A networked system connects readers to controllers and central software, so you can add or remove users, change schedules, lock doors remotely and review an audit trail for every door from one place.
Standalone vs networked access control at a glance
The table compares the two architectures on the points that usually decide a job.
| Feature | Standalone lock or keypad | Networked system |
|---|---|---|
| Where decisions are made | In the lock or keypad itself | At the controller, using a central database |
| Adding or removing a user | At each door | Once, in the software |
| Audit trail | None, or stored in the device on some models | Every door, in one log |
| Remote lockout | Usually not possible | From the software |
| Best fit | One or a few doors, few users | Many doors, staff turnover, schedules |
How a standalone keypad or card lock works
A standalone unit combines the reader, the decision and often the lock in one device. It holds a list of PIN codes or card numbers and compares each entry against that list at the door. It needs no server and no network, which makes it quick to install and simple to explain to the owner.
The trade-off is that the door knows only what was programmed into it. Every change is made at that device, door by door. The GSA guidance on physical access control systems describes standalone systems as facility-centric and notes that they typically do not connect to enterprise networks.
The keypad door lock vs access control system question usually turns on that point. A keypad suits a storeroom, a gate or a single office with a handful of users who rarely change.
How a networked access control system works
A networked system splits the job into parts. In the GSA description, the reader reads the credential and passes its data to a control panel. The panel checks it against the credential holder data, makes the access decision, and sends the result to the access control server and the door.
The server, or the hosted software in a cloud system, is where people and credentials are enrolled, and the same guidance notes that it logs system events. One record for each person covers every door they are allowed through, on the schedule set for them.
Ask how the controller behaves if the link to the server drops. Many controllers keep a local copy of their credential data so doors keep working, but confirm that on the controller’s own documentation before you promise it.
Cloud access control vs on-premises software
Networked systems come in two broad forms. On-premises software runs on a server or appliance at the site. Cloud access control keeps the software and database with the provider, and the owner manages doors through a browser or an app.
- On-premises: the owner or their IT staff maintains the server, backups and updates, and remote management depends on their network setup.
- Cloud: no local server to maintain, and remote changes are built in, but management depends on the site’s internet connection and usually on a recurring subscription.
Either way, it is now an IT system. The GSA guidance calls for regular maintenance and patching of the components, so agree with the owner who handles updates and passwords before handover.
Credential management when people leave
Staff turnover is where the gap shows most. On a standalone keypad, removing one person safely can mean changing a shared code and telling everyone else the new one. On standalone card locks, the lost card has to be deleted at every door it opened.
On a networked system it is one change in the software. The GSA guidance also advises disabling invalid credentials promptly, and disabling records rather than deleting them so the audit data survives.
- Give each person their own credential, never a shared code.
- Remove or disable it the day they leave or report it lost.
- Review the user list on a regular schedule agreed with the owner.
Audit trails and remote lockout
The audit trail is often what moves an owner to a networked system. When something goes missing, a log of which credential opened which door and when answers the question a shared keypad code never can.
- Standalone: many units keep no log. Where a model does store events, someone has to retrieve them at the door, one lock at a time.
- Networked: events from every door land in one log that can be searched and exported.
- Remote lockout: a networked system can lock doors or suspend credentials from the software. A standalone lock changes only when someone reaches it.
Scaling from one door to many
A single standalone keypad is often the right answer, and it does not have to be the last one. The problem comes at the third or fourth door, when every staff change means walking the building with a programming card.
- Plan conduit or cable to each door during construction, even if only one door gets a reader now.
- Size the controller for the doors the owner expects, not only the doors installed today.
- Mount controllers in a secure room or enclosure; our guide to network rack cable management covers tidy rack layout.
- Where readers or controllers run on PoE, budget the switch as our PoE budget guide explains.
Power, locks and egress still apply
Neither architecture changes the hardware rules at the door. The lock still needs the right power supply, and the choice between fail safe and fail secure still decides what happens when power drops. Our maglock vs electric strike guide covers both.
Free egress is still required. Exit devices, request to exit sensors and fire alarm release work the same whether the door is standalone or networked; see our guide to the request to exit sensor. Check local code with the authority having jurisdiction before you lock any exit.
Where to find access control products
The access control category lists access control products, and the security hardware and accessories category and security wire and cable category list the parts that finish the install. All sit in the security, surveillance and control division.
For pricing and availability on a project, contact your sales representative through the Bursma contact page, or open a Bursma dealer account.
Frequently asked questions
Do keypad locks keep a log of who entered?
Many do not. Some standalone models store events in the device, but someone has to retrieve them at each door, and a shared code cannot show which person used it.
Can a standalone keypad be upgraded to a networked system?
Some standalone products can join a networked system later, but many cannot. Check the product documentation, and run cable to the door during construction so a reader and controller can be added.
Is cloud access control better than on-premises?
Neither is better on every job. Cloud removes the local server and adds built-in remote management; on-premises keeps the data on site under the owner’s own IT control.
What happens to networked access control if the network goes down?
It depends on the controller. Many keep a local copy of their credential data so doors keep working, while remote changes and live logging wait until the link returns.