Every cloud smart home device you own is a bet that a company you don’t control will keep its servers running, keep its app updated, and keep its promises about your data. That bet has a bad track record. Insteon shut down overnight and bricked thousands of homes. Wink started charging a surprise monthly fee. Nest has quietly killed API after API. When the cloud goes, your “smart” home goes with it.
Running your smart home locally fixes this at the root. There are four concrete reasons it’s worth the effort:
- It keeps working when the internet doesn’t. ISP outage, DNS problem, the vendor’s servers down — none of it touches a local setup. Your lights, locks and automations just work.
- There’s no monthly fee. No Ring Protect, no Nabu Casa (unless you want it), no camera cloud storage subscription. You buy the hardware once.
- Your data stays in your house. Local voice never sends a recording to a server. Local cameras never upload a clip. Nothing is mined, sold, or used to train anything.
- Nobody can brick it from a boardroom. A local device with no cloud dependency can’t be discontinued out from under you. It does the same thing in ten years that it does today.
Home Assistant is the engine that makes this possible — it speaks the local protocols (Zigbee, Z-Wave, Matter, MQTT, ESPHome) that cloud gadgets try to hide behind their apps. The table below is the map: for each cloud service people most want to escape, it shows the local replacement, the hardware it actually takes, whether it runs fully offline, and how much work it is. Filter by category or search for your device.
| Cloud service you’re replacing | Local replacement | Hardware you need | 100% offline? | Effort |
|---|
“100% offline” means the feature keeps working with your internet physically unplugged. Partial means the core works locally but one piece (a weather forecast, a push notification to your phone while you’re away) still touches the internet. Effort is the realistic setup difficulty once Home Assistant is already running.
Cameras: the biggest win
Cloud cameras are the clearest case for going local, because the cloud is where they charge you and where your footage lives on someone else’s disk. The local answer is Frigate, an NVR (network video recorder) that runs alongside Home Assistant and does real-time object detection — person, car, animal — entirely on your own hardware. No subscription, no clips uploaded anywhere, and far faster notifications because nothing round-trips to a data centre.
The one requirement is a real camera instead of a cloud gadget: a PoE (Power over Ethernet) camera that speaks the open RTSP/ONVIF standard, so Frigate can pull its stream directly. Reolink and Amcrest are the usual picks. Frigate’s detection benefits from a small AI accelerator (a Google Coral) or a recent CPU, which is why camera-heavy setups often run on a Raspberry Pi 5 or a mini PC rather than the lightest hardware. We cover the full build in Frigate NVR + Home Assistant setup, the hardware in best IP cameras for Frigate, and why wired beats wireless here in PoE vs Wi-Fi cameras.
Voice: the hardest one to replace (but it’s possible)
An Alexa or Google Home is the device most people assume can’t be replaced locally. It can — this is just the most advanced project on the list. The local voice stack in Home Assistant uses the Wyoming protocol: Whisper for speech-to-text and Piper for text-to-speech, both running as add-ons on your own server. No request ever leaves your network.
For the microphone-and-speaker part, the simplest route is the official Home Assistant Voice Preview Edition (~$59), which is built for exactly this; the DIY route is an ESP32-S3 satellite. Be honest with yourself about expectations: local voice handles “turn off the kitchen lights” and “is the garage door open?” reliably, but it won’t tell you tomorrow’s weather in a natural conversation the way a cloud assistant does. For controlling your house — which is the point — it’s genuinely good. See the voice section of running Home Assistant fully offline.
Locks, sensors and alarms: dump the monitoring fee
A cloud lock ties your front door to a vendor account and app; a monitored alarm like Ring adds $10–20 every month forever. Both replace cleanly. Use a Z-Wave or Zigbee lock (Schlage BE469, Yale Assure, certain Kwikset models) that pairs directly to Home Assistant with no manufacturer cloud — details in best smart locks with no subscription.
For security, Home Assistant has a built-in alarm panel. Pair it with Zigbee motion sensors and door/window sensors, add a siren, and you have a self-monitored system that texts you instead of paying a company to watch a screen — the full build is in DIY home alarm with no monthly fees. The trade-off to name plainly: you lose professional monitoring dispatch. For many people, instant alerts to their own phone plus camera footage is the better deal; for others, that dispatch is worth paying for. Decide deliberately.
Climate and lighting: mostly easy
Thermostats and lighting are among the least painful to localize. A Zigbee, Z-Wave or Matter thermostat (Sinopé, Zooz, Heatit) gives you full local schedule and automation control with no Nest account that can be deprecated. Lighting is often the easiest win of all: most “smart bulbs” are Zigbee underneath, and they pair directly to a Home Assistant Zigbee coordinator — you can skip the Philips Hue bridge and its cloud entirely. If you’re choosing a protocol to standardize on, start with Zigbee vs Z-Wave and how Matter fits in.
Remote access: replace Nabu Casa for free
The one cloud dependency people worry about most — getting to their dashboard from outside the house — is also one of the easiest to solve for free. Instead of the Nabu Casa subscription, install Tailscale (or WireGuard). It builds an encrypted tunnel directly between your phone and your Home Assistant server, so from anywhere in the world your phone behaves as if it were on your home Wi-Fi. No ports exposed to the internet, no third party in the middle. Step by step in remote access with Tailscale. (Nabu Casa is still worth supporting if you can — it funds Home Assistant’s development — but it should be a choice, not a requirement.)
What’s genuinely hard to replace
Honesty is the whole point of this site, so here’s what doesn’t localize cleanly yet:
- Good robot vacuums. The best mapping vacuums lean heavily on the cloud. You can free some models with Valetudo (which requires rooting the robot) or buy a Matter-capable vacuum, but it’s an advanced project with compromises.
- Weather forecasts. Sun position (sunrise/sunset) is fully local via Home Assistant’s Sun integration, but an actual forecast has to come from somewhere online. A free source like Met.no is private and unmetered, but it isn’t “offline.”
- Anything that’s cloud to its core — most video doorbells’ two-way talk to a phone while you’re away, some wearables. Know these going in so you’re not surprised.
Where to start
Don’t rip everything out in a weekend. The path that works: pick the one cloud service that annoys you most — usually cameras (to kill the subscription) or remote access (to kill the fee) — and replace just that. Get comfortable, then work down the table. Our local smart home beginner roadmap lays out a sane order, and moving your smart home off the cloud in a weekend is a good first project once Home Assistant is running.
Every row you move from cloud to local is one less company that can raise a fee, close an API, or read your data. That’s the whole game.