System map

How WhyWatt Turns a Home Energy Consumption into a 20-Year Cost Comparison

You describe a home and a plan. Your ZIP code looks up climate, tariffs, load profiles and sunshine from data built offline. The engine runs two copies of the home, do nothing and your journey, year by year, and compares what each one costs. Click any box for its breakout, or an appliance to see how it is modeled.

control flow (what runs when) data flow climate tariffs projection load profiles · solar ▮▮▮▯ level of detail
How to read the engine. Nothing is computed day by day. Each appliance reports 12 monthly numbers (kWh or therms). Only the home's total electric load is then spread over one representative 24-hour day per month, which is what time-of-use pricing, solar and batteries need.

Offline pipelines

Five data sources, built once

Climate (TMYx), solar (PVWatts), tariffs (URDB), rate projection (CEC) and load profiles (NREL). Each is harvested by a script, checksum-pinned, and looked up by ZIP at run time.

Appliances

Nine appliances, one question

How much energy each month? Four levels of detail, from fixed usage to climate physics to an hourly energy balance.

Engine

Two homes, one loop

How do nothing and your journey are stepped year by year, and how the hourly energy balance prices solar and batteries.