Local real-time coordination
Keep the site meter near target while batteries, PV and charging respond as one system.
00 · FTW Community
The open-source brain for your solar, battery and EV.
FTW coordinates solar, batteries, grid and EV charging locally, in real time. One open-source home energy runtime, with no cloud dependency in the control path.
Local-first controlFast decisions stay on your Raspberry Pi or Linux host.
Hardware-neutralCoordinate devices from different vendors as one energy system.
Open by designApache-2.0 code, Lua drivers, public roadmap and community contributions.
Apache-2.0 · Community support onlyDirectory · 00 of 07
01 · One home, one system
Your energy devices should work together.
Solar inverters, batteries, grid meters and EV chargers usually arrive with separate apps, separate clouds and separate ideas about what your home needs. FTW treats the site boundary as the system and coordinates the devices behind it every few seconds.
The usual home energy stack
- One app and cloud dependency per vendor
- Battery, solar and EV charging optimize in isolation
- Schedules stand in for real planning
- Your data and control path leave the home
With FTW
- One local control loop coordinates the whole site
- PV, load, storage and charging are planned together
- Prices, forecasts and physical limits inform every plan
- Cloud services are optional, never the core control path
02 · Built for real homes
Control, planning and hardware integration in one project.
FTW is more than a dashboard. It combines an edge control loop, mathematical planning, self-learning models and hot-editable hardware drivers, with safe fallbacks when inputs disappear.
Price-aware planning
Plan across spot prices, weather, PV, household load and battery state, with a safe local fallback.
Self-learning energy models
Local PV, load, price and battery models adapt to the home instead of assuming every site behaves alike.
Lua device drivers
Modbus, MQTT, HTTP, WebSocket and raw TCP integrations can be improved without rebuilding the runtime.
Safety-first fallbacks
Watchdogs, stale-meter protection, fuse limits and explicit clamps return devices to autonomous modes when needed.
Your data, locally
SQLite history, long-format telemetry and Parquet rolloff keep high-resolution energy data under operator control.
Home Assistant
MQTT autodiscovery brings sensors and controls into Home Assistant, with an add-on path for HA OS users.
Calendar-aware energy
CalDAV turns ordinary calendar events into departure deadlines, away modes and charging windows.
Public APIs and drivers
Build new integrations, add hardware support and improve the planner through the same public repository.
03 · Choose the objective
One control system. Different ways to run your home.
The physical limits stay the same. The planner objective changes with the outcome you want.
Self-consumption
Use the battery to cover household load and absorb your own PV without intentionally importing to charge.
Passive arbitrage
Decide whether PV surplus is worth more exported now or stored for a more valuable hour later.
Active arbitrage
Import, hold or export around price opportunities while respecting fuse, power and state-of-charge limits.
04 · Community edition
Built in public. Maintained with the people who run it.
FTW Community is complete, self-hosted software under Apache-2.0. Run it, study it, adapt it and send improvements back. Sourceful stewards the project; the community helps decide where it gets better next.
No official support or SLA
The Community edition is provided as-is. Maintainers and other users may help on a best-effort basis, but response times and fixes are not guaranteed.
- Ask setup questions in Discord
- Report reproducible bugs on GitHub
- Never post secrets or private energy data
Your hardware can improve FTW
Drivers are small Lua files, documentation lives beside the code, and project decisions are recorded in public. The fastest way to make your device work better is often to improve the shared driver.
- Add or test a device driver
- Improve safety, planning or documentation
- Open an issue before a large change
05 · For organizations
Community software. Commercial accountability when you need it.
FTW Community is open source for home and commercial use. Organizations that need an accountable delivery partner can work with Sourceful on a separately scoped, supported deployment.
Apache-2.0 already permits commercial use of the Community code. A Sourceful engagement buys additional capabilities, delivery ownership and support, not permission to use open source.
Supported rolloutArchitecture, installation, commissioning, upgrades and operational handover.
Integrations and OEM deliveryCustom hardware support, certification, white-label and product integration.
Fleet and managed operationsMulti-site visibility, provisioning, monitoring and managed service boundaries.
Long-term supportDefined maintenance, response times, security handling and contractual service levels.
06 · Get started
From blank SD card to a local energy runtime.
Choose the path that fits your home. Each route leads to the same local setup experience and dashboard.
# Docker installer on Raspberry Pi OS, Debian or Ubuntu $ curl -fsSL https://raw.githubusercontent.com/srcfl/ftw/master/scripts/install.sh | bash # Then open the local setup wizard $ open http://<your-pi>:8080/setup # Build with simulators $ git clone https://github.com/srcfl/ftw $ cd ftw && make dev
07 · Stewardship
Born in real homes. Maintained as part of Sourceful Energy.
FTW grew out of the practical problem of making devices from different energy vendors behave like one system. The project brings that experience into an open, local-first runtime that homeowners and contributors can inspect and improve.
Sourceful Energy maintains the project direction, releases and core architecture together with project contributors.