KEMS
Public site GH

Kyle Energy Management System

Know what your home could do before KEMS ever takes control.

KEMS works with Home Assistant to observe real household demand, learn how the property behaves, replay the best strategy for the installed system and tariff, compare the actual energy bill with KEMS, and prove proposed control decisions in a digital twin first.

What KEMS compares

One measured baseline. One adaptive KEMS.

The user-facing comparison is deliberately simple: Live Data is what actually happened; KEMS is what the same property could have done with its configured hardware and tariff.

Adaptive strategy

KEMS changes its behaviour, not its identity.

The internal replay engine is selected automatically from the export arrangement and installed system. These are strategies inside KEMS, not separate products.

A

Self-use / no paid export

Prioritise the home, battery and solar when exported energy has no useful sale value.

No-export strategy
B

Fixed export optimisation

Value exported energy at the configured fixed export tariff while protecting household demand and battery reserves.

Fixed-rate strategy
C

Agile export optimisation

Use the rolling half-hour export-price horizon to choose when stored and solar energy is worth exporting.

Dynamic-rate strategy

Actual bill basis

Compare the number that matters on the energy account.

The headline Total energy cost includes electricity import, electricity standing charge, gas usage, gas standing charge, export income and genuine supplier/account energy credits. Battery wear is kept out of the household-bill total.

Electricity usageBoth standing chargesGas usageExport and supplier credits

Simulate and prove

Test KEMS against exactly the same property.

KEMS replays the property against the same retained demand, tariff and hardware configuration. Missing evidence remains unavailable rather than being scaled or invented.

Common demand evidenceTariff-aware strategyDigital-twin proofOne canonical cost contract

Prove before control

KEMS is built around a deliberate safety boundary.

On kems.uk, Home Assistant remains private. Live property data and credentials stay with the property. The public website receives only deliberately sanitised delayed evidence, while authenticated property access is handled through Cloudflare Access and outbound tunnels.

PropertyHome Assistant + KEMS remain the source of truth.
Public demoSanitised totals and KEMS half-hour plan, at least seven days old.
Remote accessOnly properties your Cloudflare identity is authorised to open.
DEMOSee KEMS and Compare using delayed property evidence.Open demo → PROPERTY ACCESSUnderstand how Cloudflare sign in protects each KEMS property.How sign in works →