Cloud-Based CCTV: Real Costs, Upload Speeds and AI

Cloud-based CCTV sends your camera footage over the internet to a provider's servers instead of a recorder on site. It suits businesses with many sites, full fibre and no one to look after a recorder. For one site with working cameras, recording on site and sending only alerts and clips to the cloud costs less, keeps recording when the internet drops and makes UK GDPR compliance simpler.

The deciding numbers are upload speed and the monthly fee per camera, and most guides skip both. Below we work them out for a typical 16-camera site, then look at where the AI should run, which is the part we build.

The three kinds of cloud CCTV

"Cloud CCTV" covers three designs that behave very differently when the internet is slow or down. Providers often sell it as VSaaS (video surveillance as a service). Here are the three next to the on-site recorder (an NVR, network video recorder, or a DVR for older analogue cameras) most UK businesses already have.

Verkada is the best-known hybrid. Its cameras store 30 days of continuous video on the camera and, with cloud backup turned on, copy it to the cloud on a schedule you set. When nobody is watching, its bandwidth guide says each camera sends only thumbnails and a few details about what it saw. A connector is the usual upgrade for a site that wants cloud access and wants to keep its cameras. Ask any provider which of the three you are buying, because the sales pages often use "cloud CCTV" for all of them.

How much upload speed cloud CCTV needs

More than many business lines can spare, if every camera records to the cloud around the clock. Upload is the slow direction of most UK connections, and video is the heaviest thing you can send up it.

Upload is measured in Mbps (megabits per second, the unit broadband is sold in), and published figures for one camera range widely. Videoloft's bandwidth table puts a 4MP camera (4 megapixels, a typical business camera) on H.265, a newer compression standard that makes video smaller, at 800 kbps, or 0.8 Mbps. Verkada lists 3 Mbps for the high-quality stream of its 5MP cameras and 4.5 Mbps for 4K. The difference is mostly compression and frame rate: a heavily compressed stream is smaller, and also softer when you need to read a number plate.

For 16 cameras recording all day to the cloud:

• At 0.8 Mbps each: 12.8 Mbps of upload, every second of every day.
• At 3 Mbps each: 48 Mbps, and about 15.5 TB of video a month.

Openreach says its superfast fibre-to-the-cabinet service (FTTC, the most common UK business line that is not full fibre) uploads at up to 15 Mbps. The compressed setup uses almost all of it, leaving little for card payments, phones or email. The full-quality one does not fit at all. Full fibre fixes this, and Ofcom's Spring 2026 update puts it within reach of 82% of UK homes, which leaves almost one in five without it. Business parks, rural yards and industrial units are often in that fifth.

Providers cut the load in three ways: recording only when there is motion, uploading at night, or sending a low-resolution stream and keeping full quality on site. Each is a compromise. Motion-only recording misses the minutes before an incident, which is often what the police ask for. Remote viewing of an on-site system uses upload too, but only while someone is watching: Verkada puts a live high-quality view of one 5MP camera at 3 Mbps.

What cloud CCTV costs against an on-site recorder

Cloud CCTV is priced per camera per month, and most UK providers do not publish a full price list. These are the published figures we could find, checked on 11 November 2026, before VAT unless stated. We convert at £1 = $1.34.

The headline prices hide the retention. Two days of storage is not enough for a business: incidents are often found a week later. Ask for the price at the retention you need, usually 30 days, and at the resolution your cameras actually record.

Five-year cost for 16 existing cameras

Here is the same 16-camera site four ways, keeping the cameras it already has. Before VAT and installation.

The NVR figure uses UK retail prices in November 2026: about £295 to £390 for a Hikvision 16-channel AcuSense recorder and £350 to £360 for an 8TB surveillance drive, both including VAT, after this year's rise in hard drive prices. Thirty days of 16 cameras at 0.8 Mbps fits on one 8TB drive; at 3 Mbps it needs two. Our Verkada price breakdown shows where the £18,300 comes from.

The cloud rows also leave out the line. If you are on FTTC and want continuous cloud recording, budget for a full fibre business line, or a second line just for the cameras.

What you get for the extra is real: no box to steal, one app across every site, and no drive to replace. For a business with ten sites and no IT person, that can be worth it. For one warehouse whose recorder works, it is mostly paying monthly for storage you already own.

Where the AI should run: camera, site or cloud

This matters more than where the video is stored. AI that tells a person from a fox, or spots someone in a yard at 3am, can run in three places, and each one sets what crosses the internet.

• In the camera. Modern business cameras, such as Hikvision's AcuSense range, detect people and vehicles on the camera itself. Cheap and offline, but limited to what the maker built in.
• On site, in a recorder or an AI box. The AI reads the streams on your network and sends out only the alert and the clip. Nothing needs a fast upload. Our AI security camera buying guide compares these routes in detail.
• In the cloud. The provider's servers analyse the video, which means the video has to get there first, at the upload figures above. It is usually sold per camera per month: Videoloft's AI add-ons start at $1.79 for smarter motion alerts and at $19.99 for number plate recognition, per camera, per month.

Cloud AI adds up. People counting, from $9.99 a month at Videoloft, comes to at least $9,590 (£7,160) on 16 cameras over five years, on top of the storage.

We build the on-site kind. For a UK CCTV security company we built real-time trespass and violence detection that runs on a server at each site: one RTX 5060 Ti graphics card, about £700 in November 2026, handles 15 to 20 cameras, and the footage stays on site, which keeps the GDPR side simple. The model we chose, X-CLIP, needs about 1GB of GPU memory and 0.02 seconds per check, so it does not need a data centre.

On-site AI scales further than most people expect. Angel Protection, a US school and hospital security firm, weighed the cloud and chose on site, because schools do not have the upload to send every camera out. Cheap processors decode the streams and run a motion check, and only frames with movement reach the graphics card, so the expensive part never sits idle. That cut their hardware cost by 90% across more than 1,000 cameras, alerts arrive about a second after a weapon appears, and only a timestamp and a cropped image ever leave the building. How we scaled it to 1,000 cameras explains the design.

Is cloud CCTV GDPR compliant?

It can be, and the work is mostly paperwork you already owe for any CCTV. Moving footage to the cloud adds three questions:

• A processor contract. You stay the controller of the footage; the provider processes it for you. UK GDPR Article 28 requires a written contract that says what it may do with the footage, how it keeps it secure and what happens when you leave.
• Where the footage is stored. UK and EU data centres are straightforward. If the provider or its hosting is in the US, the transfer is covered only when the US company is certified to the UK Extension of the EU-US Data Privacy Framework, known as the UK-US data bridge, or when you have another transfer safeguard in place. Ask, and get the answer in the contract.
• Retention that deletes itself. Set the cloud plan to the retention your policy states, usually 30 days, so footage is not kept longer than you need it. This is one thing cloud systems do well.

Adding AI raises the stakes more than the cloud does. The ICO expects a data protection impact assessment (DPIA, a written check of the risks and how you reduce them) for surveillance likely to be high risk, such as monitoring staff or using face recognition. Processing on site with only alerts leaving the building gives you a shorter DPIA, because less personal data moves. In the US there is no federal equivalent; check state law, especially for face recognition.

Is cloud CCTV more secure than an NVR?

They fail differently. A well-run cloud service patches itself and keeps footage away from whoever breaks into the building. But one breach at the provider can expose thousands of customers at once: in 2021 an attacker reached more than 150,000 live Verkada cameras, which led to a US Federal Trade Commission settlement in 2024, covered in our guide to whether Verkada is worth it.

An NVR's usual weakness is being put on the open internet so staff can view it from home, then never updated. Hikvision's CVE-2021-36260, a flaw that let anyone send commands to some cameras and recorders, was used by real attackers and is on the US government's list of known exploited vulnerabilities. The fix is cheap: keep the recorder off the open internet, view it through the maker's app or a VPN (a private, encrypted link), and update the firmware. An on-site AI box that reads the streams without the cameras ever talking to an outside server is easier to secure than either.

Which should you choose?

• One or two sites, working cameras, FTTC line: keep recording on site. Add AI there, in an AI recorder or an AI box, and send alerts to phones.
• Many sites, no IT staff, full fibre everywhere: a hybrid cloud system is worth pricing. Get the 5-year cost at 30 days' retention in writing.
• A site with no building or no line, such as construction: cloud cameras on 4G or 5G with local storage are often the only practical option.
• You need detection no product offers: run a custom model on site on the cameras you have. That is what our computer vision team builds, starting with a £4,000 to £6,000 ($5,400 to $8,000) feasibility study credited to the build.

Not sure which fits? Start with where your footage is today. If it is on a box in a cupboard, you already own the hard part, and AI can be added to it without a monthly fee per camera. Our weapon detection case study shows the same approach working at scale.

Questions

How much does cloud storage for CCTV cost in the UK?

Published prices start at about £4 to £5 per camera per month before VAT, for two days of storage at 2MP. Thirty days at 4MP costs more, and few providers publish that price, so ask for a quote at the retention and resolution you need.

Can I use cloud storage with my existing CCTV cameras?

Usually, through a cloud connector: a small box on your network that records your IP cameras and copies footage to the cloud. Older analogue cameras on a DVR need an encoder first, a box that turns their signal into network video. Check your upload speed before you sign, using the figures above.

Will an NVR work without the internet?

Yes. An NVR records to its own drives and keeps recording with the line down; you only lose remote viewing and phone alerts until it comes back. Hybrid cloud cameras also keep recording locally. Direct-to-cloud cameras do not, unless they have a memory card inside.

What are the disadvantages of cloud CCTV?

A monthly fee per camera for as long as you use it, a heavy load on your upload, gaps in the recording when the line drops, and a dependence on one provider for your footage. Ask what happens to your recordings if you cancel, and whether exporting footage costs extra.

Is cloud CCTV better than local storage?

For a business with several sites and no IT staff, often yes. For a single site with working cameras, usually no: an on-site recorder costs under £1,000 once, and AI can run beside it without sending video anywhere.