The hardware outlives the cloud

A decade of camera-vendor shutdowns turned into one architectural rule — and why every Frigate user is already living by it.

Published May 8, 2026

Every few years, a smart-home vendor turns off a cloud and bricks somebody’s hardware. Wink went paid-subscription in May 2020 and locked out users who didn’t pay. Insteon shut its servers off in April 2022 with no warning — devices stopped working that morning. “Works with Nest” sunset in 2019 and broke a generation of integrations overnight. Belkin’s WeMo NetCam line was discontinued with no replacement path. The list runs longer every year.

The pattern is reliable enough to plan around: the hardware outlives the cloud.

Cameras are designed for a 7–10 year service life. The cloud they depend on has, empirically, a 4–6 year half-life. The mismatch is the entire failure mode of the consumer-camera category, and it is the thing every Frigate user has already routed around — whether they articulated it that way or not.

Why the math doesn’t work

A consumer camera sells for $80–$200, once. The cloud it talks to costs the vendor real money every month, forever. That is a margin problem dressed up as a feature, and it resolves in one of three ways:

  1. The cloud goes paid. Free becomes a teaser. The customer either pays a monthly fee that starts to exceed the camera’s purchase price, or they walk.
  2. The cloud gets cost-engineered down. Retention windows shrink. Resolution gets capped. Push alerts get rate-limited. The product the customer bought decays in place.
  3. The cloud gets shut down. Either the vendor exits the category, gets acquired by someone who doesn’t want the recurring cost, or quietly stops paying the bill.

None of these paths are surprises. They are the steady state of the business model.

The Frigate exit

Frigate is the architectural answer to all three failure modes simultaneously. The detection runs on a box you own. The recordings live on a disk you own. The cameras speak ONVIF and RTSP — open protocols that any future replacement camera will also speak. There is no vendor cloud to shut down because the system never depended on one.

The trade is real. You buy a mini-PC. You read a config file. You learn what a Coral TPU is. You spend an evening tuning thresholds (we wrote about that one here). The browser-tab simplicity of a vendor cam is gone, replaced by a pile of YAML.

What you get back is the only thing that matters at year seven: the system still works. No abrupt email about “exciting changes to your service.” No app-store update that removes a feature behind a paywall. The cameras you bought in 2024 and the install you finished in 2025 will still be running in 2031 because nothing in the loop is at the mercy of someone else’s quarterly review.

Why this constrains how we built ViewPane

ViewPane sits on top of Frigate, and the hardware-outlives-cloud rule is the constraint that shapes every architectural decision in the app:

  • No ViewPane cloud. If we ran a backend, we would be exactly the failure mode this post is about. The app talks to your Frigate, full stop. There is no “ViewPane service” to shut down.
  • No account system. Account systems exist to be retired. We don’t have one.
  • The push relay runs on your hardware. Most other companion apps in this category route notifications through a vendor cloud — which means the day the vendor stops paying that AWS bill, the alerts stop firing. Our relay is a tiny Docker container that runs alongside Frigate. The day we disappear, the relay keeps running.
  • Stable upstream API only. We talk to the public, documented Frigate API. If we got hit by a bus tomorrow, every install on every customer’s hardware keeps working. The app on your phone keeps working too. No fork-of-a-fork dependency that breaks the moment a single maintainer steps away.

The shorter version

If you have been running Frigate for two years, none of this is new — you already made this decision when you chose self-hosted over a cloud-cam ecosystem. We are writing it down because it is the load-bearing reason ViewPane exists at all. The companion-app market is full of well-designed apps that depend on backends nobody is promising will be around in 2030. We don’t want to be one of those apps. The architecture is the promise.