Cloud-managed does not describe every part of the system.
A platform may manage cameras and doors in the cloud while recording video locally, executing door decisions at an onsite controller and using the WAN for administration.
Ask where each critical function occurs: credential validation, video recording, operator viewing, alerts, user management and updates. A single “cloud” label can hide different architecture and recurring obligations. Map the physical devices, local services, network routes and vendor-hosted services before comparing products.
Draw the path from device to operator.
Onsite devices
Identify cameras, readers, controllers, intercoms, bridge appliances, power supplies and any required local storage or server.
Network and power
Confirm switch ports, PoE, firewalls, DNS, uplink capacity, backup power, room access and who makes network changes.
Vendor services
Document hosted management, video storage, integrations, subscription tiers, support windows and the conditions for continued access.
Operator workflow
Determine who administers users and credentials, who investigates events and what training or role restrictions are required.
Show what data moves offsite. Video uploads, snapshots, event records and identity information may follow different paths. Vendor documentation and contract terms should identify those paths for the selected product.
Plan behavior during WAN, power and service interruptions.
Write the expected response as a test case. A claim of “offline operation” should identify which functions continue and how long the supporting local components remain powered.
Define access, retention and exit before subscribing.
Keep recovery information and sensitive settings in the organization’s approved secure system, with an owner who can reach the vendor when the usual administrator is unavailable.
Ask each proposer for the same architecture evidence.
Request a per-site diagram, list of local components, bandwidth assumptions, license schedule, offline behavior, retention settings, integrations and support responsibilities. Test one camera event, one door event and one administrative change across the full workflow before acceptance.
A product can be an excellent match for one property and a poor match for another. Treat cloud-managed, on-premises and hybrid designs as options to evaluate against the operation rather than a prescribed answer.
Common cloud-security questions.
Does cloud-managed mean no equipment onsite?
No. Cameras, controllers, readers, power and sometimes local recording or bridge devices remain at the facility.
Will doors stop working if the internet fails?
Behavior depends on the particular controller, credential configuration, power and product architecture. Test the actual installed system under an agreed outage scenario.
Does a subscription include all future storage and support?
Not necessarily. Confirm retention tier, camera or door license, hardware warranty, onsite service and renewal terms in writing.
Reference notes
- CISA, Require Multifactor Authentication: identity protection for remote access and business systems.
- Platform storage, offline behavior and terms must be verified against the selected manufacturer’s current documentation and agreement. This page is a planning guide, not a vendor specification.
Plan this with Terapixels.
Share your facility, existing systems and the decision you need to make. We will help identify the right scope and next step.
Discuss a project ↗