Bottom line: yes, Home Assistant runs fine on a 2 GB VPS — if your devices are cloud-connected or reachable over the internet. The catch: most smart-home gear (Zigbee, Z-Wave, local LAN devices) needs a USB dongle or local network, which a VPS can't give you. If you use cloud-based devices and want HA as a remote controller, a VPS is a great fit. If you have local radios, keep HA on a box at home.
The hardware split:
VPS works when: your devices are Wi-Fi / cloud / LAN-reachable, you want always-on remote access, and you don't need a Zigbee/Z-Wave USB dongle.
Local box wins when: you need a USB dongle for Zigbee/Z-Wave/Thread, or you want everything to work when your internet goes down.
When a VPS makes sense
- You use cloud or IP-based devices (many Wi-Fi bulbs, plugs, Tuya, ESPHome over IP).
- You want always-on remote access from your phone anywhere without a VPN tunnel home.
- You're comfortable with tailscale or a reverse proxy to reach it securely.
- You want no hardware on your desk — everything in one cloud box.
The honest tradeoff
The biggest gotcha: Home Assistant's most valuable integrations (local Zigbee/Z-Wave hubs, USB radios) cannot work on a VPS — there's no USB passthrough to a dongle you don't own. If your home is built around those, a VPS for HA is a trap. A good middle path: run HA at home and use a VPS as the always-on reverse proxy / remote entry point, which is often the better architecture anyway.
Specs for HA on a VPS
| Setup | RAM | vCPU |
|---|---|---|
| HAOS, a few integrations | 2 GB | 1–2 |
| HA + lots of integrations / media | 4 GB | 2 |
Provider-reported; see our methodology on how we treat untested data.
Run anything else on that box? Combine HA with n8n, Uptime Kuma, or your Docker stack — and read the RAM sizing guide before you oversubscribe it.