Recommended Free Tools
For most cloud VPSs, the practical way to host Home Assistant is Home Assistant Container on a 64-bit Linux server, managed with Docker Engine and Docker Compose. You provide and maintain the operating system, Docker, storage, updates, backups and remote-access security. Home Assistant OS is a better appliance-style choice only when your VPS provider exposes a compatible virtual machine in which the OS image can run properly.
Need a server to try this on? Antihost offers Linux VPS plans with NVMe storage, full root access and a 14-day free trial.
This guide shows how to size the server, deploy a persistent Container installation, secure access from outside your home, plan for missing USB radios, and operate the system safely over time.
As an Amazon Associate I earn from qualifying purchases.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWhat a Home Assistant VPS actually runs
A VPS is a virtual server in a provider’s data center. It gives Home Assistant a public network location and continuously running compute, but it does not reproduce the hardware attached to your house. A normal VPS deployment therefore consists of a Linux virtual machine, Docker Engine, a Home Assistant Container, persistent storage for /config, and a deliberate remote-access design.
Home Assistant Container is a standalone container installation. You supply the Linux system and container runtime, and you manually handle host maintenance and Home Assistant updates. Container installations do not include Home Assistant apps (the add-on system available with Home Assistant OS). Services such as an MQTT broker, database, automation helper or voice-processing component must be run separately, usually as additional containers, or supplied by another machine.
#1 Best Overall
- 12th Intel Alder Lake N95 Processor – The GMKtec G3 S Mini PC is powered by the 12th Gen Intel N95 processor with 4 cores, 4 threads, 6MB cache and a burst frequency up to 3.4GHz. Compared with N100/N5105/N5100/N5095, the N95 delivers up to 36% overall performance improvement. Perfect for routine tasks, office work, and home entertainment, this compact mini desktop is more convenient than traditional bulky PCs.
- 8GB RAM & 256GB SSD Storage – Pre-installed with 8GB DDR4 memory and a fast 256GB M.2 2242 SSD, the G3 S mini desktop offers quicker startup, smoother multitasking, and faster file transfers. Enjoy seamless performance whether you’re working on multiple applications, browsing, or streaming content.
- Rich Interfaces & Connectivity – The G3 S mini computer comes equipped with USB 3.2 (up to 10Gbps), dual HDMI 2.0 (4K@60Hz), and a 3.5mm audio jack. With support for WiFi 5, Bluetooth 5.0, and Gigabit Ethernet (RJ45 1000MbE), it connects easily with monitors, projectors, printers, office equipment, and other peripherals, making it versatile for both home and business use.
- Dual 4K Display Support – Featuring upgraded Intel UHD Graphics (up to 1000MHz), the G3 S supports 4K video playback and AV1 decoding for a smooth viewing experience. With dual HDMI outputs, you can connect two 4K@60Hz displays simultaneously, enabling efficient multitasking for work and entertainment.
- GMKTEC WARRANTY - GMKtec offers a 3-year limited warranty (1 year replacement + 2 years parts replacement) for each mini PC, starting from the date of the purchase effective on all sales starting Oct. 2026. All defects due to design and workmanship are covered. With a professional after sales team always ready to attend to your needs, you can simply relax and enjoy your mini PC
Home Assistant’s 2025 installation guidance no longer treats Core and Supervised as forward-looking methods. For a new VPS, choose Home Assistant OS when the provider offers a suitable VM environment, or choose Home Assistant Container when you want ordinary Linux and Docker control.
Home Assistant OS or Container: which fits a VPS?
| Choice | Best fit | Apps | Who maintains the stack? | VPS suitability |
|---|---|---|---|---|
| Home Assistant OS | Appliance-style deployment with the Supervisor and integrated management | Yes | Home Assistant manages most of the operating stack; you still manage the VPS account and provider | Use only where the VPS exposes a supported virtual-machine environment and allows the OS image to operate as intended |
| Home Assistant Container | Linux users who want host and Docker control | No | You maintain Linux, Docker, the Home Assistant image and any companion services | Direct fit for most conventional 64-bit VPS instances |
Container is usually the least surprising choice on a rented Linux server. It is portable, easy to recreate and compatible with standard firewall and reverse-proxy tools. The trade-off is operational responsibility: there is no Supervisor to install apps for you, and an unattended host update or an untested image upgrade can interrupt service.
Free tools Windows power users keep installed
One-click scans. No signup required.
VPS requirements and sensible sizing
Home Assistant publishes 2 GB RAM and 2 vCPUs as minimums for its virtual-machine installation. Container usage varies, so those figures are a starting point rather than a guarantee. Recorder retention, database size, history-heavy dashboards, camera processing, voice assistants and other containers can all increase demand.
| Requirement | What to choose | Why it matters |
|---|---|---|
| CPU architecture | 64-bit amd64 or aarch64 |
Home Assistant marks i386, armhf and armv7 unsupported; those 32-bit architectures stop receiving updates. |
| Starting compute | At least 2 vCPUs and 2 GB RAM | Matches the published VM minimum; add headroom for databases, history, cameras and companion containers. |
| Disk | Persistent SSD-backed storage with snapshots or backups | The configuration, database, recordings and backups must survive container recreation and host reboots. |
| Operating system | Current 64-bit Debian- or Ubuntu-family server image | Provides familiar package management, security updates and Docker support. |
| Network | Stable public IPv4 or DNS name, IPv6 if needed, and predictable egress limits | Remote access, integrations and image downloads depend on reachable networking. |
| Administration | SSH access, a non-root administrator and provider firewall/security-group controls | Lets you harden and recover the host without exposing unnecessary services. |
A small installation with modest history may run comfortably at the minimum. If you plan to retain years of recorder data, run video analysis, host an MQTT broker and database, or process voice locally, start larger or choose a VPS that permits an easy resize. Check whether disk expansion, snapshots and additional memory can be added without rebuilding the server.
Prepare the VPS before installing Home Assistant
- Create a 64-bit server. Select a current Debian- or Ubuntu-family image on
amd64oraarch64. Avoid 32-bit images even if the provider still lists them. - Create a non-root administrator. Upload an SSH public key, grant administrative privileges through the distribution’s normal mechanism, and test a second SSH session before disabling root access.
- Apply security updates. Enable the image’s automatic security-update facility where practical, then reboot if the kernel or other core packages require it.
- Set the host time zone. Use the household’s chosen IANA time-zone name consistently. Home Assistant can use a different zone from the provider’s data-center location, but choosing deliberately prevents confusing timestamps.
- Configure the provider firewall. Initially allow SSH only from trusted administration addresses. Permit HTTPS (TCP 443) once a reverse proxy is ready. Do not expose Docker’s API.
- Confirm storage and DNS. Point a stable DNS name at the VPS if you intend to use HTTPS, and verify that the data disk is mounted before placing the Home Assistant configuration on it.
Install Docker Engine and Compose
Home Assistant’s Linux Container instructions require Docker Engine 23.0.0 or later. Install Docker Engine, not Docker Desktop, on the server. Use your distribution’s current Docker packages or Docker’s installation instructions, then verify the versions:
docker --version
docker compose versionOn Debian- or Ubuntu-family systems, the package names commonly include the Docker engine and Compose plugin. Package names and repository steps change, so use the current instructions for your exact distribution rather than copying an old third-party script. Add your administrator to the Docker group only if you understand that Docker-group membership is effectively root-equivalent; otherwise run Docker commands with the appropriate elevated privilege.
Create a persistent Home Assistant Container
Make a directory that is independent of the container’s writable layer. A path such as /opt/homeassistant/config is easy to back up and reference from Compose:
sudo mkdir -p /opt/homeassistant/config
sudo chown -R $USER:$USER /opt/homeassistantIn /opt/homeassistant/compose.yaml, use a Compose definition based on Home Assistant’s documented pattern:
Rank #2
- 【AMD Ryzen 3 5300U CPU: Outperforms N150 & 3500U】 BOSGAME E5 mini PC is powered by the TSMC 7nm FinFET architecture AMD Ryzen 3 5300U processor (4 Cores, 8 Threads, up to 3.8GHz boost, 6MB total cache). Compared to low-end Intel N150 or 3500U chips which only have 4 single threads and throttle under load, the 5300U delivers over 30% faster multi-core speed. Run 30+ browser tabs, large Excel sheets, and Zoom meetings simultaneously without system lag.
- 【8GB DDR4 RAM & 256GB NVMe SSD Storage】 Installed with high-speed 8GB DDR4 dual-channel memory and a fast 256GB M.2 2280 SSD, eliminating slow boot times and application loading delays. To accommodate growing data requirements, the upgradeable hardware design features dual SODIMM slots that allow you to expand memory up to 64GB RAM, ensuring smooth operation during heavy multitasking.
- 【High-Capacity Dual M.2 SSD Storage Expansion】 Never worry about running out of space for your business files. In addition to the pre-installed 256GB system drive, the motherboard houses an extra empty internal M.2 2280 NVMe PCIe 3.0 slot. This allows you to easily add a second solid-state drive for up to an additional 2TB of storage capacity (upgrades not included) without needing to remove or reinstall the original operating system.
- 【Radeon 6-Core Graphics & Triple 4K Displays】 Integrated with official AMD Radeon Graphics (6 Graphics Cores, 1500 MHz frequency) for casual gaming, photo editing, and crisp 4K media decoding. Featuring 1x HDMI 2.0 port, 1x DisplayPort, and 1x Full-Function Type-C port, the E5 outputs true 4K@60Hz resolution to three monitors at once. This multi-screen setup eliminates constant window-switching for traders, programmers, and office workers.
- 【Dual 2.5GbE LAN Ports for Advanced Networking】 Experience fast wired network transmission speeds up to 2500Mbps without lagging or buffering. The integration of dual 2.5 Gigabit Ethernet ports (powered by Realtek RTL8125 controller) makes this compact computer an exceptional hardware choice for tech enthusiasts. Easily configure it into software routers, hardware firewalls (pfSense, OpnSense), home NAS servers, or local homelabs.
services:
homeassistant:
container_name: homeassistant
image: ghcr.io/home-assistant/home-assistant:stable
volumes:
- /opt/homeassistant/config:/config
- /etc/localtime:/etc/localtime:ro
- /run/dbus:/run/dbus:ro
restart: unless-stopped
stop_grace_period: 60s
privileged: true
network_mode: host
environment:
TZ: Europe/AmsterdamReplace Europe/Amsterdam with the IANA time-zone name you selected. The host-network setting means Home Assistant listens directly on the VPS network, including its default port 8123. The /config bind mount is the critical persistence setting: deleting and recreating the container should not delete your configuration or database.
The example uses privileged mode and the D-Bus mount because some integrations expect host-level access. Privileged containers increase the impact of a container compromise, so do not add unrelated services to this container and keep the host patched. If your integration set allows a narrower device and capability configuration, adopt that deliberately and test it rather than removing settings blindly.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsStart the service from the directory containing compose.yaml:
cd /opt/homeassistant
docker compose up -d
docker compose ps
docker compose logs --follow homeassistantWhen the logs show that Home Assistant is running, browse to http://VPS-IP:8123 from a temporarily permitted administration network and complete onboarding. If the provider firewall blocks 8123, allow it only for the onboarding period or use an SSH tunnel; do not leave an unauthenticated setup endpoint on the public internet.
Complete onboarding without creating a security liability
- Create a unique administrator password that is not reused anywhere else.
- Enable multi-factor authentication in your Home Assistant user profile after the account is created.
- Store API tokens, webhook secrets and other credentials outside public repositories. Restrict permissions on any local secret files and on the VPS account that can read them.
- Set the correct location, unit system and time zone. These values affect sun triggers, weather, energy calculations and displayed history.
- Configure recorder retention before the database grows without bound. Keep only the history you actually need, and place large media or camera data on storage sized for it.
Make remote access private or properly encrypted
Port 8123 is Home Assistant’s default local listener, not a finished internet-facing design. A raw public http://VPS-IP:8123 URL sends credentials and session traffic without TLS and exposes the application directly. Choose one of these patterns instead.
VPN access
A VPN such as Tailscale or another WireGuard-based service places your phone or laptop on a private network before it connects to Home Assistant. This avoids public port forwarding and is often the simplest design for a personal installation. Restrict the VPS firewall so 8123 is reachable only through the VPN interface or local host, then use the VPN address or private DNS name. You still need to maintain the VPN software and user access.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Home Assistant Cloud
Home Assistant Cloud is the managed option recommended in Home Assistant’s remote-access documentation as the easiest and safest choice for most people. It supplies a remote URL without router port forwarding or your own certificate and reverse-proxy configuration. It is a subscription service, so account for that recurring cost and dependency when choosing the architecture.
HTTPS reverse proxy
Run Caddy, Nginx, Traefik or a provider edge proxy on the VPS, obtain a certificate for your DNS name, and forward HTTPS traffic to Home Assistant on the local host. Expose TCP 443 publicly and keep 8123 closed to the internet. Home Assistant must be told which proxy addresses are trusted so it can safely interpret forwarded client information.
Rank #3
- 【MAX 7735U High Performance 】Powered by the AMD Ryzen 7 7735U (8-Core, 16-Thread, boost up to 4.75GHz), this Beelink SER5 MAX mini PC delivers robust performance for daily office tasks, including spreadsheet editing, PPT creation, email management, coding and web browsing. It effortlessly handles photo and video editing via PS, PR and Lightroom, and runs popular esports titles such as LoL, CSGO and DOTA 2 at excellent settings.
- 【High‑Speed Memory & Storage】 Equipped with 24GB high-speed LPDDR5 RAM and a blazing-fast 500GB M.2 2280 PCIe 4.0 SSD, this BEELINK 7735U MINI PC supports seamless heavy multitasking. It features expandable storage up to 8TB, letting you store massive project archives and local files without worry.
- 【4K Triple Display & Radeon 680M Graphics】 Built-in AMD Radeon 680M Graphics (12-Core, 2200MHz) brings outstanding graphic performance for design work and buttery-smooth 4K HDR video playback. This BEELINK SER5 MINI PC supports triple 4K monitors via HDMI, DP and USB-C port, allowing you to run trading dashboards, spreadsheets and design drafts side-by-side to boost your productivity.
- 【Cooling & Full Connectivity】 This BEELINK SER5 7735U MINI PC adopts an upgraded dual‑cooling system with heatsink and cooling fan that boosts heat dissipation by 19% while keeping noise below 32dB for quiet operation. Equipped with WiFi 6, Bluetooth 5.4 and 2.5G RJ45 Ethernet port, it delivers stable, lag‑free connections ideal for office work, home media and home‑server use.
- 【Lifetime Technical Support】Ryzen 7 mini pc Package Included:1* Beelink Ser5 7735U Mini PC,1* HDMI Cables( 100cm),1* Power adapter,1* User manual,1* Mounting bracket.If you want to set up automatic startup,please contact us.All of our mini pc obtained FCC,CE ROSH Certifications.We Offer 1 Year Free Warranty,and 7 Days/24 Hours Serving,and lifetime technical issue assistance without worrying about quality,just email to our customer service team.
http:
use_x_forwarded_for: true
trusted_proxies:
- 10.0.0.0/8Replace the example network with the actual reverse-proxy address or subnet; trusting a broad or incorrect range can let an untrusted client spoof its source address, while omitting the proxy causes Home Assistant to block requests. Reload and test from both an internal administration connection and a mobile connection. Keep certificate renewal, DNS records and proxy configuration in the same backup plan as the Compose file.
Plan for Zigbee, Thread, Z-Wave and Bluetooth radios
A cloud VPS normally has no USB port connected to the radio hardware in your home. Installing the container does not magically provide Zigbee, Thread, Z-Wave or Bluetooth capability. Before promising those integrations, decide where the coordinator will live.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
- Use a network-capable coordinator or bridge that Home Assistant can reach over the network.
- Keep the USB radio on a home computer or small local server and expose it using a supported network method, accounting for latency and outage behavior.
- Run Home Assistant on hardware physically near the devices when reliable Bluetooth or proprietary radio access is more important than cloud availability.
- Check each integration’s supported coordinator and connection method; do not assume that a generic USB-over-IP service will be reliable.
Design automations so essential household functions fail safely when the VPS, VPN or internet connection is unavailable. A remote VPS can be excellent for dashboards and internet integrations while still requiring local infrastructure for time-critical radio devices.
Secure the host and the Home Assistant account
- Use SSH keys, disable password authentication when you have verified key access, and set
PermitRootLogin noin the SSH configuration. - Allow SSH only from trusted administration addresses through the provider firewall or host firewall. Open HTTPS 443 only when a reverse proxy is configured.
- Keep the operating system, Docker Engine, reverse proxy and Home Assistant image updated. Remove unused containers, images and listening services.
- Use a strong, unique Home Assistant password and multi-factor authentication for every administrator.
- Never expose the Docker socket or Docker API to the public network. Treat access to the Docker group as privileged host access.
- Review login and proxy logs after deployment. Unexpected authentication failures, unfamiliar API clients or repeated restarts are reasons to investigate before expanding access.
Backups that survive a VPS failure
Home Assistant backups are encrypted compressed archives. Configure automatic backups in Settings → System → Backups, download and protect the emergency kit, retain multiple restore points, and enable a second location outside the VPS. Keep at least one copy off-site: a local /backup directory on the same virtual disk will not help if the provider deletes the instance, the disk fails or an attacker gains account access.
Back up more than the Home Assistant archive. Preserve the Compose file, reverse-proxy and certificate configuration, firewall rules, DNS records, radio-coordinator settings and any external database or MQTT configuration. Store these files in a secured repository or storage location that is not mounted read-write inside the Home Assistant container.
For a business-critical system, create a spare VM and perform a restore test. A backup that has never been restored is an assumption, not a recovery plan. Record the emergency-kit location and the order in which DNS, Docker, companion services and Home Assistant must be restored.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Update Home Assistant without losing the installation
Read the release notes before every upgrade, especially when a release contains backward-incompatible changes. Create a fresh backup, then pull and recreate the container:
cd /opt/homeassistant
docker compose pull homeassistant
docker compose up -d
docker compose logs --follow homeassistantKeep the previous image available until you have confirmed that integrations, automations, dashboards and external services work. If the new container fails, inspect logs first, stop dependent changes, and restore the last known-good configuration and image according to your rollback plan. Do not delete the persistent /config directory while troubleshooting.
Rank #4
- MINI PC COMPUTER OFFICE LIGHT GAMING - GMKtec Nucbox G10 Series is equipped with the Ryzen 5 3500U, a 64-bit quad-core mid-range performance x86 mobile microprocessor. This processor is based on AMD's Zen+ microarchitecture and is fabricated on a 12 nm process. The 3500U operates at a base frequency of 2.1 GHz with a TDP of 15 W and a Boost frequency of 3.7 GHz. This APU supports up to 32 GB of dual-channel DDR4-2400 memory and incorporates Radeon Vega 8 Graphics operating at up to 1.2 GHz. 20% Multi-core Performance increase over previous Ryzen 3 models such as 4300U. 35% performance increase over the Intel N-series N95/N97/N150.
- RYZEN 5 3500U vs RYZEN 3 4300U COMPARISON - Why Choose Ryzen 5 3500U: Better multi-threaded performance: More threads, better suited for multitasking and demanding applications. Better graphics: With Vega 8, it's superior for casual gaming, video playback, and GPU-intensive tasks. Overall higher performance: Higher boost clock and better ability to handle a variety of workloads, from light gaming to productivity tasks. So, if you're looking for a more balanced processor with stronger multitasking capabilities and better GPU performance, the Ryzen 5 3500U would be the clear choice.
- 16GB DUAL CHANNEL DDR4 + 512GB SSD - Installed with DDR4 16GB SO-DIMM RAM Dual Channel (2x8GB) and a 512GB SSD, the Nucbox G10 mini pc supports memory expansion to 64GB RAM. Featured with Dual M.2 2280 PCIe 3.0 slots, supports dual storage slot expansion to 16TB SSD (2*8TB). (Upgrades not included) This model supports a configurable TDP-down of 12 W and TDP-up of 35 W.
- UNLEASH RAW PERFORMANCE MODE 25W - Dominate demanding tasks with the AMD Ryzen 5 3500U processor. When switched to Performance Mode in the BIOS (press "Esc" key repeatedly during boot, save then exit), this mini PC delivers superior multi-core processing power, significantly outperforming Intel N-series chips in CPU-intensive applications, multitasking, and creative workloads.
- MINI DESKTOP COMPUTER WITH TRIPLE DISPLAY SCREEN - Nucbox G10 integrates AMD Radeon Vega 8 1200 MHz GPU to deliver powerful graphics processing power to easily handle video editing, and playback, or casual gaming. And it can connect to 3 display screens simultaneously via HDMI 2.1 TMDS/ DPv1.4/ TYPE-C.
How to compare VPS offers for Home Assistant
Provider marketing often emphasizes a low monthly price, but reliability and recovery features matter more for a home-control system. Compare these items before ordering:
| Comparison point | Questions to ask |
|---|---|
| CPU and architecture | Is the plan genuinely 64-bit amd64 or aarch64? Are vCPUs shared, and can the plan be resized? |
| Memory and disk | Does RAM cover Home Assistant plus databases and proxies? Is storage SSD-backed, expandable and included in snapshots? |
| Backups | Are provider backups separate from the VM disk, how often do they run, how long are they retained, and can you download or restore them? |
| Network | Are IPv4 and IPv6 available? What are egress limits, inbound filtering options and regional latency to your home? |
| Firewall controls | Can you enforce security groups before traffic reaches the VM, and can rules be limited to trusted SSH addresses? |
| Availability and support | What maintenance notices, recovery console and support channels exist when the VM will not boot? |
| Total recurring cost | Include snapshots, extra disks, backups, IPv4 addresses, egress and any managed VPN or cloud-remote-access subscription. |
Do not select a provider solely because it advertises a one-time introductory rate. A slightly more expensive plan with reliable snapshots and a usable recovery console can reduce the cost of an outage.
Common failure modes and fixes
The browser cannot reach port 8123
Check that the container is running with docker compose ps, inspect logs, verify that network_mode: host is present, and confirm both the provider firewall and the host firewall. If you intentionally closed 8123 after configuring a VPN or proxy, connect through that approved path instead of reopening the port publicly.
Home Assistant starts with an empty setup
The container is probably using a different host directory. Confirm that the Compose file maps the intended absolute path to /config, that the path is mounted, and that the expected files exist before recreating the container. Never create a second empty directory over the original configuration.
Proxy requests are rejected
Verify that use_x_forwarded_for is enabled only when a proxy is actually in front, and set trusted_proxies to the proxy’s real address or subnet. A wrong value either blocks legitimate requests or trusts clients that should not be trusted.
A Zigbee or Bluetooth integration cannot find its device
The VPS likely has no physical radio. Move the coordinator to a network-capable or local host arrangement supported by the integration, then verify network reachability and coordinator firmware. USB device paths from a home computer do not automatically exist inside a cloud VM.
An update causes missing integrations or slow history
Check release notes and container logs, confirm available RAM and disk, and examine recorder database growth. Restore the latest known-good backup on a spare VM if the production instance cannot be diagnosed safely.
When a VPS is the wrong architecture
Choose local hardware instead when your automations must continue during an internet outage, when most devices depend on USB radios, or when your home’s cameras and media would make cloud storage and egress expensive. A hybrid design is also valid: keep radio-dependent control local and use a secure tunnel or cloud service for remote dashboards. The right choice is the one that matches failure tolerance, not simply the one with the lowest server price.
Bottom line
Host Home Assistant on a VPS with a 64-bit Linux image, Docker Engine 23.0.0 or newer, and a persistent /config volume. Use Home Assistant Container for the normal VPS case, accept that apps and automatic host management are absent, and protect remote access with a VPN, Home Assistant Cloud or a correctly configured HTTPS reverse proxy. Treat encrypted off-site backups, SSH hardening, MFA, firewall rules and a radio-coordinator plan as part of the deployment—not optional follow-up work.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
