Shared Compute - General Compute
$12.49/mo
2 vCPU · 4 GB · 40 GB
Choose location
Phoenix, United States
| Provider | Plan | vCPU | RAM | Disk | Regions | Billing | Price |
|---|---|---|---|---|---|---|---|
| Virtualized | Shared Compute - General Compute | 2 | 4 GB | 40 GB | Phoenix, United States | Fixed price | $12.49/mo |
| Virtualized | Shared Compute - General Compute | 3 | 6 GB | 60 GB | Phoenix, United States | Fixed price | $17.49/mo |
| Virtualized | Shared Compute - General Compute | 4 | 8 GB | 80 GB | Phoenix, United States | Fixed price | $22.99/mo |
| Virtualized | Shared Compute - General Compute | 8 | 16 GB | 160 GB | Phoenix, United States | Fixed price | $44.99/mo |
| Virtualized | Shared Compute - General Compute | 16 | 32 GB | 320 GB | Phoenix, United States | Fixed price | $79.99/mo |
| Virtualized | Shared Compute - General Compute | 32 | 64 GB | 640 GB | Phoenix, United States | Fixed price | $139.99/mo |
Home Assistant Instant App
Home Assistant is an open-source smart home hub for automations, dashboards and thousands of integrations. Compare live VPS prices, CPU, RAM, disk and regions, launch with a prepared owner login on the plan you choose, and keep root access.
Home Assistant
Instant App on marketplace VPS
Live marketplace offers
Choose billing and size, compare providers side by side, pick a location, then launch.
1 provider
Home Assistant is a self-hosted smart home platform for dashboards, automations and device integrations. Use it instead of paying for SmartThings or Alexa cloud. Sign in as owner after boot and add integrations. No Instant App form fields are required at create time.

Open Home Assistant and sign in with the prepared owner account. Your overview dashboard is ready.

Build automations that run on your VPS instead of a vendor cloud.

Manage devices, people and system options from Settings after first login.

Change password and profile options after first login.
Compare live Home Assistant VPS plans from independent providers, then self-host a smart home hub on the offer you pick. Use it instead of paying for SmartThings or Alexa cloud.
See live prices, regions and plan sizes before you buy. Shop smart-home hosts across independent providers, including 2 GB boxes that fit Home Assistant well.
Pick a plan and Home Assistant is prepared on that VPS for you, including the owner account. You still get root access.
Compatible offers list cities and countries. Latency for the UI and some cloud bridges follows the region you pick.
Dashboards, automations and config live on your VPS volume. You control SSH, DNS and who can sign in.
Most Home Assistant VPS pages sell one company's servers. NodeRings lists Compute Instance plans from independent providers so you can compare self-hosted smart home offers by price, size and region, then launch on the one that fits.
Home Assistant Instant App prepares Home Assistant on the provider VPS you selected. NodeRings does not operate that hardware or sell its own VPS fleet.
Compare plans, pick a provider offer, and launch Home Assistant on that server.
01
Browse live offers below. A 2 GB plan is a solid start for Home Assistant. Sort by provider, size, price and region.
02
Choose the provider plan and region. There are no Instant App form fields to fill for Home Assistant.
03
Confirm checkout and wait for the server. Then open http://YOUR_IP/ and sign in with homeassistant_admin_user and homeassistant_admin_pass from your server notes. You keep root SSH.
NodeRings Instant App brings Home Assistant up with Docker and prepares first-boot access for you. Use the sections below to reach the UI, find passwords, and operate the stack.
Credentials are written on first boot to:
/root/.noderings_passwordRead them over SSH:
cat /root/.noderings_passwordCompose project directory
/opt/noderings/home-assistant
/opt/noderings/home-assistant/docker-compose.yml
/opt/noderings/home-assistant/.envWorking directory for compose, the stack file, and generated secrets.
Credentials file
/root/.noderings_passwordWritten once on first boot.
Boot unit
/etc/systemd/system/noderings-home-assistant.serviceBrings compose up after Docker is ready.
Compose runs a single Home Assistant container with config under /config. The UI is on HTTP port 80 (container port 8123).
homeassistantHome Assistant web UI and API on HTTP port 80.
Container status
cd /opt/noderings/home-assistant && docker compose psLive logs
cd /opt/noderings/home-assistant && docker compose logs -fRestart containers
cd /opt/noderings/home-assistant && docker compose restartsystemd unit status
systemctl status noderings-home-assistantYour Home Assistant app starts on http://. Cloudflare can give visitors a padlock without installing anything on the VPS.
Add your domain
Sign up at Cloudflare and add the domain you want to use.
Point it at your VPS
Create an A record to your server IP and leave the orange cloud on.
Open the https site
Visit https://your-domain and sign in with the owner credentials from your server notes. You may need to set trusted proxies / external URL in configuration.yaml for HTTPS reverse proxies.
Only allow Cloudflare
Optional. With SSH (port 22) already allowed and everything else blocked by default, open only Cloudflare to ports 80 and 443:
curl -s https://www.cloudflare.com/ips-v4 | while read ip; do sudo ufw allow from "$ip" to any port 80,443 proto tcp; doneKeep port 22 allowed for SSH.
Home Assistant runs as a single Docker container with a config volume. A quiet personal hub needs about 2 GB of RAM; many integrations and add-ons need headroom. These are starting points, not guarantees.
| Workload | Illustrative starting point | Note |
|---|---|---|
| Personal smart home hub | 1 vCPU / 2 GB RAM / 20+ GB disk | Suggested Instant App floor for Home Assistant Container. |
| Many integrations | 2 vCPU / 2–4 GB RAM | More headroom when cameras, energy and dozens of devices are connected. |
| History and media | Disk sized to recorder DB and media | History and media grow the config volume. Keep copies off-box. |
| Local device discovery | Same size; network access to LAN | Some local discovery works best when the VPS can reach your home network (VPN or colocated). |
These are starting points, not guarantees. Needs depend on integrations and history retention.
This is self-hosted Home Assistant on a provider VPS, not managed SmartThings. You pick the plan. Home Assistant is prepared on that server. Day-to-day care stays with you.
Home Assistant is prepared on the VPS with no Instant App form variables. The owner account is created for you via the onboarding API on first boot.
Root SSH on the VPS. You own automations, dashboards, integrations, DNS, TLS, OS updates and backups unless a provider product says otherwise.
Home Assistant OS, Supervisor add-ons, automatic TLS and vendor cloud bridges are not bundled in. Finish TLS and connect devices after the server is up if you need them.
NodeRings helps with marketplace, billing and console. Provider hardware issues go to that provider. Looking after Home Assistant on the server is yours.
Home Assistant is a free, open-source smart home platform. People use it for dashboards, automations and device integrations on hardware they control.
No. Home Assistant Instant App asks for no form variables at create time. After the VPS is ready, sign in with the owner username and password from your server notes.
No. NodeRings is a marketplace. Independent providers list VPS plans. You pick a plan, Home Assistant is prepared on that provider server, and you manage the hub from there.
No. You get a virtual machine with Home Assistant prepared for you, plus root access. That is different from SmartThings or a managed product that owns updates and support for you.
It prepares Home Assistant Container on the VPS you choose so you skip hunting through install guides by hand. It is still your self-hosted server, not a separate managed hosting brand.
Open http://YOUR_IP/ and sign in with homeassistant_admin_user and homeassistant_admin_pass from /root/.noderings_password.
Yes. Sign in and change the password in your profile. The onboarding API only creates the first owner once.
A common starting point is about 1 vCPU, 2 GB RAM and 20 GB disk for Home Assistant Container. Larger homes usually need more RAM. Use the sizing guide above and compare plans in the list.
You confirm the plan and finish checkout. When the server is ready, open the site URL and sign in with the owner credentials from your server notes.
Yes. Each compatible plan lists available regions. Pick the city or country that matches latency and compliance needs.