Products

Put every kWh where it is worth most.

Optimize self-consumption on both on-site systems and virtual net-billing systems, by managing the battery.

Net-billing, net-metering or zero-feed-in: it makes no difference to us.

The engineering question is identical for all of them, and Optimize answers it the same way. The legislation will most likely keep changing too, and the product is built to grow with it — software updates carry any new rules and the features they bring.

What the controller decides

Optimize reads site load, PV output, battery state and, where they exist, flexible energy prices. Then it decides whether production goes to the load, into the battery, or onto the grid. Put simply: it gets the most value out of your system by controlling your hardware.

Export caps go straight into the inverters
One resolved limit is written to every inverter on site in a single operation
Plans against a day-ahead PV forecast, derived from an hourly radiation forecast for the site
Plans around flexible electricity prices for the best financial result
Battery operation with virtual net-billing systems
Settlement-period reporting and owner summaries on GPweb-Server
Choose the optimization logic you want

Why there is no savings figure on this page

We are not going to invent one. The legislation is still in flux, and every customer's consumption and requirements are different. We would rather tell you precisely what the equipment does for you, after looking at your own tariff and your own load profile. Anything else would not be serious.

Common questions

Which scheme am I under — net-metering, net-billing or zero-feed-in?

We support all of them, and the controller does not care which. The optimization problem — match production against consumption across the settlement period — is the same one under either scheme. The "virtual" net-billing and net-metering systems are technically different (they actually require a controller on each side), but the goal stays the same.

Do I need a battery?

Self-consumption improves without one: the controller can still steer load and cap export. But a battery is the only instrument that moves energy across time. Production peaks at midday and consumption usually does not; without storage the gap between those two curves is simply lost. We still need to look at your individual situation, but in most cases a battery is what makes the gains significant.

Will it work with the battery and inverters I am specifying?

Whatever is in your system: if we do not already have a driver for your hardware and it speaks a documented protocol, we write the driver for it — at no charge. So far, we have not met one we could not do.

Can I add this to a plant we already built for DEDDIE remote control?

Yes. Where a plant already runs GPweb-Remote, the controller is already there and Optimize runs on the same box. One engine, one arbitration order, no protocol converter and no second vendor between the compliance layer and the optimizer.

What runs where?

All devices carry it, sized to the system. GPweb-Monitor is the low-cost end of the range and fits a home or small commercial installation. GPweb-Remote is the controller for larger sites, and it is the one already running DEDDIE remote control — so on a plant that also has DEDDIE obligations, the optimizer and the compliance layer share one box, one engine and one arbitration order. Reporting and owner summaries surface on GPweb-Server either way.

Tell us the tariff, the load profile and the battery you have (or are planning). We will tell you what our systems can do for you.