Walk through any real portfolio of commercial solar and battery assets and you will not find one brand. You will find a Victron site that a previous contractor put in, a Sunsynk hybrid at the warehouse that went up two years later, a Fronius grid-tie array on the head office roof, and a Freedom Won pack at the site that needed more backup. Each came with its own app, its own login, its own way of presenting the same handful of numbers. The result is that nobody has a single accountable view of the portfolio. They have three apps per site and a spreadsheet trying to hold it all together.
This is the quiet tax on managing a mixed fleet, and it gets worse with every site you add. The honest position is that the brand on the box should not matter to whoever is responsible for the asset’s performance. What matters is the energy moving through it, the tariff it is dispatching against, and how hard the battery is being worked. Those questions are identical whether the inverter says Victron or Sungrow on the front.
Why fleets are mixed in the first place
Single-brand portfolios are an accident, not a plan. Assets are deployed at different times, by different contractors, under different supply conditions, against whatever was available and competitively priced that quarter. A site commissioned in 2023 sits next to one commissioned in 2025, and the hardware market moved in between. Procurement standardising on one make across an entire estate is the exception, and even then a single acquisition or a single distressed site brings a foreign brand into the fold.
So the mixed fleet is the normal case. Treating it as a problem to be solved by ripping out and standardising hardware is expensive and usually pointless. The hardware in the ground is mostly fine. What is missing is a layer above it that does not care which badge it is reading from.
Hardware-agnostic is an architecture choice, not a marketing line
It is easy to claim brand-neutrality. It is harder to build the oversight so that adding a brand is a data exercise rather than an engineering project. The distinction shows up in how device support is structured. In Soluno’s instrumentation, a device is resolved by a manufacturer identifier carried in the data stream itself, and support is driven by a catalog rather than written into the code one brand at a time. Bringing a new make into the fold means adding it to the catalog, not rebuilding the pipeline.
The brands that already sit in that catalog include Victron, Fronius, Sunsynk, Sungrow, GoodWe, Freedom Won and Tesla Powerwall. More important than the named list is the shape underneath it: the catalog models any manufacturer’s inverters across grid-tie, hybrid, battery and off-grid types, plus solar chargers, battery packs across lead-acid, lithium-ion and lithium iron phosphate chemistries, and fuel generators. A mixed fleet is overseen as one system, not as a pile of devices each demanding its own attention.
That is the difference between a portfolio view that happens to support several brands and one that is indifferent to brand by design. The first kind breaks the moment a site shows up with hardware nobody anticipated. The second simply absorbs it.
What being brand-indifferent lets you actually do
Once the badge stops mattering, the work that does matter becomes possible across the whole fleet at once. Three disciplines benefit most.
-
Dispatch tuned to the same tariff reality, everywhere. The Eskom tariff structure shifted under every asset in the country at the same moment. In the restructure NERSA approved on 18 February 2025, the morning peak was cut from three hours to two, the evening peak was extended from two hours to three, and off-peak rates were equalised across seasons. A battery whose charge and discharge windows were set against the old structure is now arbitraging into windows that no longer exist, and that is true whether it is a Victron or a Sunsynk. Re-tuning dispatch is the same job on both, and it only gets done if something can speak to both.
-
Battery health tracked against the make’s own warranty curve. State of health is not something most packs report directly. It has to be derived from how the battery has actually been cycled, using the depth of discharge it has seen against the cycle life it was rated for. Those rated curves differ by make: a Freedom Won pack and a Sunsynk high-voltage pack each carry their own documented cycle thresholds and a ten-year warranty horizon. Watching wear means watching each pack against its own curve, in the same view, rather than logging into a different app to read a different number.
-
One performance picture instead of per-site islands. A console that opens on a map and a table of every site, with each site locked to its own isolated data namespace, is what lets a portfolio owner answer “how is the fleet doing” without assembling it by hand from separate logins. The oversight runs fleet-wide on a schedule, re-solving dispatch across every site rather than at one site at a time.
Why the brand actually does still matter, in one specific way
There is a caveat worth stating plainly, because pretending otherwise would be dishonest. Brand-indifference applies to oversight, not to physics. The make genuinely matters when you are reading fault codes and reading degradation, because those are manufacturer-specific. A fault code on a Fronius means something different from the same number on a Sungrow, and the cycle life of one lithium iron phosphate pack is not the cycle life of another.
The point of a hardware-agnostic approach is not to flatten those differences. It is to hold them in one place so they can be interpreted correctly. Fault codes are resolved against a manufacturer-scoped catalog, so a raised code is read in the language of the make that raised it. Degradation is measured against per-chemistry curves, so a pack is judged against its own rated life and not a generic assumption. Being agnostic about the badge for the purpose of the portfolio view, while being precise about the badge for the purpose of diagnostics, is the whole trick.
The cost of staying single-app per site
Every brand-specific app does roughly the same thing: it shows you what happened. None of them re-tunes dispatch when the tariff structure changes underneath the asset. None of them reads one pack’s wear against its warranty and another pack’s wear against a different one, in the same place. And none of them gives a fleet owner a single accountable view, because each app only knows about its own brand.
The drift this allows is not dramatic. It does not trip an alarm. The tariff windows move, the battery quietly loses capacity at the order of one to four percent per year, the load at a site shifts as tenants and processes change, and three different apps each report that everything is fine because, on their own narrow terms, it is. The gap between the model each asset was financed on and the performance it actually delivers widens silently, multiplied across every site in the fleet. The economics make this concrete in one direction: with export credited below the retail import rate and capped per time-of-use period, the value sits in tuning self-consumption and peak-shaving at every site, which is exactly the work that fragmented per-brand apps cannot do.
The takeaway
A mixed fleet is not a problem to standardise away. It is the normal state of any real portfolio, and the hardware in the ground is usually fine. What is missing is a layer that is indifferent to the badge for the purpose of seeing the whole estate, and precise about the badge for the purpose of reading faults and degradation correctly.
If you are managing more than a handful of sites across different makes, the question is not which brand to standardise on. It is who holds the single accountable view, re-tunes dispatch as the tariff moves, and watches each pack against its own warranty curve, across every site at once, regardless of what the box says on the front. That is stewardship of a portfolio rather than a drawer full of logins, and it is the difference between a fleet that quietly drifts and one whose performance is actually owned.
Sources and further reading
Want to know what your solar asset could save?
How Much Do I Save?