Cloud-first camera platforms have a clean origin story. You buy a Ring or a Nest, plug it in, hand the company $5/month per device, and never think about storage, NVRs, or RAID arrays. The footage lives somewhere else. When you need to find a clip, you open the app and scroll. For a while, that’s appealing.
Five years in, most of our clients reach the same conclusion: it was the wrong call. Either the bill has quietly grown to several hundred dollars a year, or the ISP went down at the worst moment, or the company changed the storage tier, or AI features they paid for started missing things, or — in a few memorable cases — a vendor sunset the device and bricked a $300 camera overnight.
Local-first NVR platforms — UniFi Protect, Synology Surveillance, BlueIris, Frigate — solve nearly every one of those problems, and they cost less over five years than the cloud subscriptions they replace. Here is why we install local NVRs on every meaningful surveillance job, and why we think any homeowner with more than two cameras should be doing the same.
The five-year subscription math
A typical Wasatch Front home with a Ring doorbell, three Stick Up Cams, and a couple of indoor cameras lands at six devices. Ring Protect Pro covers an unlimited number of devices on one address for ~$20/ month. That is $1,200 over five years for cloud storage and the AI features that gate replay and package detection.
For the same six cameras, a UniFi Cloud Gateway Ultra or a UNVR with appropriately-sized disk runs $400–$1,200 in hardware (depending on stream count and retention) and $0/month after that. We worked through the disk-sizing math in detail in the NVR storage post. The break-even on hardware vs subscription is roughly year two; everything past that is pure savings.
The same logic applies to Nest Aware, Arlo Secure, Wyze Cam Plus, and every other “security as a service” pricing model. We covered the broader trend in the smart-home subscription creep post — cameras are the worst offender of the bunch.
What you actually get from local recording
Footage when the internet is down
A cloud camera with no internet records nothing. The stream goes from the camera to the cloud and back to your phone; cut the middle out and the system stops working. ISP outages on the Wasatch Front are not frequent, but they are not rare either — a Comcast node fault, a fiber cut on Bangerter, a cable nick in a new Lehi neighborhood. We covered why you might add dual-WAN with cellular failover separately, but failover is about remote access. Local recording is what keeps the cameras themselves recording at all.
A local NVR records 24/7 to local disk regardless of what the WAN is doing. Internet comes back, the recordings are still there. Internet stays down, the recordings keep being made. The forensic value of surveillance footage tracks closely with whether it exists at all.
24/7 continuous recording, not motion-only
Cloud cameras are almost always motion-triggered to control bandwidth and storage costs. PIR sensors and pixel-change detectors miss things — we wrote about this in the Ring-misses-packages post and again from the camera-quality angle in the night footage post. When the camera is always recording, the question “what happened at 3:42 PM” has an answer regardless of whether the algorithm fired.
No bandwidth tax on the upload side
Six cloud cameras streaming at 2–4 Mbps each burn 12–24 Mbps of upload, continuously, on a home connection where upload is usually the constrained direction. On a 50/10 cable plan, that’s the entire upstream. Video calls suffer. Backups suffer. Anything else uploading suffers.
Local cameras stream to a switch on the same LAN. The only WAN traffic is the occasional remote-app session. Net upstream impact: under 1 Mbps average, and only when somebody is actually watching.
You own the footage
Cloud platforms control retention windows, deletion policies, who can request access, and what gets shared with law enforcement under what conditions. Some of that has been controversial — Ring’s old relationships with police departments, Amazon Sidewalk quietly opting devices into a mesh, retention tiers that change without notice.
A local NVR is yours. The footage sits on your disk, in your house, on your network. You decide retention. You decide who sees it. If law enforcement asks for clips, they ask you, and you produce what is relevant. For homeowners in Holladay, Park City, and other privacy-conscious neighborhoods, that alone is the reason we are called.
Higher resolution and better compression
Cloud platforms cap resolution and bitrate to keep upload and storage costs manageable. Most Ring and Nest streams sit at 1080p at modest bitrate. A local NVR happily stores 4K H.265 streams at full bitrate because the disk is on-prem and the link is gigabit. We worked through the megapixel-versus-detail tradeoff in detail — you cannot zoom into a license plate that wasn’t captured at high enough resolution to begin with.
What you give up
It would be dishonest to pretend local NVR is purely upside. The honest tradeoffs:
- Up-front cost. Hardware is $400–$2,000+ depending on camera count. Cloud platforms have a $0 day-one cost.
- Ethernet runs. PoE cameras need a cable to the switch. We covered cable choices in the Cat5e/Cat6/Cat6a post. On a retrofit this can be the most expensive line item, though MoCA and PoE-over-coax sometimes solve it without drywall work.
- You manage the disk. Drives die. Good NVRs alert you when SMART starts whispering; great installs use RAID and a UPS. We sized the UPS side in the rack UPS post.
- Setup is more involved. Plugging in a Ring is easier than commissioning UniFi Protect on a Cloud Gateway. That is where we come in.
None of those are dealbreakers; they are just the price of owning the system instead of renting it.
Where local NVR makes the most sense
Any home with three or more cameras
The break-even cost crosses cloud the moment camera count crosses three. Below three, a Ring two-pack on a subscription is fine. Above three, the math, the bandwidth, and the reliability all start tilting hard toward local.
STRs and revenue-bearing properties
We covered this at length in the Park City and Heber STR security post. If a guest disputes a damage claim or a noise complaint, the question is whether you have the clip. Cloud platforms will sometimes have it; sometimes the event triggered, sometimes it didn’t, sometimes the retention window already lapsed. A local NVR with 30–60 days of 24/7 recording always has it.
Anyone with privacy concerns
Mountain neighborhoods like Park City, Alpine, Holladay, and parts of Bountiful skew privacy-aware, and our clients there increasingly do not want Amazon, Google, or any third party in the loop. Local-only is the only honest answer.
Homes already running other on-prem infrastructure
If you already have a UniFi network, a managed switch, and a rack — see the new-build rack post for context — adding UniFi Protect on a Cloud Gateway is the path of least resistance. The dashboard is the same one you already use, the cameras PoE off the same switch, and the recordings live on the same gateway.
What we typically install
For a six-to-twelve camera Wasatch Front home, the package looks like:
- UniFi Cloud Gateway Ultra, Cloud Gateway Max, or UNVR depending on stream count and IDS needs — we picked through that decision in the gateway comparison post.
- G5 Bullet, G5 Turret, AI Pro, and G5 Doorbell Pro cameras as the situation demands. The camera-resolution guide walks through which lens for which scene.
- Disks sized for 30–60 days of 24/7 footage, using the NVR storage formula.
- A managed PoE switch in the rack — see managed vs unmanaged for why managed matters here.
- UPS power on the rack, sized via the rack UPS guide, so a flicker doesn’t crash a recording array.
Bottom line
Cloud cameras win on day-one simplicity and lose on everything else: cost over time, reliability when the ISP fails, footage quality, retention control, and privacy. For a home with more than two cameras, a local NVR pays for itself in two years and keeps paying back forever. The footage is there when you need it, the bandwidth is on your LAN where it belongs, and the company that sold you the camera cannot brick it from a thousand miles away.
Keystone Integration installs UniFi Protect and other local-NVR camera systems across Park City, Holladay, Draper, Heber City, and the rest of the Wasatch Front — replacing cloud subscriptions with cameras you actually own. See our full service list or get in touch to scope a system.