Informational
Cloud Access Control vs Local Access Control
Explainer Guide
What It Means
Cloud access control usually means the site manages doors, users, or events through an online platform or app-based service. Local access control usually means the site manages the system on the device itself or through a local controller or on-premises platform. Some systems also blend the two.
| Question | Cloud Access Control | Local Access Control |
|---|---|---|
| Management style | Remote app or web-led administration | On-device, controller, or local platform management |
| Best fit | Simple remote-friendly sites | Heavier controller or site-specific access workflows |
| Key tradeoff | Convenience and remote visibility | Tighter local control and often deeper customisation |
How It Fits in a Real Installation
Cloud-style access can suit smaller distributed businesses or sites that want simple remote management. Local or on-premises access can suit sites that want tighter control, larger controller systems, or management that is less dependent on an outside service model.
Why It Matters
This matters because the choice affects internet reliance, remote management style, long-term licensing, and what the site expects from day-to-day administration. It is not only about whether a door opens. It is about how the site will live with the system afterward.
Common Misunderstandings
A common misunderstanding is assuming cloud automatically means better. For some sites it is simpler. For others, especially larger controller systems, local or on-premises management is the better operational fit.
Specify the operating model, not just 'cloud' or 'local'
| Requirement to document | Cloud-managed example | On-premises example |
|---|---|---|
| Door operation during WAN/server loss | Controller or terminal should keep the approved cached permissions; confirm model behaviour and event reconciliation. | Controllers should keep local decisions if the management server stops; confirm advanced/offline limitations. |
| Administration | Named tenant, MFA, least-privilege roles and an account recovery owner. | Dedicated server/client, administrator MFA where supported, backups and patch owner. |
| Ongoing cost | Per-door/device/user subscriptions, mobile credentials, support and data retention. | Server/OS, base and door licences, support, replacement and upgrade labour. |
| Network | Required outbound destinations, DNS/NTP, bandwidth, VLAN and vendor remote access. | Controller/server VLAN, firewall rules, remote support method and time source. |
| Exit plan | Credential/export capability, subscription expiry behaviour and device transfer. | Configuration/database backup, licence recovery and replacement-server procedure. |
Use a controller-backed professional platform
For the Hikvision 20-30 door examples in this guide cluster, use HikCentral Professional with the appropriate access-control base and expansion licences, not the lightweight HikCentral Access Control free tier advertised for up to 16 doors. Controllers, readers, locks, contacts and REX remain at each door zone; the management platform centralises people, access levels, events and operator workflow. Confirm software/server sizing, exact Australian licence names and offline behaviour before ordering.
Where to Go Next
Read the standalone-versus-networked guide next if you are still choosing the underlying system tier, or the time-attendance page if workforce reporting matters too.
Relevant SecurityWholesalers Product Areas
- Hikvision Access Control Base License Package - Useful when the site needs a proper software layer for users, schedules, event review, and central administration.
- Hik-Connect Team Mode 1 Door - Relevant where a smaller site wants cloud-style management for access control and time attendance.
- Hikvision DS-K2704X - A four-door controller with web-based setup and room to grow into a much larger system.
- Hikvision DS-K2702X-P - A strong fit when one or two doors need proper logs, schedules, and a real controller architecture.
Related Guides in This Series
Source References
Frequently Asked Questions
-
What does cloud versus local access control mean in plain English?
Cloud access is managed through an online service; local access is managed on-device or through local controllers and software.
-
Where does cloud versus local access control fit in a real installation?
Cloud is often attractive for simpler remote admin; local is often stronger for controller-heavy or more site-specific control.
-
Why does cloud versus local access control matter to a buyer or installer?
The choice affects remote admin, dependence on internet or subscriptions, and how the operator manages the system later.
-
What is useful to understand about cloud versus local access control?
Cloud is not automatically better; it is only better when the admin model actually suits the site.
-
When should a site move beyond the basic version of this?
A site moves beyond the simple version when it needs hybrid administration, larger controller architecture, or deeper on-site event control.
-
Which related guide should someone read next?
Read the standalone-versus-networked guide next if the tier is still undecided.
Review information
Content owner: SecurityWholesalers access control guide team. Revision: 17 July 2026. Use these examples as a starting point, then confirm the details against current product manuals, approved drawings and relevant authority requirements.
NCC access and egress | ACMA cabling requirements | OAIC biometric guidance | Access control definitions