About ChargeControl
An operating system for EV charging and energy operations.
ChargeControl exists to bring home, public, workplace, and depot charging together with energy management, settlement, and reporting in one place.
What ChargeControl is
ChargeControl is an operating system for EV charging and energy operations rather than a single point tool for one domain.
An operating system, not a point tool
ChargeControl brings charging, energy, and settlement functions together instead of leaving them in separate single-purpose products.
One platform across domains
Home, public, workplace, and depot charging run on the same governed dataset instead of separate, disconnected systems.
Built on open protocols
Support for OCPP, OCPI, ISO 15118 Plug & Charge, Modbus, and EEBus keeps the platform compatible with mixed hardware and networks.
Operational and financial together
Charging operations, energy management, reimbursement, and reporting connect instead of living in separate tools.
How ChargeControl approaches the category
A small set of principles shape how the platform is built and extended.
Data-first approach
Every capability builds on one normalized dataset so charging, energy, and financial views stay consistent.
Openness by default
Interoperable protocols and open APIs keep ChargeControl compatible with the hardware and systems already in place.
Governance built in
Roles, policy, and audit trails are part of the platform rather than added on afterward.
Room to extend
REST, GraphQL, APIs, and webhooks let teams connect ChargeControl to CRM, ERP, billing, and other systems.
An operating system for EV charging and energy operations
ChargeControl exists to treat EV charging and energy operations as one connected system rather than a set of disconnected point tools. Home, public, workplace, and depot charging share the same governed dataset, so policy, cost, and energy decisions do not have to be reconciled after the fact from separate exports.
That category position rests on openness and extensibility. Protocols such as OCPP, OCPI, ISO 15118 Plug & Charge, Modbus, and EEBus keep hardware choices open, while REST, GraphQL, APIs, and webhooks connect the platform to the CRM, ERP, and billing systems teams already run.
Governance is built into that same foundation: roles, policy, and audit trails apply consistently as more sites, drivers, and integrations join, rather than being layered on as an afterthought.