Search for the right hardware to run Home Assistant and you land in a wall of forum threads: a Reddit argument here, a few community posts there, everyone with a different box and a different opinion. Once your smart home grows past a few bulbs and a thermostat, the machine you run it on stops being a hobby detail and starts deciding whether your automations feel instant or laggy, whether your history survives a power cut, and whether you can add camera detection or local voice later without starting over. A small mini PC answers most of those questions in your favor. The sections below cover why, how much machine you need, and whether to install Home Assistant OS on the bare metal or run Home Assistant in a container.
Why a Mini PC Beats a Raspberry Pi Here
The Raspberry Pi was the default Home Assistant box for years, and for a modest setup it still does the job. Home Assistant writes to its recorder database constantly, logging every state change from every device, and on a Pi that database usually lives on a microSD card. SD cards are not built for that kind of sustained write churn, and a card can quietly corrupt a year in and take the whole setup down with it. You can move the database to external storage to soften this, but at that point you are bolting workarounds onto a machine you have already outgrown.
The Pi is the right tool for a small, static setup, and a mini PC is the right tool for one you expect to grow. A mini PC boots and stores everything on an NVMe or SATA SSD, which handles years of constant writes, and it ships with far more RAM and CPU headroom than a Pi. Because it is x86, the hardware support in Linux is broad and mature, so the operating system underneath Home Assistant tends to behave predictably. None of this makes the Pi a bad choice; it is cheaper, sips a little less power at idle, has GPIO pins the mini PC lacks, and rides on an enormous community.
Add-ons Decide How Much Hardware You Need
Home Assistant’s core handles automations and the dashboard, but most of its power comes from the extras you bolt on: an MQTT broker like Mosquitto, Zigbee2MQTT for your Zigbee mesh, ESPHome for DIY sensors, Node-RED for visual automations, Frigate for camera object detection, and Whisper plus Piper for a voice assistant that runs entirely on your own hardware. Each of these runs as its own container alongside the core, and each one asks for a slice of CPU, memory, and disk.
Stack two or three of those on a Raspberry Pi and it copes. Add Frigate doing real-time object detection on a camera feed, or a local voice pipeline transcribing speech, and a Pi is suddenly working at the edge of what it can do. An N100-class mini PC has the headroom to run the core plus a healthy stack of add-ons and still leave room to spare, which is the situation you want to be in when you think of a new integration on a Saturday afternoon and want to try it.
An N100 Mini PC with 8GB to 16GB RAM Is Enough
An Intel N100-class chip, the kind found in inexpensive fanless mini PCs, comfortably runs the Home Assistant core and a stack of common add-ons while drawing very little power. For a machine that stays on around the clock, a low-wattage box is cheap to leave running and, when fanless, completely silent in a living room. If you want the yearly dollar math on that, our look at what a mini PC costs to run 24/7 puts numbers on it.
For memory, treat 8GB as a sensible floor and 16GB as the comfortable choice. The core itself is happy in a couple of gigabytes, but the moment you add a camera NVR, a database-heavy history, or a local voice assistant, you need that extra headroom. For storage, any modern NVMe or SATA SSD is fine; the point is to avoid running the whole system off a USB flash drive long term, because that reintroduces the exact wear problem you left the Pi to escape. Very new silicon occasionally wants a current kernel before every device on the board behaves. Also, a mini PC only handles the software side of the smart home. Zigbee, Z-Wave, and Thread devices still need a supported USB radio plugged in, whichever machine you choose. When you are ready to pick a specific model, the mini PC comparison chart tracks current specs and pricing.
The Install Choice: Home Assistant OS vs Container
Home Assistant now ships in two supported flavors: Home Assistant OS and Home Assistant Container. Two older methods, Supervised and Core, were deprecated at the end of 2025 and are no longer the path for a new build. Supervised ran the full managed stack on top of your own Debian install but held you to strict operating-system requirements, and Core was a bare Python install aimed at developers, with no containers and no add-ons. New installs should skip both.
Home Assistant OS on bare metal turns the whole mini PC into a Home Assistant appliance. HAOS is a minimal operating system built only to run Home Assistant. It includes the Supervisor, the piece that manages the core, the Add-on Store, and built-in backups, so you get one-click updates, the full add-on ecosystem, and a system that mostly maintains itself. HAOS wants the whole disk, and the box does exactly one job. For most people whose mini PC is dedicated to home automation, this is the right answer, and it is the least fiddly path from a blank machine to a working smart home.
Home Assistant Container takes the opposite approach. You install a general-purpose operating system like Debian or Ubuntu, then run Home Assistant as a single Docker container among however many others you like. The same box can then also host your network storage, a media server, or anything else you self-host. Home Assistant Container has no Supervisor, which means no Add-on Store. Everything an add-on would have given you (the MQTT broker, Zigbee2MQTT, and the rest) you now install and wire up as your own Docker containers, and you own their updates and configuration.
Home Assistant Container Has No Add-on Store; HAOS in a Proxmox VM Keeps It
Choosing Home Assistant Container means giving up the Add-on Store and the Supervisor conveniences that ride along with it: the guided backups, the one-click updates, and the reassurance that the pieces were tested together. You can rebuild all of that yourself with plain Docker, but you are signing up to be the person who keeps it running. If Home Assistant is the main thing the box does, that is effort spent for very little gain over just flashing HAOS.
If you want one mini PC to run Home Assistant and a pile of other services without the manual add-on juggling, run a hypervisor like Proxmox on the mini PC, then install Home Assistant OS inside a virtual machine on it. Home Assistant behaves exactly like the bare-metal appliance, add-ons and backups included, while the host underneath is free to run your other workloads in their own containers or VMs. That approach is a natural stepping stone toward turning the same mini PC into a broader home server, and it fits the wider self-hosting revival of moving off cloud subscriptions and onto small machines of your own. The cost is a bit more setup and a slightly steeper learning curve; in exchange, one box runs everything.
Schedule Backups and Keep a Copy Off the Box
Whichever route you take, spend five minutes on the parts that keep a smart home from becoming a weekend salvage operation. On Home Assistant OS, use the built-in backups, schedule them, and make sure a copy lands somewhere off the box, because a backup that only lives on the machine that failed is not really a backup. The SSD gives you the durability the SD card never had, but drives still die eventually, and a recent backup turns that from a catastrophe into an afternoon. If you go the container route, the same principle holds; you are just responsible for arranging the backups yourself. With a recent off-box backup, you can restore onto new hardware instead of rebuilding your automations from memory.
Buy an N100 Mini PC and Install Home Assistant OS
For most people, choose an N100-class mini PC with 16GB of RAM and an NVMe SSD, and install Home Assistant OS on the bare metal. That combination is quiet, cheap to run, and gives you the full add-on ecosystem with the least ongoing fuss. Reach for Home Assistant Container, or for Home Assistant OS inside a Proxmox VM, only when you want that one box to do more than home automation and you are ready to own a little more of the stack.
Frequently Asked Questions
Can Home Assistant run on a Raspberry Pi?
Yes. Home Assistant officially supports the Raspberry Pi and it runs well for smaller setups. The limits show up when you add heavy work like camera object detection or a local voice assistant, and over time an SD card can wear out under constant database writes.
Do add-ons work on every Home Assistant install?
No. The Add-on Store needs the Supervisor, which comes with Home Assistant OS. Home Assistant Container has no Add-on Store; you run the equivalent services yourself as your own containers.
How much RAM does Home Assistant need on a mini PC?
The core runs comfortably in a couple of gigabytes, but 8GB is a sensible floor and 16GB leaves headroom for heavier add-ons like a camera NVR or local voice and for future growth.
Should I install Home Assistant OS or use Docker?
If the mini PC is dedicated to Home Assistant, install Home Assistant OS on the bare metal for the simplest, fully supported experience with the full add-on ecosystem. Choose the container route only if the box also runs other services and you are comfortable managing your own stack.
Do I still need a Zigbee or Z-Wave stick with a mini PC?
Usually yes. A mini PC handles the software, but Zigbee, Z-Wave, and Thread devices talk over radios, so you add a supported USB radio for those protocols. Wi-Fi and network devices do not need one.
