Smart home hubs that work without the cloud (and the ones that don’t)
Updated · Reviewed against the current HomeHubAtlas dataset
Short answer: Home Assistant, Hubitat, and Homey Pro run automations fully locally; Apple Home is local for control and automations once set up; Alexa, Google Home, SmartThings, and Tuya execute in the cloud — when your internet drops, so do most of their routines. Local control also decides latency and what happens when a vendor discontinues a product.
What "local" actually means
Three things can be local or cloud: control (does tapping a button in the app cross the internet?), automations (does "motion → light" run on the hub or on a server?), and setup/administration (can you add devices offline?). A hub can be local for one and cloud for another — most marketing blurs the three. The verdicts below are about the first two, which are what you notice in an outage.
The 32 hubs we track, sorted
| Verdict | Hubs |
|---|---|
| Fully local — control and automations survive an outage | Home Assistant Green / Yellow, Hubitat C-8 / C-8 Pro, Homey Pro, SONOFF iHost, and every Zigbee2MQTT/ZHA coordinator setup |
| Local in practice — local execution inside the home network | Apple Home via Apple TV 4K, HomePod, or HomePod mini (Siri voice still needs the cloud); Philips Hue Bridge, Aqara Hub M3, and Bosch Controller II within their own ecosystems |
| Cloud-dependent — most routines execute on vendor servers | Amazon Echo hubs, Google Nest hubs, SmartThings hubs (a subset of routines can run locally), Tuya gateway, Homey Bridge, and Ring Alarm Pro (security functions excepted) |
Each hub page states its local-control verdict individually, sourced from the manufacturer's own documentation.
Why Matter helps but doesn't settle it
Matter is local by design — commands travel over your LAN or Thread mesh, not through a vendor server. But the controller still decides where automations run: a Matter plug in Alexa still waits for Amazon's cloud to fire a routine, while the same plug in Apple Home or Home Assistant runs it locally. Same device, different outage behavior — which is why our hub comparisons list local control next to the radio table.
What cloud dependence costs you
- Outage behavior. Internet down usually means voice control, app control, and cloud routines all stop; locally-executing hubs keep motion lights and schedules running.
- Latency. A local motion-to-light trip is tens of milliseconds; a cloud round trip is hundreds. You can see the difference in a dark hallway.
- Longevity. Cloud hubs live as long as the vendor's servers. A local hub keeps working after end-of-support — an underrated argument for Zigbee/Z-Wave gear on an open coordinator.
- Privacy. Local execution keeps occupancy patterns — when you wake, leave, return — inside the house.
Picking a lane
If outage resilience matters, start from the fully-local row and check our works-with pages for device coverage. If you are already deep in Alexa or Google Home, the pragmatic move is keeping time-critical automations (lights, locks) on a local layer — a Hue Bridge or a Zigbee coordinator — and letting the cloud handle voice and the nice-to-haves. The hub-choice guide walks the full decision.