When an organisation evaluates EV charging infrastructure, attention almost always lands on the hardware: power output, manufacturer, cost per point. That's understandable — hardware is the visible part.
But hardware doesn't manage infrastructure. The system behind it does.
And that's precisely where most organisations make a consequential decision by default — without understanding the constraints they're accepting.
The problem with lock-in
Most charging stations come with a manufacturer portal or application. At first, it looks sufficient: you can see the stations, monitor the sessions. It works.
Six months later, the fleet grows. A new site is added. Some equipment is replaced. And it becomes clear that the manufacturer's portal manages only its own hardware — not the infrastructure as a whole.
It doesn't account for the building's total energy consumption. It doesn't manage fleet priorities. It doesn't connect depot charging, workplace charging, and home charging in a single view. It doesn't allow costs to be tracked by department, team, or location.
The result: a different interface for every hardware brand, manual reporting, no unified visibility — and dependency on the product roadmap of a specific manufacturer.
This is vendor lock-in. It rarely surfaces at the point of purchase. It surfaces at the next expansion.
What vendor neutrality means in practice
A vendor neutral system doesn't mean all charging stations are equally suitable. It means the choice of hardware is made based on technical and commercial requirements — not on the constraints of the management software.
Integration without disruption. When you add equipment from a new manufacturer, the system absorbs it without reconfiguration. Existing rules, access policies, and session history remain intact.
Independence from market dynamics. Charging hardware manufacturers exit markets, merge, and discontinue support for older models. A vendor neutral system depends on none of them.
Real cost control. When you're not tied to a specific supplier, you choose hardware based on current market conditions — not on what's available in your software partner's portfolio.
Scaling without architectural change. New site, new vehicle type, new service — everything is added to the existing system, not a new one.
How Qerra OS addresses this
Qerra OS communicates with every charging station via the OCPP 1.6 standard — regardless of manufacturer. The choice of hardware remains with the client and is made according to site-specific requirements, budget, and long-term objectives.
The platform is not tied to any specific brand and does not evolve according to a hardware manufacturer's product roadmap. It evolves according to the needs of the infrastructure.
Qerra OS consolidates into one interface: the site's charging infrastructure regardless of hardware brand, energy management and dynamic power distribution within contracted grid capacity, fleet operations — priorities, schedules, vehicle readiness, employee home charging and public charging networks, plus access control, reporting, and cost allocation by department, location, and cost centre.
Configuration, access policies, and session history remain under the client's control. When hardware is replaced or expanded — they remain intact.
Why this matters at scale
Organisations rarely build charging infrastructure for a single site, a single vehicle, a single moment. Infrastructure grows with the fleet.
If the system behind it is tied to a specific manufacturer, every expansion involves a compromise: either follow the constraints of the current platform, or start over.
Vendor neutral architecture doesn't solve future problems — it prevents them. The organisation retains the flexibility to choose the most suitable hardware for every next step, without paying a transition cost each time.
Conclusion
Charging infrastructure is not a one-time purchase. It is an operational asset that must perform reliably as the business grows.
Reliable infrastructure is not managed by the hardware. It is managed by the system behind it.
Choosing a vendor neutral platform is not a technical detail. It determines whether the infrastructure grows with the business — or whether it has to be rebuilt with every expansion.
Qerra OS is the operational platform behind every Qerra service. Built on open standards, it manages charging infrastructure, energy, and fleet operations — independent of hardware manufacturer.