On-premise vs cloud vs hybrid VMS for public bodies in India

What are on-premise, cloud and hybrid VMS?

On-premise, cloud and hybrid describe where the VMS software runs and where the video is recorded. In an on-premise system, recording servers and storage sit in the owner's own data centre or control room. In a cloud system, cameras send video over the internet or a private link to a provider, which records it and serves it back to users through a web or mobile client. In a hybrid system, video is recorded locally and the cloud is used for some combination of remote viewing, multi-site management, incident archive or backup.

The choice is not about features. Cloud and on-premise VMS products can both offer search, analytics and mobile access. It is about bandwidth, where the data lives, who controls it, what happens when the link fails, and how the money is spent over the contract.

How do on-premise, cloud and hybrid VMS compare?

On-premise gives the most control and the least dependence on the link, cloud gives the least hardware to run, and hybrid sits between them. The table compares the factors that usually decide the choice for a public body. ICCC means an integrated command and control centre, and API means the application programming interface a provider publishes for other systems to connect.

How much bandwidth does cloud recording need?

Continuous cloud recording needs upload capacity equal to the combined bitrate of every camera, every hour of the day. That is the opposite of normal office internet use, which is mostly download.

The arithmetic is simple. If each camera streams at 4 megabits per second, 100 cameras need about 400 megabits per second of sustained upload, before any headroom. Each such camera also produces about 43 gigabytes a day, since 4 megabits per second for 86,400 seconds is 345,600 megabits. Real bitrates vary with resolution, codec (H.265 usually needs less than H.264 for the same picture), frame rate and how busy the scene is, so the numbers should come from the actual camera settings.

For a city spread across many junctions, or a campus on a shared link, that upload is often the deciding cost. It is also a security question. MeitY's advisory of 11 March 2024 asks government bodies to keep CCTV networks isolated from public networks where possible, and otherwise to use network segmentation, a secure tunnel or VPN (virtual private network), or a dedicated leased line, and to avoid exposing the system directly to the internet. A cloud design has to meet those expectations on every camera connection.

What do Indian government rules say about where CCTV video is stored?

MeitY's advisory of 11 March 2024 says the data storage of all CCTVs installed at government establishments and public places should be mandated to be within India, even if it is stored on cloud platforms. The advisory was sent to all ministries and departments and forwarded to the States by the Ministry of Home Affairs.

For cloud procurement more generally, MeitY empanels the cloud service offerings of cloud service providers (CSPs), and departments procure them through the Government e-Marketplace (GeM). MeitY's Guidelines for Procurement of Cloud Services list three empanelled deployment models: public cloud, virtual private cloud and government community cloud.

• Software as a service (SaaS) may only be offered from data centres audited and qualified by STQC under the cloud empanelment process
• The CSP is responsible for ensuring all data functions and processing are performed within the boundaries of India
• The CSP should not delete any data before 45 days from the expiry of the contract
• The CSP should provide backup that supports retention of at least 30 days, or longer as the department needs
• Departments must discover the managed service provider's exit prices, such as effort, bandwidth or unit rates for data transfer, in the procurement

How do retention and cost shape the choice?

Retention sets the storage, and storage drives cost in every model, so it should be fixed before comparing prices. MeitY's advisory asks for storage to be specified as a duration in days, based on operational need, rather than as a storage capacity.

The shape of the cost differs. On-premise spends most of its money at the start, on servers, storage, VMS licences, data centre space, power and cooling, and then pays for maintenance and an eventual hardware refresh. Cloud spends little at the start and charges a recurring fee, usually per camera and per retention period, plus the cost of the upload links. Hybrid pays for smaller amounts of both.

Because the shapes differ, a fair comparison is total cost over the same contract term, for the same cameras, the same retention and the same service levels, including links, maintenance and exit. A cloud quote that leaves out the upload links, or an on-premise quote that leaves out power, cooling and refresh, is not comparable.

When does a hybrid VMS make sense?

A hybrid VMS makes sense when video must keep recording through a link failure but some users need access from outside the control room. Recording stays on local servers or on camera edge storage. The cloud carries remote viewing, management of many small sites, or an archive of flagged incidents.

Interoperability is still maturing on the cloud side. ONVIF, the open industry forum for IP security product interfaces, released its cloud profile, Profile V, as a release candidate on 9 July 2026 and expects to finalise it by the end of 2026. Until it is final and products are listed as conformant, connecting cameras to a cloud VMS depends on each provider's own supported devices. A tender should ask for the list of supported camera models and firmware.

What should a public body's VMS tender say about hosting?

The tender should state the retention, data location, availability and exit terms it needs, and let bidders propose on-premise, cloud or hybrid against them.

• Retention in days for each camera group, at stated resolution and frame rate
• Video stored and processed within India, and for cloud, an offering empanelled by MeitY
• What must keep working if the link to the cloud or the data centre fails
• Network design for every camera link: isolation, VPN or leased line, and no direct internet exposure
• Upload bandwidth calculation submitted with the bid, and who pays for the links
• Total cost over the contract term, including links, maintenance, refresh and exit
• Export of video and audit logs in a usable format at exit, with a stated transition period

How Ahuva approaches VMS hosting

Ahuva's cloud and virtualisation scope covers private, public and hybrid cloud, with backup, disaster recovery and business continuity. Its data centre scope covers design, server, storage, virtualisation and HCI (hyperconverged infrastructure), with power, precision cooling and structured cabling, and its video surveillance scope includes IP surveillance, AI/ML (artificial intelligence and machine learning) analytics, automatic number plate recognition (ANPR) and centralised VMS. It holds ISO 27001:2022 for information security management, and its OEM (original equipment manufacturer) authorisations include HPE for server, storage and compute platforms.