What self-hosting Home Assistant means
Home Assistant is an open-source smart home platform. When you self-host it, the software runs on hardware you own, in your home. Device control and automations run locally, so they keep working when your internet connection is down. Cloud access is optional, and you can add it later for remote access.
Self-hosting also means you own the upkeep. You install updates, keep backups and keep the hardware running.
Supported installation methods
| Method | Add-ons | Best for |
|---|---|---|
| Home Assistant OS on a Raspberry Pi, mini PC or old laptop | Yes | Most people; the recommended route |
| Home Assistant Green | Yes | Buyers who want plug-and-play |
| Home Assistant OS in a virtual machine | Yes | People who already run a hypervisor |
| Home Assistant Container (Docker) | No | People who already run Docker and don’t need add-ons |
| Home Assistant on a NAS | Yes in a VM, no in a container | People who already own a NAS |
Home Assistant OS (HAOS) is the officially recommended method. It includes the Supervisor, the add-on store, one-click updates and built-in backups. Container installs have none of the add-on features.
Home Assistant OS on dedicated hardware
HAOS can run on a Raspberry Pi, a mini PC or an old laptop. The image is written to the device’s storage, and the device boots straight into Home Assistant. You don’t install Linux first.
- For a Pi, follow how to set up Home Assistant on a Raspberry Pi.
- For an old PC or laptop, follow how to install Home Assistant on an old laptop or mini PC.
Virtual machines
A virtual machine is a good option if you already run a hypervisor such as Proxmox, Hyper-V or VirtualBox. Home Assistant’s own guidance is that if you aren’t familiar with virtual machines, you should install HAOS directly on supported hardware instead. A VM needs the matching HAOS disk image, UEFI firmware and bridged networking. See running Home Assistant in a VM.
Docker containers and NAS
Home Assistant Container runs in Docker. It doesn’t include the Supervisor or the add-on store, so services such as an MQTT broker or Zigbee2MQTT run as separate containers.
A NAS can run either option. A VM with HAOS keeps add-ons, while a container does not. See running Home Assistant on a NAS or Docker and which NAS is best for running Home Assistant.
Official hardware: Green and Yellow
Home Assistant Green is a small, fanless box that comes with HAOS installed. You plug in power and Ethernet and finish setup in your browser.
Home Assistant Yellow is a modular board built around a Raspberry Pi Compute Module. It has a built-in Zigbee and Thread radio and an NVMe slot. Yellow availability has been limited, so check the official Home Assistant site before you buy. See Home Assistant Green vs Yellow for a side-by-side comparison.
Methods that are no longer supported
Supervised and Core (Python virtual environment) installs were deprecated in 2025.6 and became unsupported in 2025.12. If you run either today, take a full backup and plan a move to a supported method. 32-bit hardware is also no longer supported, so you need a 64-bit system, either x86-64 or aarch64 (64-bit ARM).
Hardware requirements for every method
- 64-bit processor. x86-64 for PCs and NAS boxes, or aarch64 for 64-bit ARM boards such as the Raspberry Pi 4 and 5.
- Memory and storage. At least 2 GB of RAM and 32 GB of storage. Use 4 GB of RAM or more if you run several add-ons.
- Flash storage. An SSD or eMMC is preferred over a microSD card, because Home Assistant’s database writes can wear out a card. If you start on a card, move Home Assistant to an SSD when you can.
- Wired network. Use Ethernet for the Home Assistant host. Wi-Fi works, but wired is more reliable for device discovery.
- UEFI boot on x86 PCs. The generic x86-64 image needs UEFI, with Secure Boot turned off.
Which method should you choose?
- You want the least fuss: Home Assistant Green, or HAOS on a Raspberry Pi 5 or a used mini PC.
- You already run Proxmox or another hypervisor: HAOS in a VM.
- You already own a NAS with VM support: HAOS in a VM on the NAS.
- You already use Docker and don’t need add-ons: Home Assistant Container.
Many experienced users prefer a used mini PC over a Pi once you add a power supply, a case and an SSD, because a mini PC often gives more performance for the money. A Pi is still a good choice for low cost, low power and a small footprint.
Remote access and backups
Set up backups before you change anything, and keep a copy off the device. Recent versions encrypt backups, so store the encryption key somewhere safe. Without it, an encrypted backup can’t be restored.
For remote access, you have three common options: Home Assistant Cloud, a paid subscription with pricing that varies by region; a VPN such as Tailscale; or a Cloudflare Tunnel. Don’t expose port 8123 directly to the internet without TLS and strong authentication with two-factor authentication.
Once Home Assistant is running, is Home Assistant beginner friendly? explains what to expect in the first few weeks.