SHSelfHostIndex

Home Automation

Control smart devices locally and privately with self-hosted home automation platforms.

85 self-hosted apps · 216 comparisons

All home automation apps

Last reviewed Aug 26, 2026 · 442 words

Pick Home Assistant and move on. At 90,111 GitHub stars, with integrations for thousands of devices and automations that run entirely on your own hardware, it has been the centre of this category since 2013 and nothing else here is really competing for the same job. The decisions worth your attention are the layers around the hub: which radio bridges your devices, whether Apple Home is in the picture, and a couple of deployment traps that reliably eat a first evening.

How to choose the stack around the hub

Start with radios. Wi-Fi devices talk to Home Assistant directly, but most good sensors and bulbs are Zigbee, and the vendor-neutral way in is Zigbee2MQTT: a USB coordinator stick, an MQTT broker, and support for thousands of devices with no proprietary hub. It runs in 256 MB; the honest cons are that you must buy the coordinator and that pairing stubborn devices can be finicky. Next, decide how deep your tinkering goes. Tasmota and WLED are replacement firmware for ESP8266/ESP32 hardware — total local control of plugs and LED strips, at the price of flashing devices yourself, which is not a beginner's first weekend. Finally, count the iPhones in the house. If the family lives in Apple Home, Homebridge (25,467 stars, 256 MB, Easy) bridges unsupported devices into HomeKit through its plugin ecosystem, and it happily coexists with Home Assistant.

The two gotchas that break a first install

Both come straight from the deployment notes. One: Home Assistant in Docker needs host networking, because device discovery over mDNS and SSDP does not cross Docker's default network — a bridged container looks fine and silently finds nothing. Zigbee and Z-Wave USB sticks likewise need an explicit device passthrough. Two: if you put it behind a reverse proxy, add the proxy's IP to trusted_proxies in configuration.yaml, or logins fail with no obvious explanation.

Where to start

A dedicated small box running the Home Assistant OS image is the least-friction path; Docker on an existing server is the flexible one, with the caveats above. Add Zigbee2MQTT once you own Zigbee hardware, and Homebridge only if Apple Home matters. For alerts from all of it, ntfy pushes notifications to your phone over plain HTTP in a 64 MB container.

The default for a first-timer: Home Assistant OS on its own hardware, one Zigbee coordinator stick, Zigbee2MQTT, and no firmware flashing until the basics have run quietly for a month. Expect a learning curve on automations — the catalogue lists it honestly — and expect it to be worth the climb.

Curated picks

Easiest Home Automation to self-hostBest API Home AutomationBest Cross-Platform Home AutomationBest Docker Home AutomationBest Free Home AutomationBest Lightweight Home AutomationBest Mobile App Home AutomationBest Multi-User Home AutomationBest Offline-First Home AutomationBest Plugins Home AutomationBest Real-Time Home Automation

Home Automation comparisons

216 head-to-head comparisons in this category.

See all comparisons →