Cloud video (VSaaS) and hybrid VMS: when it makes sense for a business or chain

A classic camera system consists of a recorder (NVR) or server at each site, viewing software, and remote access configured site by site. For a single business this works well. For a chain with dozens of branches it quickly becomes complex: different versions, different passwords, disks that fail unnoticed and no consolidated view of system health.

What is VSaaS

VSaaS (Video Surveillance as a Service) is a model in which the management software, and sometimes the recording too, runs in the provider's cloud. The customer usually pays a monthly or annual subscription based on the number of cameras and the retention period, and gets one interface for all sites via browser and app.

Common features include camera health monitoring (offline camera, failed disk), central software updates, user and permission management by site and role, controlled sharing of video clips, and integrated analytics.

Hybrid: the common approach in practice

Uploading all video to the cloud in real time needs significant upload bandwidth, especially with high-resolution cameras. The common architecture is therefore hybrid: continuous recording stays local (on a recorder, server or in-camera card), while events, thumbnails, health data and on-demand clips go to the cloud.

This gives you the central management of the cloud without choking the branch internet line, and recording continues during an outage.

Advantages

• One status view for the whole chain: which branch is healthy and which is not.
• Fewer site visits: some faults are diagnosed and fixed remotely.
• Relatively simple expansion when new branches open.
• Centrally managed security updates.
• An operating-expense model instead of a large upfront capital investment.

Questions you must ask

• Where is the data stored (country, cloud provider), and what is the encryption policy at rest and in transit?
• What is the retention period, and what does extending it cost?
• What happens when a branch's internet goes down: does local recording continue?
• Does the solution lock you into one camera manufacturer, or support several?
• How do you export video for an investigation or for the authorities, and how long does it take?
• Who is responsible for what: the cloud provider, the installer, the IT department?

Regulation and privacy

When video is stored with an outside provider, it is part of a database the organisation is responsible for. Amendment 13 to Israel's Protection of Privacy Law, in force since 14 August 2025, sharpens the responsibility of the database "controller" and the Authority's enforcement powers. The contract with a cloud provider should clearly define security, permissions and deletion. It is also worth reviewing the Israel National Cyber Directorate's recommendations for internet-connected cameras.

When it fits

VSaaS or hybrid is especially suitable for retail chains, distributed offices, warehouses and sites without on-site IT staff. In an organisation with one large site and a strong IT team, a well-managed local system may be simpler and cheaper over time. The decision should be based on the number of sites, available bandwidth, retention requirements and who will maintain the system day to day.

A simple bandwidth calculation

To see why hybrid is common, do a rough calculation. A high-resolution camera with H.265 compression can use several megabits per second, depending on frame rate and scene activity. A branch with twenty cameras could need tens of megabits of continuous upload, more than many business lines provide, and that is before tills and telephony. Uploading only events and thumbnails needs a small fraction of that.

Three models compared

• Fully local: recording and management on site. Full control and low monthly cost, but multi-site management is awkward.
• Hybrid: local recording, management and health in the cloud. A good balance for most chains.
• Fully cloud: recording straight to the cloud. Very simple on site, but dependent on the internet line, and storage cost grows with time and resolution.

A practical migration process

• Map all sites: existing cameras, recorders, internet lines.
• Check which existing cameras the new solution supports and which need replacing.
• Pilot one site, including a deliberate internet disconnection test.
• Set up users and permissions by role: branch manager, security, management.
• Roll out in stages and document each site.

Permissions and sharing

A key benefit of central management is control over who sees what. A branch manager sees only their branch, security sees all branches, and management receives reports without video access. When an employee leaves, you remove the user in one place. Also define who may export clips, require a reason for each export and keep a log. Such settings support the Privacy Protection Authority's principle of limiting viewing permissions, and make responding to police or insurer requests orderly and documented.

Health alerts: the hidden value

Many systems "fail silently": a disk fills up or fails, a camera disconnects, or the recorder clock drifts. Central health monitoring alerts on these conditions so they are fixed before someone discovers there is no recording of an incident. For chains, this alone often justifies central management.

Long-term cost

When comparing quotes, calculate total cost over several years: hardware, installation, subscription, extended retention and service. A solution that is cheap at first may be more expensive over time, and vice versa.

Summary

The cloud does not replace professional design of cameras, infrastructure and network; it changes how they are managed. In multi-branch deployments, combining reliable local recording with central management is currently one of the most effective ways to keep a system healthy over time.