Self-host Home Assistant with Levelrail
Open-source home automation that puts local control and privacy first.
- Authorhome-assistant
- LicenceApache-2.0
- Memory512 MiB
- Archarm64
- Services1
How to self-host Home Assistant
-
Pull the images
One image is pulled on your server.
Show images
ghcr.io/home-assistant/home-assistant:2025.10.2
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on port 8123.
-
Fill in the secrets
You do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
Home Assistant requirements
- Memory
- About 512 MiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 8123
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- Apache-2.0, permissive license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
- Host ports. It publishes port 8123 on the host, so open them in the VPS firewall only if you want that.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Home Assistant. New to Levelrail? Install it on a fresh VPS first.
docker pull ghcr.io/glincker/levelrail:latest Then levelrail-cli login --device. See Getting started and the Home Assistant docs page.
Deploy Home Assistant your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Home Assistant from the CLI
levelrail-cli templates deploy home-assistant --name my-home-assistant Deploy Home Assistant with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/home-assistant/deploy Home Assistant configuration
Home Assistant services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| home-assistant | ghcr.io/home-assistant/home-assistant:2025.10.2 | 8123 | home_assistant_config -> /config |
Home Assistant environment variables
The catalog lists no environment variables for this template.
Ports and volumes
- Ports
- 8123
- Volumes
- 1 named mount: home_assistant_config -> /config
Home Assistant FAQ
How much memory does Home Assistant need?
The catalog lists about 512 MiB of memory for Home Assistant.
Does Home Assistant run on arm64?
For Home Assistant, an arm64 image is published; amd64 is image published.
What licence is Home Assistant under?
Home Assistant is licensed under Apache-2.0, which is permissive, with few conditions on reuse.
Does Home Assistant need configuration before it starts?
No. The template fills in its own defaults.
Which ports does Home Assistant use?
Home Assistant listens on port 8123 inside the stack.
Where does Home Assistant keep its data?
In a named volume: home_assistant_config mounted at /config.
Can I deploy Home Assistant on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list has an entry with the id homeassistant for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image ghcr.io/home-assistant/home-assistant:2025.10.2 is what you deploy there.