Home Assistant
Local-first, open-source home automation hub with thousands of device integrations and no mandatory cloud.
5 private alternatives, vetted against our public criteria.
Google Home runs your automations and voice requests through Google’s cloud, which means an always-listening device wired to the account that already tracks you. Muting the microphone or deleting recordings helps after the fact, but it does not change where your home is actually controlled from. The hubs below keep the automation on hardware inside your own house, so your lights and sensors answer to you instead of an advertising company, and they keep working when the connection drops.
Local-first, open-source home automation hub with thousands of device integrations and no mandatory cloud.
Vendor-neutral, Java-based home automation platform with local control and a large binding ecosystem.
Lightweight open-source home automation system that runs well on low-power hardware like a Raspberry Pi.
Open-source IoT and home automation platform built on Node.js with a large adapter ecosystem.
Apple's smart home framework. End-to-end encrypted home data, on-device camera processing.
Why settings won’t fix Google Home. The speaker is a front end for a cloud service, and that is the architecture rather than a preference you can adjust. The voice processing and the automation logic live on Google’s servers because that is the product being sold, so your home has to report there for the device to do its job. Deleting a recording after the fact does not alter the design; it still routes everything that happens inside your house through a company whose business is knowing it. No settings screen turns a cloud product into a local one. A hub that runs the logic in your own home takes that server out of the loop entirely, which is the only change that genuinely brings the control back to you.
What actually matters in a smart home platform. Local control is the whole point, so begin there: the hub should keep firing routines when the connection drops, and your device states should never need to leave the house to trigger an action. Broad device support comes next, because a hub that speaks Zigbee and Z-Wave alongside Matter and Wi-Fi frees you from buying into a single vendor’s catalogue. An open-source core matters too, since it lets the community verify what the hub really does rather than take it on faith. Home Assistant leads on both breadth and a large community, while openHAB suits people who want a rules engine they can shape in detail. Remote access should be a choice you make rather than the default, reached through an encrypted tunnel or a VPN back to your own network instead of a control surface exposed on the public internet. Treat a mandatory cloud account as a warning sign, because it quietly puts a company back in the middle of your home.
How to switch. Put one hub on a small computer or a Raspberry Pi, then add your existing devices through their local integrations one at a time. Rebuild your handful of routines there and keep the Google speakers running in parallel until the new setup is stable, so nothing in your daily routine breaks during the changeover. When the local hub is reliable, unplug the cloud speakers for good. The trade is a weekend of setup for a home that stays quiet and keeps working on its own. If Google Home is one piece of a larger move, the de-Google playbook covers the rest of the ecosystem the same way.