Home Assistant Operating System

Last reviewed Sep 13, 2026 · 906 words

Home Assistant offers four ways to install, and only one of them, Home Assistant Operating System, gets you the add-on store, the built-in backup system, and updates that apply from a button in the UI. The other three (Container, Core, and the deprecated-in-spirit Supervised) trade some or all of that for the freedom to run Home Assistant beside other things on the same box. So the decision is not "which is more powerful", they run the same Home Assistant. It is whether the device will do anything else. If no, HAOS. If yes, a VM running HAOS, which gets you both, and I will get to why that is the right answer for most people with a server already.

What the Supervisor gives you and Container does not

HAOS is a minimal Linux built to run Docker and one privileged container called the Supervisor. The Supervisor manages the Home Assistant Core container and every add-on as further containers, exposes them in the UI, handles their updates, and takes snapshots of the whole lot. The practical wins are these. Add-ons like Zigbee2MQTT, Mosquitto, ESPHome, Node-RED, and a Samba share install with one click and are wired into Home Assistant's ingress, so they appear in the sidebar with no ports to remember. Backups cover Core, its configuration, and every add-on's data in one archive, which you can schedule and push to a network share or Home Assistant's cloud. Core updates, OS updates, and add-on updates each have a button and a rollback. On the Container install, every one of those is a compose file you write, a port you manage, and a backup script you maintain. It is a fine way to run it if you already do that for 20 other services; it is a poor first experience.

The hardware question has a boring answer

HAOS runs on a Raspberry Pi 4 or 5, on x86 mini PCs, on the official Home Assistant Green (about $99 at last check) and Yellow boards, and as a VM image for Proxmox, VirtualBox, and a few hypervisors. The 1 GB minimum is honest for Core alone; the moment you add Zigbee2MQTT, an MQTT broker, and a database add-on, 2 GB is the realistic floor and 4 GB stops you thinking about it. The Green is the answer for someone who wants an appliance. A used x86 thin client for the same money is faster and lets you add a Coral or a second radio later. On a Pi, boot from a USB SSD rather than a microSD card; the recorder database writes constantly and cards die in a year or two.

It takes over the whole device, and that is the trade

HAOS is not a general-purpose Linux. There is no package manager, the root shell is meant for debugging rather than living in, and anything not packaged as an add-on has no supported way to run. People who try to install Pi-hole or a media server on the HAOS box are fighting the design. The add-on catalogue is large enough that most home-automation adjacent needs are covered, and the community add-on repository fills more. For anything beyond that, the device is spoken for.

The Proxmox VM is how you keep the freedom

If you already have a server, run HAOS as a VM on it. The community-maintained Proxmox helper scripts create the VM from the official image in a minute or two, USB passthrough hands the Zigbee or Z-Wave stick to the VM, and you get the Supervisor experience while the host keeps running everything else. Give the VM 2 vCPUs and 4 GB, take Proxmox-level snapshots before big updates, and use Home Assistant's own backups for the day-to-day. The Proxmox, Docker, or both piece covers why this layering works. The one thing to know: USB passthrough of a radio is reliable, but a radio on a USB 3 port next to an SSD can suffer interference; use a short extension cable.

What the first month looks like

Onboarding takes 10 minutes. Devices on the network are discovered automatically, integrations are added from the UI, and the first month with Home Assistant guide lays out the order to do things in. HAOS itself, at 7,458 stars and Apache-2.0, releases monthly alongside Core; update Core monthly and the OS whenever it asks, with a backup taken first, which the UI offers to do for you. If you are weighing it against the other open platform, the Home Assistant vs openHAB comparison covers that; for the wider home automation category, Home Assistant is the default and HAOS is the default way to run it.

What I'd do

No existing server: buy a Home Assistant Green or a used x86 thin client, flash HAOS, and never think about the install again. Existing Proxmox host: HAOS in a VM with 4 GB and the radio passed through. Existing Docker host with no hypervisor: the Container install, with your eyes open about writing your own compose for every add-on you would otherwise have clicked. Avoid Supervised on a general Linux install unless you enjoy reading breaking-change notices; it works but the project has narrowed what it supports.