EV Charging
A heartbeat is not uptime
We build the software behind a charging network — OCPP backend, driver app, roaming and settlement — with uptime measured by sessions that completed, not by chargers that answered a ping.
Talk to us about your projectWhere charging networks quietly lose money
The protocol is standard; the implementations are not. Two chargers both claiming OCPP 1.6J will disagree about StatusNotification, about what happens when the WebSocket drops mid-session, and about whether MeterValues arrive at all. A CSMS written against one vendor's firmware meets the second vendor and starts inventing sessions.
The other loss is quieter. A charger sending Heartbeat gets reported as available while its connector sits faulted, so the uptime number looks healthy and the reviews do not. Roaming CDRs come back disputed weeks later, by which point nobody can reconstruct what the driver was actually charged for.
Capabilities
What we build for charging operators
A CSMS, a driver app and a settlement layer are three products with three different failure modes, so we scope them separately even when they ship together.
CSMS and charger connectivity
An OCPP 1.6J and 2.0.1 backend built for real firmware: reconnect handling, offline session replay, and a local auth list for when the link drops.
Roaming and OCPI
OCPI 2.2.1 against a hub or a direct peer, with reconciliation showing which CDR a roaming partner disputed and which session it maps to.
Plug and Charge
Contract certificate handling through a V2G root PKI such as Hubject, plus the fallback path for a vehicle that presents no valid certificate.
Driver mobile apps
White-label iOS and Android with live connector status, reservation, the tariff shown before the plug goes in, and a receipt matching the CDR.
Tariffs and payment rails
Tariffs by kWh, by minute or with idle fees, and a card pre-authorisation hold released on StopTransaction rather than left sitting on the driver's statement.
Load management
Dynamic load balancing across a site using OCPP charging profiles, so a depot stays inside its grid connection instead of tripping the main breaker.
Uptime and fault detection
Uptime computed from connector StatusNotification and completed sessions, not Heartbeat, so a faulted EVSE is found by your team rather than by a driver.
AI for demand and driver support
Forecasting where queues form by site and by hour, and an agent that resolves failed-session refunds from the CDR without waking the ops team.
Blockchain where it earns its place
Smart-contract settlement per kWh between roaming partners, and on-chain REC or Guarantee of Origin attribution when a corporate buyer wants sourcing they can verify.
What you get
What you own at the end
Every engagement ends with things another team can pick up, including the parts a roaming partner or a site host will eventually ask to see.
- CSMS
- The backend and its source
- The OCPP server, database schema and deploy pipeline, running on your infrastructure or ours. Onboarding a new charger vendor becomes a config change and a test rather than a call with us.
- TEST BENCH
- A charger simulator and test suite
- Simulated EVSEs replaying the OCPP message flows your own fleet produces, including the dropped-socket and offline cases, so a firmware rollout can be tested before it reaches a live site.
- SETTLEMENT TRAIL
- CDRs you can defend
- Every session reconstructable from MeterValues through to the invoice line, with the roaming partner, tariff applied and dispute status attached. This is what a partner reconciliation call actually needs.
- OPERATING NOTES
- A runbook for the ops team
- What each fault code means on your specific hardware, which ones a remote reset clears, and which need a truck roll. Written for whoever picks up the phone at 6am.
How we work
From one site to a network
Timelines below are typical for a first network build. If your installed hardware cannot support what the roadmap assumes, we would rather find that in week two than in month five.
Scoping and fleet audit
1–2 weeksWe list your charger models, firmware versions and existing back office, then establish which OCPP features each one genuinely supports rather than claims on a datasheet.
Protocol proving
2–3 weeksWe drive real chargers from a test CSMS. This is where a hardware assumption usually dies, and occasionally the plan changes — cheaply, which is the point of doing it here.
Build
8–14 weeksCSMS, driver app, tariffs and payment rails, with OCPI roaming and load management added once single-site sessions complete reliably from plug-in to receipt.
Rollout and tune
OngoingSite by site, reading failed-session reasons and fault codes, tightening load limits, and cutting the refunds caused by sessions the hardware never really started.
Is this the right fit for you?
Worth reading before you get in touch — it saves both of us a call.
A good fit if…
- You operate chargers and are locked inside a hardware vendor's own cloud
- Several charger brands need to sit behind one backend
- Roaming CDRs or partner settlement are disputed and unreconciled
- A depot or fleet needs charging scheduled around a grid connection limit
Probably not, if…
- You need charger hardware or on-board firmware built — we do software only
- A driver app over someone else's CSMS — Mobile App Development fits better
- Only the payment rail needs work — see Custom Payment Gateway Integration
- A rewards token with no settlement problem beneath it — Custom Blockchain Solutions first
Frequently Asked
Questions
Common questions about EV charging platforms.
A charging station management system (CSMS) that talks OCPP to chargers, a driver-facing mobile app for discovery/reservation/payment, a backend for pricing and billing, roaming interoperability (OCPI), fleet-management tools, and an analytics layer for utilization and uptime reporting.
All the major ones. OCPP 1.6 and 2.0.1 for charger↔CSMS. OCPI 2.2 for roaming between networks. ISO 15118 for plug-and-charge and V2G. We build CSMS that speak these protocols natively, and integrate with existing chargers from ABB, Delta, Schneider, Exicom, and others.
Tamper-proof energy-consumption records (settling with grid operators and roaming partners), smart-contract micropayments (pay-per-kWh without intermediaries), peer-to-peer energy trading between home chargers and grid-tied batteries, and transparent renewable-energy attribution via on-chain RECs/I-RECs.
Yes. UPI (India), cards via Razorpay/Stripe, in-app wallets with auto-reload, RFID cards, and fleet-billing APIs. For tokenized/crypto payments we wire in stablecoin settlement layers. The payment layer is independent of the CSMS so it evolves without retooling the charging stack.
Both, and the CSMS in between. A typical engagement is a white-label driver app (find-and-charge, pricing, reservation, payment, ratings), an operator dashboard (station health, pricing rules, revenue reports), and the CSMS connecting to chargers and payment rails.
Have a project in mind?
Fixed price after a paid discovery — no hourly billing. A real engineer reads every enquiry, and we reply within 24 hours.