Home Assistant VPS Docker Hosting

Home Assistant is free, open-source smart home software that unifies lights, thermostats, cameras, locks, sensors, and switches into a single local hub with an automation engine. It is governed by the Open Home Foundation, a non-profit announced in April 2024 that also stewards ESPHome, Music Assistant, HACS, and more than 250 related open-source projects. The platform supports thousands of integrations and runs entirely on hardware you control, with the option of paid cloud access for remote use across the wider internet.

Home Assistant controls thousands of smart devices from one dashboard. You can build automations around sunset lighting, presence-based heating, leak alerts, garage door reminders, and notification routines triggered by sensors or by external events. The Energy dashboard tracks solar generation, grid use, and per-device consumption. Voice control runs through the built-in Assist feature on supported hardware. The Logbook records every event, and history graphs show state changes for every entity, which makes diagnosing a misbehaving automation easier on a busy hub.

Home Assistant ships more than 1,000 official integrations, covering more than 3,000 named devices across major smart-home brands and open protocols. Categories range from lighting and climate to cameras, locks, energy monitors, presence sensors, weather services, voice assistants, and home appliances. The community add-on store, HACS, layers many more community integrations on top of the official catalog. The breadth is one of the main reasons people pick Home Assistant over vendor-specific hubs that only talk to one ecosystem of devices on the market.

Home Assistant OS is the turnkey image that includes the Supervisor, the official Add-on Store, and one-click upgrades. Home Assistant Container is the Docker image that omits the Supervisor and the Add-on Store, so services like MQTT brokers, Node-RED, AdGuard, and Zigbee2MQTT must be deployed as separate containers that the operator manages. Container fits servers that already run Docker. OS fits dedicated hardware. The Supervised path has been deprecated for new installs since May 2025 by the project maintainers in the docs.

Yes, technically, though it is an advanced configuration. A VPS fits cloud-API and Wi-Fi devices because those talk over HTTPS rather than over local radios. Local radio devices over Zigbee or Z-Wave need a coordinator on the same LAN as the devices, so the practical pattern is to keep a small local box at home running Zigbee2MQTT and bridge it to the remote Home Assistant over MQTT. Most homes stay on local hardware specifically to avoid this hybrid setup workflow.

Yes, the core platform is free and open source with no paywalled features. There is no per-device fee, no per-user fee, and no time limit on use. The optional Nabu Casa Cloud subscription, priced at roughly $6.50 to $8 per month, funds the project and adds simple encrypted remote access along with turn-key Alexa and Google Assistant integration. A 30-day trial is offered to new users. Self-hosting remote access through a reverse proxy or VPN remains fully supported for users who prefer not to subscribe.

A Python application runs on local hardware or on a server, talks to devices through more than 1,000 integrations over Wi-Fi, Zigbee, Z-Wave, Bluetooth, Thread, and Matter, and stores state in a recorder database. A rule engine executes user-defined automations on triggers, conditions, and actions. Local-protocol radios need a coordinator on the same LAN as the devices. Cloud-API integrations talk to vendor endpoints over HTTPS. The Companion mobile apps expose phone sensors back to the hub for location-aware routines on the go.

Yes. Local-protocol devices over Zigbee, Z-Wave, Matter, Thread, and ESPHome continue to work during an internet outage, since they talk directly to a coordinator on the local network rather than to a vendor cloud. Only integrations that depend on a vendor cloud endpoint, such as a cloud-based thermostat with no local API, break during an outage. This local-first design is one of the main reasons people pick the platform, since smart-home rules keep firing even when the outside link is down.

The minimum target is two CPU cores, two gigabytes of RAM, and persistent storage on the host. The community recommends a modern CPU with four to eight gigabytes of RAM and at least 32 gigabytes of fast storage for an installation that scales as you add integrations and history. Idle RAM use sits around 300 to 500 megabytes. Larger installs that record many sensors at high frequency benefit from migrating the Recorder database from SQLite to MariaDB or PostgreSQL for better concurrent throughput.

No. A Raspberry Pi is one common entry path, but Home Assistant runs on Home Assistant Green and Yellow appliances, mini-PCs, NAS units, virtual machines, and any Docker host that meets the resource targets. Larger installs typically move off the Pi to a mini-PC or VM for more headroom, faster storage, and better concurrent performance under the Recorder workload. Pi-class hardware on an SD card is also where the long-running SD-card wear problem shows up, which an external SSD generally solves.