One Platform.
Every Charging Context.
v.energy is a context-aware CSMS for hotels, CPOs, and fleets. Authorization, energy, pricing, billing, and roaming — evaluated together for every session.
Built For Your Operation.
Same platform. Tailored context. Hotels post to room folios. CPOs maximize solar margin. Fleets guarantee departure readiness.
Room 412 · Suite Deluxe
NFC key · PMS folio posted
Hotels
arrow_forwardGuests plug in, tap their room key, and the charge posts automatically to their PMS folio. No separate app. No card friction.
CPOs & Solar
arrow_forwardSolar surplus charges first. Grid fills the gap. Roaming drivers bring revenue. CPO-controlled pricing with eRoaming settlement — all in one platform.
Fleet & Depot
arrow_forwardProtect vehicle readiness by departure time. Optimize depot energy cost. Cost-per-vehicle reporting ready for accounting or ERP export.
One platform for the full charging chain.
A reliable charging experience depends on more than a live charger. v.energy connects charger behavior, protocol handshakes, business workflows, and recovery evidence in one operating layer.
Charger Behavior
Firmware, metering, resets, connector state, and vehicle interaction are treated as operating facts, not support afterthoughts.
Protocol Handshakes
OCPP, OCPI, and ISO 15118 are operational contracts with traceable events, not just acronyms on a spec sheet.
Business Workflow
Charging is connected to folios, tariffs, fleet readiness, roaming settlement, energy plans, and reporting.
Recovery Evidence
Every failed or successful session leaves an event trail that helps operators resolve issues instead of guessing.
The EV charging stack is fragmented. The driver feels every gap.
Legacy charging software grew around isolated pieces: charger status, payment, roaming, tariffs, billing, support. That fragmentation becomes visible when software, hardware, firmware, vehicle behavior, and business workflow do not handshake cleanly.
The fragmentation tax
A poorly matched charger, firmware build, backend, token flow, tariff engine, roaming route, and billing workflow can technically be "integrated" and still fail in the real world.
The v.energy view
We treat charging as one end-to-end operating system, not a pile of parts forced to cooperate after procurement. Research, charger behavior, protocol implementation, certification-informed requirements, diagnostics, and business workflow belong in the same architecture.
Software
Session logic, recovery, tariffs, roaming, billing evidence, and operator workflows.
Hardware behavior
Charger state, firmware quirks, vehicle interaction, metering, resets, and edge cases.
Protocol handshakes
OCPP, OCPI, ISO 15118, authorization, CDRs, and event traces that can be audited.
Certification mindset
Testability, traceability, interoperability, and requirements discipline from the start.
| Strategic question | v.energy | Legacy CSMS |
|---|---|---|
| What is the source of truth? | The full session outcome across charger, vehicle, authorization, energy, metering, pricing, billing, and recovery. | Charge point status, backend events, and reports from separate systems. |
| How are hardware and software matched? | Validated as one operating flow, with expected charger behavior, firmware realities, and handshake requirements understood before scale. | Connected after the fact through integrations, adapters, and vendor-specific assumptions. |
| What do protocols mean? | Operational contracts. OCPP, OCPI, and ISO 15118 are treated as evidence trails and handshake rules, not just message transport. | A connectivity checkbox. The protocol may be supported, but interpretation and diagnostics vary by vendor. |
| Who owns failure? | The platform identifies where the chain broke and gives the operator a recovery path before the customer experience collapses. | Failures fall between charger vendor, backend, payment provider, roaming hub, installer, and support desk. |
| How does certification influence the product? | Certification-informed research shapes architecture, testing, traceability, interoperability, and deployment readiness. | Compliance is often handled as a late-stage requirement or documentation layer. |
| What does the user experience become? | Charging feels like a reliable product: start the session, receive energy, see the right price, and trust the operator. | The user becomes the integration test for a stack of parts that were never designed as one experience. |
The strategic difference
Poor handshaking does not look technical to a driver. It looks like your charger does not work.
Start with your site.
Hotels, charge point operators, fleets — we tailor every deployment to your operation.