Cloud VPS 6 GB
Most popularDashboards and cloud automations for one household or team.
$24.99per month
- 6 GB RAM
- 4 vCPU cores
- 100 GB NVMe SSD
- 30 TB
- Unlimited
Home Assistant hosting for dashboards, automations and webhook flows, run as a self-hosted home automation platform on your own domain. Deploy Home Assistant 2026.9.4 from the official container image, pinned by digest, with a persistent config volume, so settings, users and integrations survive restarts, and HTTPS provisioned for you. It runs in the cloud, so it cannot reach devices on your local network.
Self-hosted Home Assistant is a home automation platform written in Python. Upstream describes it as open source home automation that puts local control and privacy first, built in a modular way so support for other devices or actions can be added easily. It is licensed under Apache-2.0 and is a self-hosted alternative to cloud hubs such as SmartThings.
This template is a cloud-hosted install, not a smart-home hub for local devices. On xCloud it runs the official Home Assistant Container image at 2026.9.4 on an isolated Docker network, with one ha_config volume mounted at /config and HTTPS on your domain. It suits cloud services, MQTT, webhooks and dashboards. Local discovery, USB, Bluetooth, UDP and the add-on store are not available.
Installing Home Assistant means a container, a persistent config folder, a domain and HTTPS before the first automation runs. This is the same result without assembling any of it.
Step 01
Create your xCloud account, pick Home Assistant from the OneClick catalog and select a domain. No extra fields are needed.
Step 02
We start the pinned 2026.9.4 image, mount the ha_config volume at /config and serve it over HTTPS on your domain.
Step 03
Open the HTTPS URL right away and create the owner account. Whoever opens the page first becomes the owner.
The Home Assistant container runs here with HTTPS and persistent config. Local-network discovery and hardware are outside this install.
Build dashboards, automations, scripts and scenes from one web interface, reachable over HTTPS from anywhere you sign in.
Connect cloud services, MQTT brokers, webhooks and REST or WebSocket clients to the automations you build in Home Assistant.
Your /config folder lives on the ha_config volume, so YAML, users, integrations and the database survive restarts.
The owner account you create on first open stays in place after an xCloud Restart, and no preset password exists.
xCloud serves HTTPS with reverse-proxy trust preconfigured, so proxied requests are not rejected by Home Assistant.
No local discovery (mDNS, SSDP, DHCP), USB, Bluetooth or add-on store, since this runs on an isolated Docker network.
xCloud runs the server, HTTPS and the Home Assistant container. You own the dashboards, automations and integrations you build.
A hobbyist or small team pulls data from the cloud services they already use into one set of dashboards, reachable over HTTPS from any browser without exposing a home router.
A developer triggers automations from outside services by calling webhooks, then chains scripts and scenes so an incoming event updates a dashboard or calls another REST service.
An integrator whose devices already publish to an MQTT broker reachable from the server wires those messages into Home Assistant automations and scenes, with configuration saved on a persistent volume.
Someone who wants their YAML, users and integrations in one backed-up place keeps the whole /config folder on a Cloud VPS they control, instead of on a single local machine.
Dedicated Cloud VPS sizes, pre-configured for Home Assistant hosting. Pick the one that fits, and resize any time.
Dashboards and cloud automations for one household or team.
$24.99per month
Room for longer histories and more integrations.
$59.99per month
Home Assistant alongside a larger self-hosted stack.
$84.99per month
Every size is a dedicated Cloud VPS that xCloud provisions. Billed monthly with no lock-in. Home Assistant is free under Apache-2.0; you pay for the server it runs on.
Connect any VPS and deploy Home Assistant on it through the same panel, for a per-server management fee instead of a Cloud VPS rental.
Start your journey without cost.
$0forever
Your rate with 2–5 servers connected.
$5per server / month
The same platform, discounted at 6–10 servers.
$4per server / month
The same platform, discounted at 11+ servers.
$3per server / month
Priced per connected server, so your rate adjusts automatically as you add or remove servers. You pay your own provider for the server itself.
Home Assistant on xCloud runs on a dedicated Cloud VPS for cloud-service and MQTT automations. Deploy in minutes, then keep control of your config.
Deploy faster using an xCloud Managed Server built with optimized stacks and high-speed SSDs.
Protect your infrastructure with a free SSL certificate and more advanced security features at no additional cost.
From Server creation to application deployment, everything can be managed from our intuitive control panel.
See why agencies, developers, startups, and growing businesses choose xCloud to power their projects.
xCloud works really well, I am surprised by its performance being this the release version, I have tried many paid platforms such as runcloud, cloudpages or serveravatar, as well as free platforms such as CyberPanel, CloudPanel or Hestia Control Panel and direct competitors such as SpinupWP and FlyWP. Of all those that I have tried, the platform that works best for WordPress is SpinupWP and I believe that xCloud can reach and surpass that development, its roadmap is promising. Congratulations to the xCloud team, I hope they become the leading platform in the segment, it has all the potential to achieve it!
Brian GeovannyI've been with runcloud for the last 3 years. However, after trying xcloud for the last month, I'm switching over. They are on a roll with their setup.
Kevin PinedaI'm moving my servers to xCloud, a cloud control panel by M Asif Rahman and the WPDeveloper team. Their roadmap looks interesting and no, there are no team mates nor API limits with xCloud! #xCloud #wordpress #hosting
Leo KooHow Cloud Nine Web Elevated Client Experience While Streamlining Hosting Operations using xCloud
Ed EllinghamxCloud is like having an expert server team on call — without the big agency costs. It's given me back my time and given my clients peace of mind. Highly recommended for freelancers and small teams who want reliable performance and security.
Dumitru ButucelxCloud isn't just a solution. It's like one of that friend who got your back when you screw things up pretty bad.
Waqar AhmedTrust me when I say, once people explore the potential of xCloud they gonna switch from other panels, just keep delivering the best tech, lots of love for the team 😍😍
Rahul SinghSo far my experience has been smooth like silk. I didn't imagine that configuring and managing a VPS would be so easy. As of today, I have deployed 8 sites. The support is good, and they treat users with respect, even if they ask stupid questions (myself included). For the future, I hope for greater flexibility in scheduled backups and more comprehensive and consistent documentation. I'm sure that within a few months, xCloud will become the leader in its segment. This community is amazing, and the Staff here is super helpful.
Massimo VillaCame from cloudways then to runcloud then to xcloud. Looks like I'm staying here.
Gerson ElI've recently taken all of my Vultr-hosted sites and gotten rid of cPanel for them to substitute it with xCloud. I have to say, I'm really impressed with xCloud so far! The interface is definitely the standout feature for me.
Tony LewisI came from Cloudways and won't go back. Highly impressed with xCloud. Glad I gave them a chance.
Jared McDowellI like xCloud better than RunCloud, but one thing I'll point out is that some years ago RunCloud was hungry for business, the support was outstanding, and the community was active and helped each other. Maybe it was sold, there was a change in management, or they stopped being hungry, but the quality of the RunCloud offering declined and it hasn't been moving forward quickly. My point is that currently the xCloud team has the edge and it is theirs to keep or lose
David McCanHow Kevin Heinrichs Cut Hosting Costs by 84% While Running WooCommerce & Node.js Sites Efficiently
Kevin HeinrichsI had 150 sites on cloudways and am in the process of moving them to xcloud. Much faster and better priced.
Dan SpinozaDear xCloud Team, I have been using xCloud for some time now and am genuinely impressed with its capabilities and the flexibility it offers by allowing users to bring their own VPS for management. It's a fantastic service, and my experience so far has been very positive. Successful migrated 5 sites on a single server. Xcloud migration tool worked great. There were few hiccups with security plugin like MalCare but disabling the plugin prior to migration worked just fine.
Rahil MaknojiaCame from runcloud. Tried xcloud and never came back.
Karl FanegaHow Advanced Web Strategies Saved Over $2,000 & Recovered 56 Hours per Month Managing 70+ Client Websites
Gary MoodyxCloud gave me what no other hosting platform could: the flexibility of a VPS with the convenience of managed WordPress. As a solo founder running an entire business on one server, that combination is an important unfair advantage.
Jorge de los Reyes MartínezI use Server Avatar and xCloud and I'll sooner use xCloud than Server Avatar personally.
Jay PaganoHow Newman Web Solutions Ensured Perfect Uptime and Seamless Scaling For 120+ WordPress Sites with xCloud
Lori NewmanI too have moved over to xCloud. It's pretty sweet. One click n8n and uptime Kuma apps
John ApertureI went from Cloudways to xCloud. No intention on switching in the foreseeable future.
Blaine MooreFeel free to contact us with any questions or concerns you may have.
Yes. Home Assistant is open source under Apache-2.0, so running it costs nothing in licences. What you pay xCloud for is the dedicated Cloud VPS hosting the container, plus the HTTPS route and deployment. No Home Assistant subscription is bundled, and none is needed for the dashboards, automations or webhooks described here.
Yes. This template runs the official Home Assistant Container image, ghcr.io/home-assistant/home-assistant at 2026.9.4, pinned by digest, with ha_config mounted at /config and port 8123 proxied over HTTPS. It gives you Home Assistant Docker hosting without writing the compose file or a reverse proxy.
Yes, with limits. A VPS suits cloud services, MQTT, webhooks, REST and WebSocket clients, dashboards and automations. It cannot reach devices on your home network, so if most of your devices are local-only, run Home Assistant on the same network as those devices instead.
No. The add-on store is not part of the Container image, and this template does not add one. You get Home Assistant core with its integrations and custom components in /config. Anything that needs a separate add-on has to run as its own service beside it.
No. The install runs on an isolated Docker network without host networking, so local discovery by mDNS, SSDP or DHCP does not work. Integrations that rely on devices answering on your LAN will not find them from a cloud server.
No. USB dongles such as Zigbee and Z-Wave, Bluetooth and UDP-based integrations are unavailable on this cloud-hosted install, because the server has no access to your radios. Cloud-connected devices and MQTT work, since they reach Home Assistant over the network.
Updates are deliberate. The image is pinned to an exact tag and digest, and existing installs stay on it when the catalogue changes. Back up the full /config volume, read the upstream release notes for breaking changes, pin the new tag and digest, redeploy without deleting volumes, then check login and automations.
The template asks for 1024 MB of RAM, 1 CPU core and 8 GB of disk as a baseline, and this page sells the 6 GB Cloud VPS for headroom. Large histories, many integrations or camera and media features need more, so watch memory as you add them.
Everything is in the ha_config volume mounted at /config: configuration.yaml, YAML includes, the .storage directory with users, tokens, integrations and HTTP settings, the database and custom components. Take one backup of the whole volume and restore it as a unit.
No. This is a Home Assistant install running on your own Cloud VPS, not the separate Home Assistant Cloud subscription service. You own the server, the owner account and the ha_config data on it, and the site works without any Home Assistant subscription.
Whoever opens the site first. Home Assistant has no preset account, so open your HTTPS URL as soon as the install finishes and create the owner account immediately, before you share the address. The first start can take a few minutes while integrations load.
Yes. There is no lock-in — cancel any time. Hosting is billed monthly and charged for what you actually use, so when you delete the server the unused balance is refunded to your account, less up to 10% in payment-processing fees.
Deploy Home Assistant 2026.9.4 in minutes, with HTTPS and persistent config already in place.