Comparison
Cloud versus on-premise video management
The decision with the longest tail on a camera project, because it determines who can administer the system, what happens when the link drops, and what you are committed to paying years after installation. We install both, so there is nothing to sell you here.
The real question
Not which is better, but which failure you can live with
Both architectures work. Both are installed on serious commercial sites every day. The comparison is not a quality question, and a contractor who only ever recommends one of the two is telling you about their margin, not your building.
What actually separates them is where the single points of failure sit and who carries them. On-premise puts the risk in the building: the server, the disks, the backups and the updates are yours, and so is the consequence when one of them is neglected. Cloud moves the risk to the link and to the vendor: your video is administered from anywhere, and it depends on a connection you may not control and on a company continuing to exist and continuing to support the hardware you bought.
Neither is a smaller risk in the abstract. They are different risks, and the right answer is the one whose failure mode your organisation can actually absorb.
Where they differ
Six axes that decide it
Read these against your own operation instead of in general. Most sites find that two or three of the six dominate and the rest are close to neutral.
Retention
On-premise retention is bounded by the disks you bought and extending it means buying more. Cloud retention is usually a subscription tier, so it extends by paying, not by visiting. Where a regulator sets the period — a licensed cannabis premises in California must retain 90 days — the requirement is fixed and the question is only which architecture meets it more cheaply over the system's life.
Outage behaviour
An on-premise recorder keeps recording through an internet outage and you lose only remote access. A cloud system's behaviour depends on whether it buffers locally, and that varies by platform. This is the single most important thing to establish before choosing, and the answer is frequently not on the datasheet.
Cost shape
On-premise concentrates spend at installation and then costs maintenance and eventual replacement. Cloud spreads it into a subscription that continues for as long as you run the system. Capital against operating expenditure is often decided by your finance function, not by the security requirement, and that is a legitimate way to decide it.
Administration
Cloud is administered from a browser anywhere, which is decisive where several sites are managed by one small team or where nobody on site is technical. On-premise suits organisations with IT staff who would rather hold the system than depend on a vendor's console.
Data control and procurement rules
Some organisations cannot host video externally: procurement policy, a contractual requirement that data does not leave the site, or a security programme that forbids it. Government, defence-adjacent and some medical facilities regularly fall here, and where that applies it settles the question before any other axis is considered.
Evidence handling
How footage is exported, in what format, with what audit trail, and how quickly somebody can produce it when an insurer or an investigator asks. Cloud platforms are usually stronger at sharing a clip; local systems are usually stronger at bulk export. Worth testing instead of assuming, because it is the thing you will actually do under pressure.
When each is right
The cases where the answer is not close
Cloud is usually right when
- You run several sites administered by one team.
- There is nobody technical on site.
- Staff turnover means credentials and permissions change often.
- You would rather a predictable recurring cost than a large capital one.
- Remote access and clip sharing are things you do weekly, not after incidents.
On-premise is usually right when
- Your connectivity is poor or expensive.
- You have IT staff who will maintain it properly.
- Procurement or a security programme requires that video stays in the building.
- Retention requirements are long and the storage economics favour owning disks.
- The site is a single building, where the multi-site advantages of cloud do not apply.
What we will not do
Recommend a platform before seeing the site
We install both architectures and we do not have a house platform to move. What we will not do is name a product as the answer on the strength of a datasheet, or tell you which is right before we know your connectivity, who administers the system afterwards, what your retention obligation is and whether any procurement rule constrains where data can live. Those four answers decide it, and none is visible from a phone call.
We will also not promise that a given cloud platform keeps recording through an outage until we have confirmed it for that platform. It is the most commonly assumed capability in this category and the most variable in practice, and getting it wrong means discovering the gap at the worst possible moment.
For completeness on scope: we hold CSLB#976737 as a C-7 low voltage contractor and BSIS Alarm Company Operator licence ACO #7501, we work on commercial premises only and not on private residences, and we do not hold a C-10 or C-16, so we do not work on fire alarm systems; that is coordinated with your own licensed fire alarm contractor.
The middle case
The answer is genuinely close when
A single site with reasonable connectivity, moderate retention, and one competent administrator can be built either way and run well either way. On those projects the decision usually comes down to the cost shape your organisation prefers, and there is no security argument that should override that preference.
Whichever you choose, the infrastructure underneath is the same and it decides whether either works — see network cabling services for the pathways and PoE side, and commercial camera installation for how positions are designed before any platform is selected. If procurement rules apply to the equipment schedule, that filter comes first: what Section 889 says and who it binds.
Common questions
Cloud and on-premise questions
It depends entirely on the architecture, and it is the first question to ask a vendor, not an assumption to make. Some cloud platforms record to an on-site appliance or to storage inside the camera and upload when the link returns, which means an outage costs you the live view but not the footage. Others stream continuously and record nothing locally, which means an outage is a gap in your evidence. Both are sold as cloud video. Ask specifically what happens to recording during an outage, how long the local buffer lasts, and what happens when it fills.
RelatedRemote video monitoring
Cloud usually, and this is the case where the answer is least ambiguous. One console covering every building, consistent user permissions across sites, no travelling to a location to add a user or pull footage, and updates that arrive without a site visit — those advantages compound with each additional site, and they address the administrative burden that is the real cost of multi-site video. The counterweight is that the recurring cost also multiplies by site, so the calculation is worth doing over the years you expect to run the system, not for the first one.
RelatedRemote video monitoring
Yes, and on larger estates it is often the sensible answer rather than a compromise. A common shape is on-premise recording for continuous retention, with a cloud layer for remote access, alerting and sharing clips. That gives you local retention that does not depend on a link and remote administration that does not depend on being in the building. It is more to maintain than either alone, so it earns its place on sites where both requirements are real, not as a default.
RelatedRemote video monitoring
This is the question buyers ask last and should ask first. Get the answer in writing before you commit: how long footage remains accessible after a subscription lapses, in what format you can export it in bulk, and whether the cameras themselves are locked to that platform or will work with another system. Some platforms use hardware that only operates with their service, which turns a subscription decision into a hardware decision several years later. That is not a reason to avoid cloud, but it is a reason to know the answer at the start.
RelatedRemote video monitoring