Self-host ESPHome with Levelrail
A dashboard to build, flash and manage firmware for ESP32 and ESP8266 smart home devices.
- Authoresphome
- LicenceGPL-3.0-only
- Memory512 MiB
- Services1
How to self-host ESPHome
-
Pull the images
One image is pulled on your server.
Show images
esphome/esphome:2026.10.2
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on port 6052.
-
Fill in the secrets
1 secret is generated and stored encrypted, 2 settings are preset, 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.
After the first start
- Sign in as admin with the generated password.
ESPHome requirements
- Memory
- About 512 MiB
- Architectures
- amd64 unknown, arm64 unknown
- Ports
- 6052
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- GPL-3.0-only, copyleft license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then ESPHome. 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 ESPHome docs page.
Deploy ESPHome your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy ESPHome from the CLI
levelrail-cli templates install esphome --name my-esphome Deploy ESPHome with the API
curl -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
https://levelrail.example.com/api/v1/service-templates/esphome/install \
-d '{
"name": "my-esphome"
}' ESPHome configuration
ESPHome services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| esphome | esphome/esphome:2026.10.2 | 6052 | config -> /config |
ESPHome environment variables
| Variable | Service | Value |
|---|---|---|
| PASSWORD | esphome | Generated at deploy |
| TZ | esphome | Preset by the template |
| USERNAME | esphome | Preset by the template |
Ports and volumes
- Ports
- 6052
- Volumes
- 1 named mount: config -> /config
ESPHome FAQ
How much memory does ESPHome need?
The catalog lists about 512 MiB of memory for ESPHome.
Does ESPHome run on arm64?
For ESPHome, arm64 support is not confirmed; amd64 is unknown.
What licence is ESPHome under?
ESPHome is licensed under GPL-3.0-only, which is copyleft, so changes you distribute must be shared under the same terms.
Does ESPHome need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which ports does ESPHome use?
ESPHome listens on port 6052 inside the stack.
Where does ESPHome keep its data?
In a named volume: config mounted at /config.
Can I deploy ESPHome on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for ESPHome, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image esphome/esphome:2026.10.2 is what you deploy there.