NVR vs Cloud VMS: How Factory Video Actually Gets Stored (India)
For a mid-size Indian factory — ~20 cameras at 4MP H.265, 30-day retention — a local NVR with roughly 16–24 TB of surveillance HDD is the default: one-time hardware, no recurring bill, no upload-bandwidth dependence. Cloud VMS wins on off-site safety and remote access but needs sustained upload most Indian plants lack. Most land on hybrid.
The storage decision is where a camera project quietly becomes a cost project. Buy too little disk and your footage rolls over before an incident is reviewed; go all-cloud without checking your upload link and the system silently drops frames. This guide does the actual TB and INR math for an Indian plant floor, then lays out the trade-offs plainly.
The two ways to store factory video
Every deployment stores footage in one of two places — on a box in your plant, or in a data centre over the internet.
- Local NVR / DVR. A Network Video Recorder (IP cameras) or DVR (older analog/HDCVI cameras) sits in your control room with hard drives inside. Cameras stream to it over the LAN; footage stays on-premises. This is what the overwhelming majority of Indian factories already run.
- Cloud VMS. Cameras (or a bridge appliance) upload footage over your internet link to a cloud Video Management System. You watch and search from a browser or app; retention is a subscription, not a disk.
The split matters because they fail differently and they cost differently. Local is a capital cost that depreciates; cloud is an operating cost that recurs forever — and depends entirely on your upload pipe.
Storage sizing: how many TB for 20 cameras, 30 days?
Storage is just bitrate x time. The arithmetic is fixed: 1 Mbps of continuous video = ~10.8 GB per day (1 Mbit/s x 86,400 s/day ÷ 8 bits/byte = 10.8 GB), the same constant CCTV storage calculators use (example bandwidth/storage calculator). H.265 (HEVC) delivers roughly the same picture as the older H.264 at about half the bitrate, and "smart"/H.265+ scene-adaptive encoding can cut a static factory scene by a further 30–40%.
Typical indicative bitrates for continuous 24/7 recording, and what they mean for 20 cameras over 30 days:
| Camera setting (H.265, 24/7) | Bitrate/cam (indicative) | 1 camera/day | 20 cameras x 30 days |
|---|---|---|---|
| 2MP / 1080p | ~2 Mbps | ~21.6 GB | ~13 TB |
| 4MP | ~3 Mbps | ~32.4 GB | ~19 TB |
| 4MP with smart codec (H.265+) | ~1.5–2 Mbps | ~16–22 GB | ~10–13 TB |
| 8MP / 4K | ~6 Mbps | ~65 GB | ~39 TB |
Figures indicative (mid-2026); real bitrate swings with frame rate, scene motion, lighting and encoder. Add ~10–20% headroom and plan for RAID/overhead.
So a realistic mid-size floor — ~20 mixed 2–4MP cameras, H.265, 30-day continuous retention — needs roughly 16–24 TB of raw disk. Turn on smart-codec and drop overnight frame rate and you can push toward 12–14 TB. Move to 4K everywhere and 30-day retention alone crosses 35 TB. Continuous recording is the expensive assumption; motion-only recording can cut storage 40–70% but risks missing slow events — for a factory floor with near-constant activity, the saving is smaller than a retail shop would see.
The India cost math (indicative, mid-2026)
Local NVR — one-time capital
- NVR body (16–32 channel): entry units list from around ₹8,000, but a branded 32-channel recorder with adequate incoming bandwidth runs ~₹15,000–₹35,000 indicative (CP Plus NVR range).
- Surveillance HDD: an 8TB Seagate SkyHawk or WD Purple runs ~₹16,000–₹25,000 indicative (Seagate SkyHawk surveillance drives). For ~20 TB usable you need about three 8TB drives — roughly ₹50,000–₹70,000 in disk. Use surveillance-rated drives (built for 24/7 write), never desktop HDDs.
- All-in for a 20-camera plant: NVR + ~20 TB of drives + a PoE switch on a UPS lands in the low ₹80,000–₹1,20,000 band as a one-time spend (excluding cameras and cabling), then near-zero recurring cost until a drive fails (plan a replacement cycle of 3–5 years).
Cloud VMS — recurring operating cost
Cloud is priced per camera per month, scaling with resolution and retention. Continuous 30-day retention for 20 factory cameras sits well above entry-level home-camera plans (commonly ~₹99–₹249/camera/month, indicative). Indian cloud-CCTV pricing is largely quote-based, so treat ~₹150–₹600 per camera per month (indicative) as a planning band for continuous factory-grade retention and confirm with live vendor quotes: for 20 cameras that's roughly ₹3,000–₹12,000/month, i.e. ₹36,000–₹1,44,000 every year, forever. Over 3–5 years, cloud typically costs more than a local NVR — you are renting disk plus bandwidth plus resilience.
India's bandwidth reality — the deciding factor
Here is what quietly kills all-cloud plans on an Indian factory floor: upload, not download. Cameras push data up; your broadband is usually built to pull data down.
Twenty cameras at ~2–3 Mbps each is 40–60 Mbps of sustained upload, 24 hours a day, 7 days a week — not a burst, a constant firehose. Measured Indian wired-broadband upload sits in the mid-50s Mbps range on average, with download higher (indicative; the Telecom Regulatory Authority of India runs the crowdsourced MySpeed measurement portal, myspeed.trai.gov.in). But "average speed" is not "committed sustained upload": most business plans are asymmetric and contended, so a link that shows 50 Mbps on a speed test rarely holds 50 Mbps of upload continuously against everything else the plant is doing. Push all your cameras to the cloud and the VMS silently drops frame rate or resolution to fit the pipe — you find the gap only when you go looking for footage that isn't there.
This is why the pragmatic answer for most mid-size Indian plants is hybrid: record everything locally on the NVR (full quality, no bandwidth risk), and sync only a thin stream — clips, thumbnails, or a lower-resolution copy — to the cloud for off-site remote viewing and disaster backup. You get on-premises reliability plus the "watch from my phone" and "footage survives if the recorder is stolen or burns" benefits, without needing a 60 Mbps sustained uplink.
Local vs cloud vs hybrid: the trade-offs
| Local NVR/DVR | Cloud VMS | Hybrid | |
|---|---|---|---|
| Cost shape | One-time capex | Monthly opex, forever | Capex + smaller opex |
| Upload bandwidth needed | None (LAN only) | High, sustained 24/7 | Low (thin sync) |
| Survives on-site theft/fire? | No (box is on-site) | Yes | Yes (cloud copy) |
| Remote / phone access | Extra setup, port-forwarding | Native | Native |
| Footage lost if internet down | No | Yes (buffering helps) | No (local keeps recording) |
| 3–5 year total cost (20 cams) | Lower | Higher | Medium |
| Best for | Cost-sensitive single site | Multi-site, thin coverage | Most mid-size plants |
What a plant head should actually do
- Size disk before you buy the NVR. Decide retention (30 days is common; check if any compliance or insurance clause demands more) and pick drives for your real bitrate, not the box's max channel count.
- Test your upload speed at the plant, sustained, before committing to cloud — not a one-off speed test. If you can't hold your camera bitrate uphill 24/7, cloud is a trap; go local or hybrid.
- Keep footage as governed data. Worker video is personal data under India's Digital Personal Data Protection Act, 2023, which sets expectations for purpose, retention limits and notice (DPDP Act, MeitY). A retention window and access control aren't optional — and cloud storage adds cross-border and vendor-access questions to answer.
- Buy compliant cameras regardless of where you store. New CCTV sold or installed in India from 1 April 2026 must meet BIS/STQC Essential Requirements (BIS CRS CCTV guidelines, crsbis.in). Storage choice doesn't change the hardware rule.
- Keep a timestamped record for safety duties. The Factories Act, 1948 puts continuous duties on you around dangerous machinery and hazardous processes (India Code); retained video is evidence your controls were followed.
Storage sizing assumes you already know how many cameras go where — and that placement question is where projects most often go wrong. This is the gap Mama closes: you record a short phone walkthrough of the floor, and it reads the space — zones, sightlines, hazards — then returns a floor plan plus a camera-placement plan. From that you get the exact channel count and resolution mix, so your NVR-vs-cloud storage math starts from real numbers instead of a guess.
FAQ
How much storage do I need for 20 cameras for 30 days? Roughly 16–24 TB of raw surveillance HDD for ~20 mixed 2–4MP cameras recording continuously in H.265 with 30-day retention (indicative). Smart codec and lower night-time frame rates can bring it toward 12–14 TB; all-4K pushes it past 35 TB. Add 10–20% headroom.
Is cloud VMS cheaper than a local NVR? Usually not over 3–5 years for a single site. A local NVR plus ~20 TB of drives is a one-time spend in the ~₹80,000–₹1,20,000 band (indicative), while cloud recurs at roughly ₹150–₹600/camera/month for factory-grade continuous retention — ₹36,000–₹1,44,000 per year for 20 cameras, every year. Cloud earns its cost on multi-site and off-site resilience, not price.
Can Indian broadband handle all-cloud CCTV? Often not. Twenty cameras is 40–60 Mbps of sustained upload 24/7, and most Indian business links are asymmetric and contended — a 50 Mbps speed test rarely means 50 Mbps of continuous upload. Test sustained upload at the site first; if it can't hold, go local or hybrid.
Should I use H.265 or H.264? H.265 (HEVC) for storage — same picture quality at roughly half the bitrate of H.264, which nearly halves disk and bandwidth. Confirm your NVR and cameras both support H.265/H.265+; mixing can force a fallback to H.264 and blow up your storage estimate.
What retention period do Indian factories need? There's no single legal number for general factory CCTV, so 30 days is the common default; some insurers, customers (pharma/food audits) or site-security policies specify longer. Balance it against the DPDP Act's expectation to not keep personal data longer than needed — size disk for your actual policy, not the maximum the box allows.