Analytics cookies only (Google Analytics, PostHog). No ad networks, no cross-site tracking. See our privacy policy.
Self-host evcc
updated Nov 2026deployed by usprices checked · Jul 2026Install verified on Ubuntu 26.04 · Nov 2026 · how we test
We earn commissions when you shop through the links below. Full disclosure →
An EV charge controller and home energy management system written in Go. It talks to wallboxes and chargers, solar inverters, batteries, grid meters and vehicle APIs, and starts or throttles charging to match solar surplus, a dynamic tariff or a plan you set. The web interface on port 7070 asks for an administrator password on first use, then configures devices, and shows live power flows and charging sessions. Settings and sessions are stored in an SQLite database in a directory you mount. REST and MQTT APIs let other home automation systems read it. It runs locally without a cloud account, but many commercial chargers need a paid sponsor token.
Pick evcc when you own an electric car and a wallbox and want charging driven by solar surplus, a dynamic tariff or a departure plan, on a server in your own home with no vendor cloud. It speaks to a long list of chargers, inverters, batteries, grid meters and vehicle APIs, exposes REST and MQTT for other home automation systems, and keeps its settings and charging sessions in one SQLite database. It is MIT-licensed Go with a Vue web interface, and ships as one image. Our snippet adapts the docs' Docker Compose example, pins `evcc/evcc:0.319.0` (pushed to Docker Hub 2026-11-08, amd64 and arm64) instead of `latest`, uses host networking as the docs recommend, and keeps the database in a named volume. The docs state no minimum RAM, so our floor of 256 MB is a modest figure, not a documented one. It is a charge controller rather than a general home automation hub; Home Assistant and openHAB sit above it and can read its API, while evcc alone decides when the car charges.
What you need
Any VPS with at least 256 MB of RAM
A domain you control — most self-hosted setups need HTTPS in front of them
Paid link — we earn a commission if you shop through it.
Install
Run these commands on your server:
# evcc — EV charging controller — adapted from the docs' Docker Compose example, pinned to 0.319.0 (the docs use latest), host networking as the docs recommend, database in a named volumecat > docker-compose.yml <<'EOF'services: evcc: image: evcc/evcc:0.319.0 network_mode: host restart: unless-stopped volumes: - evcc-data:/root/.evccvolumes: evcc-data:EOFdocker compose up -dtimeout 180 bash -c 'until curl -fsSL -o /dev/null http://localhost:7070/; do sleep 3; done'# → http://SERVER_IP:7070 — the evcc web interface asks you to set an administrator password on first visit, then walks through adding chargers, meters and vehicles; with no hardware it still starts and shows the setup page
evcc's README, docs and Dockerfile flag these before you rely on it:
non-negotiableSome devices need a paid sponsor token. The README excludes sponsor-required components from the MIT licence; the sponsorship page says many commercial chargers require a token, while open-hardware chargers, switch sockets and plugins do not, and that one token covers up to three instances in the same home. Prices listed there are $4 a month or $150 once via GitHub Sponsors, or EUR 50 a year or EUR 150 once direct, and a time-limited trial token exists. Check your charger against the device list before buying hardware.
non-negotiableThe first visitor to the web interface sets the administrator password. The docs say you are prompted for one on first use, so until you open the page the instance is unprotected; do that before exposing port 7070, and put TLS in front of it.
non-negotiableNothing runs until a device exists. The configuration docs say at least one meter or charging point must be configured for the system to run, and the snippet stops at the setup page; the interface starts, but no charging is controlled.
non-negotiableThe snippet uses host networking, which the docs recommend and which needs a Linux host. In bridge mode the device search does not see your network, mDNS features (EEBUS, SMA Sunny Home Manager, app discovery) and UDP devices such as KEBA chargers need extra port publishing, and you enter device addresses by hand.
non-negotiableMount the /root/.evcc directory, never a single database file. evcc keeps evcc.db with its -wal and -shm files there, and the docs advise a named volume and warn against NFS/SMB shares or Docker Desktop bind mounts because SQLite locking can break. If sessions vanish after an update, the directory is not mounted correctly.
non-negotiableThe image sets TZ=Europe/Berlin in its Dockerfile. If your tariff windows and charging plans are in another zone, set TZ on the service before you create plans.