By SafePath Tech Solutions · Reviewed October 22, 2026
Compare the choices.
| Decision | On-site management | Cloud management |
|---|---|---|
| Administration | Customer-managed software; remote access depends on the design. | Hosted administration with local controllers operating doors. |
| Multiple locations | Enterprise functions may centralize sites and users. | A common portal can simplify distributed operations. |
| Maintenance | Assign server updates, backups, restoration, and support. | Review hosted service responsibilities plus local firmware and network care. |
| Offline decisions | Depend on cached controller permissions and configuration. | Depend on cached controller permissions and configuration. |
| Costs | Servers, software, support, maintenance, and staff time. | Subscriptions, door/user tiers, equipment, integrations, and support. |
The local controller still matters.
A cloud-managed door does not necessarily request cloud permission on every badge presentation. Many controllers decide locally using downloaded permissions and schedules. Specify cached capacity, event storage, schedule operation, and restart behavior for the selected equipment.
Existing permissions and new changes are different.
A credential may keep working while a new grant or revocation waits for connectivity. Verkada, for example, documents last-known-configuration operation during internet loss and synchronization afterward. Test new credentials, revocations, remote unlock, mobile use, and emergency actions separately on any proposed platform.
Make multi-site management meaningful.
A shared platform can simplify traveling staff, delegated site managers, door-health monitoring, and consistent schedules. It can also create overly broad access if roles are poorly designed. Demonstrate central oversight, local managers, visitors, time zones, and an employee transferring between buildings.
Separate SSO, provisioning, and door permissions.
SSO simplifies signing into management software. Provisioning creates or disables accounts. Physical-access rules determine which doors a credential opens. Ask which user types synchronize, how groups map to roles or door access, and how quickly a departing employee loses both portal and physical access. Check existing sessions and disconnected controllers.
Name the maintenance and recovery owners.
On-site software needs operating-system care, backups, restoration testing, certificates, and secure remote access. Hosted software needs defined service commitments, incident communications, administration, and data exports. Both require local power, controller firmware, network support, and functioning doors.
Hosting does not decide hardware flexibility.
Cloud and on-site platforms may use supported Mercury boards or vendor-specific panels. Readers, mobile services, card applications, and integrations create additional dependencies. Evaluate each layer and its migration path independently.
Compare lifecycle costs and interruption types.
Include door licenses, mobile credentials, directory/SSO tiers, integrations, support, training, and replacements. Ask what changes on subscription expiry. Internet loss, licensing expiry, and power failure are distinct scenarios. Confirm door and egress behavior with the responsible project professionals.
Put these answers in the proposal.
- Controller models and local decision behavior
- An internet/server/power/license interruption matrix
- SSO, provisioning, session, and door-access removal tests
- Site permissions, staff sharing, schedules, and reporting
- Maintenance, recovery, and support responsibilities
- Recurring costs, exports, and transition requirements
Test a user’s complete lifecycle.
In an authorized pilot, add a user, grant limited doors, change their role, remove access, and review the audit records. Test relevant disconnected-controller cases safely. Record what updates immediately and what waits for reconnection.
Questions worth asking.
Does cloud access control fail without internet?
Not necessarily. Local controllers may continue using stored permissions. New updates and remote functions can be unavailable; verify the exact design.
Does SSO mean a computer password opens the door?
Usually SSO refers to management-software login. Door credentials and permissions are separate, and any directory connection must be explicitly configured.
Can one platform manage every building?
Potentially. Review site limits, controllers, time zones, local autonomy, permissions, integrations, and licensing before standardizing.
Let’s make your next security decision a confident one.
A new facility. An aging system. A challenge you need to solve. Start here.