Home Assistant Hosting on Your Own VPS
Automation with a fixed public address, long history and no subscription for remote access.
Size a server for Home Assistant
Every stop is a real configuration you can deploy. Priced per month and billed monthly, exclusive of 18% GST.
What Home Assistant is
Home Assistant is an open-source home automation platform with integrations for thousands of devices and services. Most installations run on hardware at home, and for good reason — many devices speak Zigbee, Z-Wave or local-only protocols that require a radio on the local network.
That is the honest limitation of running it on a VPS, and it should decide whether this is right for you. A cloud instance cannot see a Zigbee dongle in your living room. What it can do well is cloud-integrated automation: services with APIs, webhooks, presence via mobile apps, weather, calendars, energy tariffs and anything else that lives on the internet rather than the LAN.
Where a VPS clearly wins is remote access and history. A static public address with TLS means no dynamic DNS, no port forwarding on a home router, and no subscription for remote access. Long-term statistics stop being constrained by an SD card, which is the component that most often ends a Raspberry Pi installation.
“Open source home automation that puts local control and privacy first. Powered by a worldwide community of tinkerers and DIY enthusiasts.”
Why run Home Assistant on a VPS
A static public address with TLS — no dynamic DNS and no router port forwarding.
No subscription for remote access.
Disk that does not wear out, unlike the SD card in a typical home install.
Uptime independent of home power and broadband.
A VPN endpoint on the same machine can bridge back to local devices if you need both.
Home Assistant features
Thousands of integrations for cloud services and APIs
Automations, scripts and scenes
Dashboards for desktop and mobile
Long-term statistics and energy tracking
Mobile apps with presence detection
REST API and webhooks
Add-ons for related services
Home Assistant hosting requirements
The recommended starting point for Home Assistant, not a hard floor — size it on the sliders.
| Memory | 4 GB for a typical instance with several integrations |
|---|---|
| CPU | 2 vCPU |
| Storage | 40 GB; the recorder database grows steadily with history retention |
| Operating system | Ubuntu 22.04 LTS |
| Installs on | Ubuntu 24.04 LTS, Ubuntu 22.04 LTS, Debian 13 (Trixie), Debian 12 Bookworm, AlmaLinux 9, AlmaLinux 8, Rocky Linux 9, Rocky Linux 8 |
| Ready in | About 6 minutes |
| Smallest server | 2 vCPU · 4 GB memory · 20 GB disk |
| Admin account | You create it on Home Assistant’s own setup page once the install finishes. Whoever opens that page first can claim it, so do it right away. |
How deployment works
Home Assistant is installed in a Python virtual environment or as a container, behind TLS on your own domain. Be clear about the limitation before deploying: local-radio protocols such as Zigbee and Z-Wave need hardware on your local network, so a cloud instance either skips them or reaches them over a VPN you set up.
What people run it for
Cloud-integrated automation
Services, webhooks, calendars and weather driving automations.
Remote access done properly
Your own domain and TLS instead of exposing a home router.
Long history
Years of energy and sensor statistics on real disk.
Hybrid setups
A cloud instance with a VPN back to local radios for Zigbee and Z-Wave.
Home Assistant hosting questions
Related applications
Node-RED Hosting Event-driven flows for IoT, MQTT and API glue, on a server with a fixed address. 
OpenVPN Hosting Your own VPN server with a dedicated address and nobody else on it. 
Nextcloud Hosting File sync, sharing and collaboration on storage you own, without per-user pricing. 
Grafana Hosting Dashboards and alerting over your own metrics, without per-seat or per-metric billing. 
Immich Hosting A self-hosted photo library with mobile backup and search, on storage you own. Deploy Home Assistant on your own server
Root access, your choice of size, and no container between you and the application.