Scan the QR code, the app finds your recorder, video appears. No port forwarding, no static IP, no router settings. It is genuinely clever and it is why almost every DVR sold in the last decade ships with it switched on.
It also routes your camera footage through a server belonging to the company that made the box. That is the trade. Worth understanding before you accept it.
What the cloud option actually does
When you enable the cloud service, the recorder opens an outbound connection to a server run by the manufacturer and registers itself with its serial number. Because the connection was made from inside your network, your router allows the replies back without any configuration. That is the whole trick.
Open the app and scan the code, and the app asks that same server for the device matching the serial. The server already has a live connection to your recorder, so it either brokers a direct connection between your phone and the recorder by punching through both firewalls, or it relays the video through itself when that fails.
Which of the two you get is invisible from the app. Nobody tells you. On a mobile network behind carrier-grade NAT it is frequently the relay.
The problems with it
Speed
A relayed stream travels from your recorder to the manufacturer’s server and back down to your phone. Most of these servers sit in China, where the recorders are built. The round trip to Europe is long before the Great Firewall has taken its share.
I have tested apps that take over a minute to show a picture. Live video arrives with several seconds of lag behind it. Seeking through recorded footage turns into a waiting game, and pulling a clip off the recorder to hand to the police can take an afternoon.
A direct connection to your own recorder over your own line has none of that. The video takes the shortest path that exists.
Privacy
Video from your cameras passes through equipment you do not own, operated by a company you have no relationship with, under a jurisdiction you did not choose. Whether anybody looks is not the point. The capability exists and you have no way to audit it.
Some of these platforms have also been built badly. Research published in 2019 into the iLnkP2P cloud, used by millions of budget cameras and recorders, found device identifiers that could be enumerated and connections that carried no meaningful encryption, which meant footage and credentials were exposed to anyone who worked out the pattern. That was one platform among several, and it shipped under dozens of brand names.
My position has not changed on this. Video should travel between the two parties with an interest in it, not through a third party for the sake of convenience.
You are renting the connection
The cloud only works while the manufacturer keeps the server running. I have watched vendors quietly retire a cloud platform a year after clearing their stock, and watched others ignore international customers whose connectivity problems they had neither the tools nor the inclination to diagnose.
Some services also cap what you can do. Concurrent stream limits are common on the consumer tiers, so the recorder that shows four cameras at once on the local network shows you one at a time through the app.
When the server goes away, the recorder still works perfectly on your own network. You simply cannot reach it from outside any more, and there is nothing you can do about it.
So what should you use instead
A VPN into your own network is the right answer, and it has become far easier than it was when this page was first written.
Most decent routers will run a VPN server, and WireGuard in particular is fast enough on modest hardware to carry several camera streams. You connect the phone to your home network and then point the app at the recorder’s local address, exactly as if you were sitting in the house. The recorder is never exposed to the internet at all, and the traffic is encrypted end to end with nobody else in the path.
Speed is close to a direct connection. There is no relay in the path, just the encryption overhead, which costs almost nothing on modern hardware.
If you are going to port forward
Direct port forwarding gives you the speed without the third party, and we walk through it in port forwarding a Hikvision DVR or NVR.
Understand what it costs, though. An open port puts the recorder’s own software in front of the entire internet, and that software has a poor record. Hikvision’s command injection flaw in 2021 was rated 9.8 out of 10 and was exploited at scale against exactly the devices people had helpfully forwarded a port to. Other vendors have been no better.
If you do it, do it properly. Change every default password on the recorder before it goes near the internet, keep the firmware current, use non-standard external port numbers, and restrict inbound connections by source IP on the router if it supports it. Our default password directory exists partly because so many of these devices are still running the credentials they left the factory with.
Common questions
Is cloud DVR access safe?
It depends entirely on the platform, and you have no way of assessing which one your recorder uses. Several of the budget P2P clouds have been found to carry footage without proper encryption.
Why is my CCTV app so slow to connect?
Because the connection is probably being relayed through a server on the other side of the world rather than reaching your recorder directly.
Is port forwarding better than the cloud?
Faster and more private, but it exposes the recorder’s software to the internet. A VPN gives you the speed and the privacy without the exposure, and is the option I would choose.
What happens if the manufacturer shuts down the cloud service?
Remote access stops. The recorder carries on working on your own network, and you would need to set up port forwarding or a VPN to reach it from outside.
