Cloud VMS vs NVR — What Actually Changes When You Move Recording Off-Site
An NVR records in the building; a cloud VMS records somewhere else. That single difference decides what survives an outage, who owns the hardware, and what leaves the site.
An NVR is a box in the building that records the cameras on its network. A cloud video management system records somewhere else and manages the cameras over the internet. Everything else people argue about follows from that one difference, so it is worth being precise about what it actually changes.
Where the recording happens
With an NVR, video travels from the camera to a recorder on the same LAN. The path is short, the bandwidth is free, and nothing needs to leave the building for footage to exist.
With a cloud VMS, the video has to reach the recorder over the site's internet connection. That is the whole trade. Everything good about the cloud model and everything that can go wrong with it comes from moving that one hop off the local network and onto an uplink you share with the rest of the business.
A hybrid arrangement records locally and manages centrally: a box on site writes the footage, and the cloud provides the operator interface, user accounts, and search across locations. This is usually what people actually want when they say "cloud" — central management, local recording.
What happens when the internet drops
This is the question that separates the models, and it deserves a blunt answer.
An NVR keeps recording. It never needed the internet; you simply cannot reach it remotely until the link returns.
A pure cloud VMS stops recording. Footage from the outage window does not exist afterwards and cannot be recovered, because it was never written anywhere. Any vendor who is vague on this point is worth pressing.
An on-site recorder in a cloud-managed system keeps recording through the outage and uploads afterwards. Nevtech's site nodes and edge gateways both work this way, which is why outage behaviour is a deployment decision rather than a property of the product.
Who owns the hardware problem
An NVR is a computer with disks in it, and disks fail. Someone is responsible for noticing a degraded array, sourcing a replacement, and rebuilding it — and for the fact that a recorder bought today will be end-of-life while the cameras are still fine.
Cloud recording moves that work to the platform operator. You stop buying and replacing disks and start paying for storage as a service. Whether that is cheaper depends entirely on your retention window, which is the variable most people underestimate.
The honest framing is not "cheaper" but "different": capital expenditure and a maintenance obligation, versus operating expenditure and a dependency.
What leaves the site, and when
An NVR sends nothing out until someone views footage remotely. A cloud VMS sends every enabled camera's stream continuously, all day, whether or not anyone is watching.
That is the number to work out before committing: real per-camera bitrate multiplied by camera count, compared against measured upload — not the figure on the internet bill. Get it wrong and the failure is not a clean error message. It is dropped frames, fragmented recordings, and footage that turns out to be unusable exactly when it matters.
An on-site recorder changes this shape too: it uploads on demand and in the background rather than streaming everything live, which is what makes constrained and cellular sites viable at all.
What happens when you add a second site
One NVR is manageable. Five NVRs at five sites is five sets of credentials, five firmware versions, five port-forwarding arrangements, and no way to search across them.
This is where central management earns its keep, and it is independent of where recording happens. A cloud-managed deployment gives one login, one user directory, one place to grant a guard access to exactly the cameras they should see, and one search across every location.
If you only ever have one building, that advantage is small. If you have several — or expect to — it is usually the deciding factor.
How this maps to Nevtech
Nevtech VMS is a cloud VMS that does not force the recording question. Cameras can record in the cloud, or on a site node in the building — a box whose cameras record locally, where viewing on site is LAN-speed and recording continues through an internet outage — or through an edge gateway that records locally and uploads. The console is the same in every case.
Two consequences worth knowing. First, the platform reports coverage honestly: the playback timeline draws a gap where nothing was recorded rather than quietly closing the space, so an outage is visible as an outage instead of being discovered months later. Second, access is scoped per user — an operator can be restricted to specific sites or cameras and sees nothing from the rest, which is what makes one login across several buildings safe.
If you are weighing the two models, decide the outage question first. It is the one thing you cannot fix after the fact.