Home Assistant OS vs Docker vs Proxmox

Quick Summary (TL;DR):
For most users, Home Assistant OS (HAOS) directly on the hardware is still the simplest and lowest-maintenance choice. It includes Home Assistant Core, Supervisor and Home Assistant Apps, and Home Assistant recommends HAOS for most installations. Home Assistant Container is the better fit if you already maintain Linux and Docker and want Home Assistant to behave like one service among many, but you manage the host, container updates and supporting services yourself, and Container does not include Home Assistant Apps. Proxmox is not a separate Home Assistant installation type: the normal approach is to run the official HAOS KVM/Proxmox image inside a virtual machine. That preserves Supervisor and Apps while adding VM isolation and the ability to run other workloads, but it also adds another operating layer to maintain and makes USB Zigbee/Thread/Z-Wave hardware more complicated. For a dedicated Home Assistant mini PC, use direct HAOS. For an existing Docker server, Container can be very clean. For a multi-service home server, HAOS on Proxmox is usually the most flexible architecture.

Home Assistant OS vs Docker vs Proxmox at a Glance

Feature	Direct HAOS	Home Assistant Container	HAOS VM on Proxmox
Installation type	Home Assistant OS	Home Assistant Container	Home Assistant OS inside VM
Supervisor	Yes	No	Yes
Home Assistant Apps	Yes	No	Yes
HA updates	Managed in HA	Pull/recreate container	Managed in HA inside VM
Host maintenance	Minimal	You manage Linux + Docker	You manage Proxmox
Built-in HA backups	Yes	Yes	Yes
Other server workloads	Mostly through Apps	Excellent	Excellent
USB radios	Direct access	Docker device mapping	USB passthrough to VM
Best use	Dedicated Home Assistant box	Existing Docker host	Multi-service home server

Home Assistant Officially Has Two Main Installation Types

Home Assistant’s current installation documentation describes two supported installation types: Home Assistant Operating System and Home Assistant Container.

Proxmox sits underneath Home Assistant. You install Proxmox VE on the physical server, create a virtual machine, and run Home Assistant OS inside that VM using the official KVM/Proxmox .qcow2 image.

This distinction matters because HAOS on Proxmox still includes Supervisor, Apps, Home Assistant OS updates and the normal HAOS backup experience. You have not switched to Container just because you are virtualising the operating system.

What Is Home Assistant OS?

Home Assistant Operating System is a minimal operating system designed specifically for the Home Assistant ecosystem. It includes Home Assistant Core, Home Assistant Supervisor and support for Home Assistant Apps.

Supervisor handles several jobs that otherwise become your responsibility:

Updating Home Assistant Core.
Updating Home Assistant OS.
Installing and managing Home Assistant Apps.
Creating and restoring Supervisor-managed backups.
Managing parts of the network and host system.
Providing the integrated HAOS management experience.

Home Assistant explicitly recommends HAOS for most users because it removes most of the operating-system administration.

What Is Home Assistant Container?

Home Assistant Container runs Home Assistant Core in an OCI container, with the official documentation focusing on Docker.

You provide the operating system and container runtime. You also manage:

Linux updates.
Docker updates.
Persistent volumes.
Container networking.
USB/device mappings.
Supporting services such as MQTT.
Backups for any external containers.

Container still gives you the normal Home Assistant interface, integrations, automations, dashboards and blueprints. What it does not include is Supervisor or the Home Assistant Apps system.

What Does Proxmox Change?

Proxmox turns the mini PC into a virtualisation host. Home Assistant becomes one virtual machine rather than the owner of the physical server.

Mini PC hardware
    ↓
Proxmox VE
    ├── Home Assistant OS VM
    ├── Linux VM
    ├── LXC container
    └── Other services

The main advantage is isolation. Home Assistant can use HAOS while other workloads run separately. The main disadvantage is that you now have two systems to maintain: the Proxmox host and the HAOS guest.

Apps Are the Biggest HAOS vs Container Difference

Home Assistant renamed what used to be called add-ons to Apps in 2026. Older guides will still use the old term.

Apps are additional software packages managed directly from Home Assistant, including software such as MQTT brokers, ESPHome Device Builder, Node-RED, editors, VPN tools and voice-related services.

Apps are only available with Home Assistant OS. On Home Assistant Container, you can often run the same underlying software, but you deploy it separately in Docker and maintain it yourself.

Thread and Z-Wave Are More Integrated on HAOS

Home Assistant’s current installation documentation notes that some integrations, including Thread and Z-Wave, rely on Apps for their out-of-the-box HAOS experience.

That does not mean these technologies are impossible with Container. It means you may need to deploy and connect the supporting services manually rather than installing them through Home Assistant.

Updates: HAOS Is the Simplest

With HAOS, Home Assistant Core and HAOS updates are managed from Home Assistant.

With Container, the official update process requires pulling a newer container image and recreating the service. With Docker Compose that normally looks like:

docker compose pull homeassistant
docker compose up -d

This is easy if you already operate Docker. It is still an extra responsibility compared with direct HAOS.

With Proxmox, HAOS still updates itself inside the VM, but the Proxmox host also needs package and security updates. Virtualisation adds flexibility, not zero maintenance.

Backups Now Work Across Installation Types

Older comparisons often claim that proper backups are an HAOS-only feature. That is no longer accurate. Home Assistant’s current Backup integration creates and restores backups across all installation types.

The difference is the scope around Home Assistant:

HAOS: Home Assistant plus Supervisor-managed Apps and App data can be part of the integrated backup workflow.
Container: Home Assistant can create backups, but separately deployed Docker services remain separate systems with their own data and backup requirements.
Proxmox + HAOS: you can use Home Assistant backups inside the VM and also use Proxmox-level VM backups or snapshots.

Proxmox snapshots are useful for short-term rollback, but they are not a replacement for an independent Home Assistant backup stored away from the same SSD.

Supervisor Restore Remains a HAOS Advantage

The Supervisor-specific full and partial restore actions are available on HAOS. They can restore Home Assistant settings plus selected Apps and App data.

Container does not have Supervisor, so external services such as a separately deployed Mosquitto or Node-RED container need their own recovery plan even if Home Assistant itself is backed up.

Direct HAOS Has the Fewest Layers

Mini PC
    ↓
Home Assistant OS
    ↓
Supervisor
    ↓
Home Assistant Core + Apps

For a dedicated smart-home controller, this is attractive. There is no general-purpose Linux host, Docker Compose stack or hypervisor to troubleshoot.

If the machine exists only for Home Assistant, additional layers need to justify themselves.

Docker Is Best When You Already Run Docker

Home Assistant Container makes sense when the server already runs Docker services such as:

Mosquitto.
InfluxDB.
Grafana.
Immich.
AdGuard Home.
VPN services.
Media services.

In that environment, Home Assistant can fit cleanly into the same Compose-based management model.

If you are buying a mini PC purely for Home Assistant, installing Linux and Docker only to run one Home Assistant container usually creates work rather than saving it.

Proxmox Is Best When the Machine Is a Server First

Proxmox makes the most sense when you want one physical mini PC to run several isolated workloads.

Home Assistant in its own HAOS VM.
Linux servers in other VMs.
LXC containers.
DNS or VPN services.
Monitoring.
Development or test machines.

Home Assistant retains the complete HAOS experience, while other services can be restarted, upgraded or rebuilt independently.

Proxmox Resource Requirements

Home Assistant’s current virtual-machine documentation lists minimum resources of 2GB RAM and 2 vCPUs. Those resources can be increased later.

For a normal Home Assistant VM, 4GB RAM is a comfortable practical starting allocation on a modern mini PC. The physical Proxmox host may need 8GB, 16GB or considerably more depending on the other guests.

Do not confuse Home Assistant memory requirements with whole-server memory requirements.

Storage Architecture

With direct HAOS, Home Assistant owns the physical boot drive. With Container, Linux owns the drive and Home Assistant normally uses a persistent mapped configuration directory. With Proxmox, the HAOS VM sees a virtual disk stored on the Proxmox host.

Proxmox gives you more flexible storage management, but you must understand where VM disks, snapshots and backups live. A snapshot stored on the same physical SSD does not protect you from SSD failure.

USB Zigbee, Thread and Z-Wave

Direct HAOS has the simplest hardware path: plug the USB radio into the Home Assistant machine and let HAOS use it.

With Docker, the host device must be mapped into the Home Assistant container.

With Proxmox, the USB device must be passed through from the host into the HAOS VM. Proxmox supports USB passthrough by vendor/product ID or by host bus/port.

That works well, but it ties the VM to physical hardware on that Proxmox node. Our next article covers the implementation details: Home Assistant on Proxmox: Zigbee and Thread USB Passthrough.

Bluetooth and Virtualisation

Bluetooth is another area where direct hardware is simpler. A Proxmox VM does not automatically inherit the host’s integrated Bluetooth controller.

You may need a passed-through USB Bluetooth adapter or, often more usefully, ESPHome Bluetooth proxies around the house. Bluetooth coverage is a radio-placement problem as much as a server feature.

Security and Maintenance

Direct HAOS is purpose-built and keeps the host narrow in scope. Container gives you full control over Linux, but you are responsible for Linux, Docker, firewalling and every other service. Proxmox provides strong VM isolation, but the hypervisor becomes critical infrastructure that also needs updates.

No option eliminates security maintenance. It changes how much infrastructure you own.

Failure Domains

With direct HAOS, a mini-PC or SSD failure stops Home Assistant. With Docker, a host failure can stop Home Assistant and every other container. With Proxmox, a host failure can stop every VM on that node.

Virtualisation isolates software workloads from each other, but it does not remove the physical host as a single point of failure. Off-host backups remain essential.

Can You Run Home Assistant Container Inside Proxmox?

Yes. You can create a Linux VM, install Docker and run Home Assistant Container there.

Proxmox
    ↓
Linux VM
    ↓
Docker
    ↓
Home Assistant Container

This makes sense if that Linux VM already hosts a larger Docker stack. If your only goal is to run Home Assistant on Proxmox, using the official HAOS virtual-machine image is usually simpler and retains Supervisor and Apps.

What About LXC?

Community guides and scripts exist for running Home Assistant-related software in LXC. However, Home Assistant’s official production installation choices remain HAOS and Container, and its Proxmox image is a KVM/QEMU VM image.

For a predictable long-term installation, HAOS in a VM is the cleaner Proxmox route.

Direct HAOS Is Best for a Dedicated Mini PC

Fewest layers.
Direct USB access.
Supervisor and Apps.
Simple updates.
Integrated host management.
Easy recovery with Home Assistant backups.

If your N100/N150 mini PC exists only for Home Assistant, direct HAOS is the logical default. See How to Install Home Assistant OS on an N100 or N150 Mini PC.

Container Is Best for an Existing Docker Host

You already manage Linux and Docker Compose.
You prefer separate containers for MQTT and related services.
You do not need the Apps store.
You are comfortable managing updates manually.
You understand device mapping and host networking.

Container is powerful precisely because it gives you control. That control is also the maintenance cost.

Proxmox Is Best for a Multi-Service Home Server

Home Assistant gets a dedicated HAOS VM.
Other workloads remain separate.
Resources can be allocated per guest.
VM backups and snapshots are available.
You retain Supervisor and Apps.
The server can grow beyond Home Assistant.

The cost is operational complexity: Proxmox networking, storage, host updates and passthrough become part of your skill set.