Monitoring Enphase and SolarEdge fleets in one dashboard: what multi-brand actually requires

Almost no installer ends up with a single-brand fleet. Supply changes, a customer specifies something, a product line gets discontinued, you acquire another company's install base. Five years in, most companies run several manufacturers' hardware and several manufacturers' portals. One browser tab each.

That is tolerable at twenty systems and impossible at four hundred. The failure is not that any individual portal is bad. The first-party tools are good at what they were built for. It is that no one opens six portals every week. Coverage collapses to whichever systems someone checked, which in practice means whichever customer called.

Reading a fleet across brands means integrating with each manufacturer's cloud platform separately. Every one has its own authentication, its own data model, its own rate limits, its own idea of what a reading contains and how often it publishes. There is no shared standard to lean on. An adapter is real engineering per brand, and it needs maintenance, because these platforms change without consulting anyone.

This is worth understanding as a buyer, because it explains why brand coverage claims deserve more scepticism than they usually get. A logo wall costs nothing to produce. A working adapter is ongoing work, and an integration that broke six months ago looks exactly like one that works right up until you try to read a system with it.

Ask the specific question rather than the general one: not "do you support this brand" but "how many systems on this brand are you reading in production today, and when did that adapter last return data". A vendor who cannot answer that quickly has told you the answer.

We currently read nine brands in production and say so precisely, because we have removed brands from our own compatibility list when their adapters stopped being productive. Enphase and SolarEdge — the two that dominate US residential — are in integration with our founding partner cohort and are not counted among the nine. Listing them as supported before they are would be the exact failure described above.

The second half of multi-brand monitoring is harder than the integration and gets discussed less. Once the data is in one place it has to be made comparable. Manufacturers report different quantities at different intervals with different definitions, and a fleet view that simply stacks their numbers side by side produces a dashboard that cannot be reasoned about. What matters is a normalised measure of whether each system is performing as it should — expected output given the weather at its location, compared against what arrived — because that is the only comparison that works identically across every brand.

Get that right and the fleet becomes rankable. Not four hundred systems to check. The six that are underperforming, ordered by how much they are losing. That is what multi-brand monitoring is for. One tab is the means.