01
OCPP support varies by manufacturer
The standard is interpreted differently by each vendor and firmware version, so compatibility is empirical rather than assumed.
ThinkDebug
Practical deep dives on software architecture, AI systems, and scaling digital products - drawn from the work we ship.
Charging networks, roaming and driver apps across mixed hardware.
We build charging and e-mobility software: charge point management, driver apps and roaming, tariffs and billing, and the integrations with hardware, energy suppliers and roaming hubs that make a network usable.
EV charging is a hardware reliability problem expressed in software. Chargers are outdoors, unattended and made by many manufacturers with uneven OCPP support, and a driver who arrives at a broken or unavailable unit does not distinguish between the hardware, the network and the app.
Roaming makes it harder again. A driver expects to charge on any network with one account, which means authorisation, pricing and settlement have to work across operators through hubs, with the resulting reconciliation problem arriving monthly.
The constraints that shape every build in this sector, and the ones teams usually meet too late.
The standard is interpreted differently by each vendor and firmware version, so compatibility is empirical rather than assumed.
Connectivity drops, hardware faults, and the driver blames the app for all of it.
Sessions authorised on another operator's network have to price and settle correctly, weeks later.
A driver standing at a charger will give up in seconds, and a failed start is the single worst experience on the network.
A map showing a charger as free when it is broken destroys trust faster than having fewer chargers.
Tariffs vary by time, site and supply contract, and the price quoted has to match the price charged.
Swipe to read all 6
Each one is a system we have built before, not a capability we are willing to try.
OCPP-based management across mixed hardware, with firmware and diagnostics.
Finding, authorising and starting a charge, with availability that is honest.
Pricing, session billing and OCPI roaming settlement that reconciles.
Fault detection and remote recovery before drivers report the problem.
Smart charging, scheduling and load management for depots.
Site capacity, load balancing and grid-aware charging.
Engagements across sectors - the same team, the same standards.
Partnering with Thinkdebug to develop the Forever 52 mobile app has been a game-changer for us. They were always open to feedback, and it was clear they were as invested in our success as we were. What really sets them apart, though, is the amazing support we've received since the app launched. They’ve made sure the app continues to run smoothly and are always ready to fix any issues that come up.DMDhruv MehtaBusiness Head, Forever 52
Chosen for fit and long-term maintainability, never for novelty.
Send us the scope and we come back with an itemised estimate - no discovery fee, no obligation.
What we design and document against, from the first commit rather than the week before an audit.
Certification itself belongs to your entity and its assessor. What we provide is software built and documented so the assessment is about evidence rather than remediation.
Most of our work comes from clients we already shipped for. These are the reasons they give.
We test against the actual chargers and firmware you deploy, because the standard is interpreted differently by every manufacturer.
Health is inferred from real session and heartbeat data, since a map that lies about a free charger loses drivers permanently.
The start-of-charge path is the most important flow on the network and is treated as such.
Sessions, tariffs and CDRs are recorded so a monthly settlement with another operator is verifiable rather than accepted on trust.
Fault detection and remote reset resolve many issues before a driver ever arrives at the unit.
Tariff evaluation is server-side and versioned, which is both a trust and a regulatory requirement.
Let's start with you.
Your information stays private. We reply within 24 hours.
Still have a question we have not answered?
Ask an engineerWhat we build for emobility & ev, the work we have shipped, and what we have written about it.
