Self-host evcc with Levelrail
A smart charging controller that charges your electric car from solar surplus and cheap tariffs.
- Authorevcc-io
- LicenceMIT
- Memory128 MiB
- Services1
How to self-host evcc
-
Pull the images
One image is pulled on your server.
Show images
evcc/evcc:0.319.0
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on port 7070.
-
Fill in the secrets
1 setting is 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
- Open the address and finish the setup wizard to add your charger, meter and vehicle.
evcc requirements
- Memory
- About 128 MiB
- Architectures
- amd64 unknown, arm64 unknown
- Ports
- 7070
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- MIT, permissive 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 evcc. 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 evcc docs page.
Deploy evcc your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy evcc from the CLI
levelrail-cli templates install evcc --name my-evcc Deploy evcc with the API
curl -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
https://levelrail.example.com/api/v1/service-templates/evcc/install \
-d '{
"name": "my-evcc"
}' evcc configuration
evcc services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| evcc | evcc/evcc:0.319.0 | 7070 | data -> /root/.evcc |
evcc environment variables
| Variable | Service | Value |
|---|---|---|
| TZ | evcc | Preset by the template |
Ports and volumes
- Ports
- 7070
- Volumes
- 1 named mount: data -> /root/.evcc
evcc FAQ
How much memory does evcc need?
The catalog lists about 128 MiB of memory for evcc.
Does evcc run on arm64?
For evcc, arm64 support is not confirmed; amd64 is unknown.
What licence is evcc under?
evcc is licensed under MIT, which is permissive, with few conditions on reuse.
Does evcc need configuration before it starts?
No. The template fills in its own defaults.
Which ports does evcc use?
evcc listens on port 7070 inside the stack.
Where does evcc keep its data?
In a named volume: data mounted at /root/.evcc.
Can I deploy evcc 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 evcc, 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 evcc/evcc:0.319.0 is what you deploy there.