EV Charger Controller OEM
If you want to build chargers in your own shape and size, the control card is the part you should not be designing from scratch. We supply ours as a component, with everything on a single board, so a panel builder or an installer can put their own product around it instead of spending two years discovering the problems we already solved.
This is for companies that want their own charger: their own enclosure, their own form factor, their own branding, without taking on the electronics and firmware behind it. We supply the controller; you design the product around it.
Discuss controller integrationFor Charger manufacturer
What the controller covers
Swipe to compare
| Function | Scope |
|---|---|
| Control pilot and proximity | IEC 61851-1 control pilot and proximity interface |
| Supported ratings | Single phase 3.3 and 7.4 kW, three phase 11 and 22 kW. Others custom |
| Contactor control | Relay-driven output with feedback monitoring on contactor state |
| Meter interface | Modbus RTU energy meter shipping. Other protocols custom |
| Connectivity | Wi-Fi, BLE and 4G shipping. Ethernet configurable. Others custom |
| Protocol | OCPP 1.6J and 2.0.1 released and maintained. 2.1 in development |
| Update | OTA shipping with rollback. Staged rollout via CMS configurable |
| Provisioning | Factory flashing from a controlled release package, per-device credentials at end of line |
Why a maintained stack matters
OCPP is a moving target. Versions evolve, backends implement them differently, and security expectations tighten. A controller with a maintained stack absorbs that. A controller with a firmware snapshot becomes your maintenance problem the day you ship.
Ask any controller supplier what their firmware update and security response process is. The answer separates a component supplier from a partner.
Certification implications
The controller carries functions that sit inside the certified behaviour of your product. Changes to it can have certification consequences for you, which is why version control and change notification run both ways.
How we work with you on this
A controller is the component your whole product depends on, which makes supplier lock-in a real risk and one you should raise with us directly rather than discover later.
Our engineers work with yours through the integration, and the firmware handover model is agreed at the start rather than at the point you need it. Both source and signed-binary models are available. Which one applies is a commercial decision made openly, because a customer who finds out at handover that they cannot maintain their own product has been badly served.
Eight to ten years of field behaviour, already in the board
The difference between a first charger design and a mature one is not the schematic. It is the accumulated list of things that only appear in the field.
We have been designing chargers for eight to ten years, and the practical cases are built into the controller: vehicles that negotiate badly, supplies that sag and recover, sessions interrupted in ways no specification anticipated, the sequence a unit has to follow when a driver unplugs at the wrong moment. Those are not in any standard. They are in returns, and they are why our chargers are stable.
A company designing its first charger meets all of them over about two years. Starting from our controller means most of them are already handled.
Who this is for
- Panel manufacturers building charging into their own product range
- Installers and solar companies who want a charger of their own rather than reselling another brand's
- Equipment makers adding charging to an existing line
- Anyone whose product needs a shape, size or integration that no standard charger provides
The common thread is that the enclosure and the market are yours and the electronics are not where you want to spend your engineering.
Commercial terms
- Minimum order quantity is 100 units
- A one-time training fee covers integration support, so your engineers are not working it out alone
- Technical support through the integration period
The training is not optional in practice. A controller integrated without it usually works and usually has something wrong in the areas that only show up later, which is exactly what buying a mature controller was supposed to avoid.
Want this applied to your own site?
Discuss controller integrationTechnically reviewed by Anees P K, Director of Technology. Last reviewed 2026-08-29.
Frequently asked questions
Can we use your controller in our own charger design?
Yes, under an integration programme covering the controller, its firmware and integration support. Enclosure, power path, protection selection and product positioning remain yours.
Which OCPP versions does the controller support?
OCPP 1.6J and 2.0.1 are released and maintained, with 2.1 in development.
Do you provide firmware updates?
Yes. A maintained stack is the main reason to buy a controller rather than build one, since OCPP and security expectations keep moving.
Will it work with our CMS?
Interoperability is verified by integration testing against your specific backend. Version compliance alone does not guarantee it, because backends implement the protocol differently.
Does using your controller affect our certification?
It can, because the controller performs functions inside your product's certified behaviour. Change notification runs in both directions for that reason.
Can we get the firmware source?
Source is not included by default. It is available under licence or a technology transfer agreement, which is a separate commercial route.
Discuss controller integration
Tell us about your charger design and target backend and we will map the integration boundary and what verification it needs.
Discuss controller integration