EV charging software development for charge point operators and mobility providers.
We build and extend charging management systems and driver apps for charge point operators and mobility providers.
Connect chargers, roaming and payments around your platform, or scope a custom product.
- 120+Projects delivered across 12 countries since 2012
- 100+Senior in-house engineers, six countries
- 5.0Unified rating across 61 client reviews on Clutch
- 2 to 4 weeksTypical time from signature to start
- ISTQBISTQB-certified QA engineers
- ISO 27001Certified security practice, audited by Quay Audit UK
01Overview
Scope the charging workflow to deliver first
We start with the workflow to deliver first and the platform, charger interfaces and session data it needs. We assess what an existing charge point management system (CPMS) covers, which data and APIs you can use, and where configuration, integration or a custom build provides the required behaviour.
- Run the estateStation state, firmware and configuration connected to the operator's daily workflow.
- OCPP 1.6 and 2.0.1
- Firmware and configuration
- Uptime, faults and alerts
- Sell the sessionDriver access, session state, payments and receipts through an account experience.
- Driver app and live map
- Authorization and start
- Payment and receipts
- Settle across networksTariffs and session records shared with partners and reconciled for settlement.
- OCPI and roaming hubs
- Charge detail records
- Tariffs and reconciliation
- Fit the gridCharging profiles assessed against site and grid-connection limits.
- Smart charging profiles
- Site and connection limits
- Demand response signals
02Compare
CPO, eMSP or both: pick the product before you pick the stack
A charge point operator (CPO) runs charging infrastructure; an e-mobility service provider (eMSP) offers drivers access and accounts. Your operating role, tariffs and partner requirements establish which product scope fits.
| Your charging operation | The product requirement | The route that fits |
|---|---|---|
| “We own the chargers and run them from the vendor’s portal.” | Manage station state and configuration across supported hardware | Assess the existing platform and its OCPP support. Configure or extend it where it fits; scope a custom management core for differentiated operating requirements.How we build custom systemsOr book a meeting |
| “We sell access to drivers and own no chargers at all.” | Connect availability, accounts, session state and payment | Choose a white-label app or build the driver experience over supported status and session interfaces, with payment and failed-session handling agreed for the product.Mobile app developmentOr book a meeting |
| “We have a dozen chargers and a spreadsheet.” | Cover standard operations with a maintainable product | A white-label CPMS can provide the core. Assess charger support, tariffs, roaming and data rights, then configure it or add a focused integration.Get a second opinion firstOr book a meeting |
| “We do both, and one team carries both roadmaps.” | Give operator and driver workflows clear ownership | Define separate product roadmaps and a shared session-data contract. Scope the OCPI boundary where the operator and mobility-provider roles exchange data.Platform development and integrationOr book a meeting |
| “It all works until a roaming session has to be billed.” | Reconcile charge detail records, tariffs and partner totals | A focused session-settlement integration, with partner data mapped to the billing workflow and reconciliation breaks raised for review.Data and integration engineeringOr book a meeting |
For a charge point operator, we build or extend the management system that keeps chargers online, configured and billing. For a mobility provider, we build payments, roaming and a driver app with live charger status. When you run both, we staff them as two products.
Andrii BurdaSenior Engineering Manager, unicrew03Platform
Charging systems and integrations we build
Scope the charging capabilities your operator or driver workflow needs, with hardware and partner interfaces assessed for each integration.
OCPP connections to supported chargers, firmware and configuration controls, authorization, transaction records, tariffs and a station-health view. Hardware and version coverage are agreed for your estate.
- Sits with
- The charge point operator
We assess OCPP 1.6 and 2.0.1 against charger firmware and the management system. The versions are not compatible; 2.0.1 adds device management, security, smart charging features and ISO 15118 support.
- Sits with
- The charge point operator
Live charger status, authorization, session start, payments and account access. Native or React Native applications use the platform's supported status and session interfaces.
- Sits with
- The mobility provider
Open Charge Point Interface (OCPI) connections between operators and mobility providers, bilateral or through hubs such as Hubject or Gireve. We assess versions and modules for status, tariffs, sessions and charge detail records (CDRs).
- Sits with
- Both, at the boundary
Session rating, invoicing, account billing and ad-hoc card payments connected to payment providers and your ERP. We scope the meter records and applicable billing requirements with your operating owner.
- Sits with
- Both, in different halves
Smart charging profiles, site and grid-connection limits, and schedules for lower-cost hours. We assess equipment and platform support for demand-response signals and OpenADR interfaces.
- Sits with
- The charge point operator
04Proof
Charging mobile work and adjacent engineering
- React Native work in EV chargingOur named React Native work includes LADE. Adjacent mobile engagements include Droniq and Triathlon Ireland; mobile app development covers our mobile engineering scope.LADEan EV charging client we can name
- Energy systems next doorWe built a CRM and B2B marketplace for a commodity trader. This is adjacent commercial-data work. ETRM and CTRM covers trading engineering; energy and utilities covers utility-data integration. Those scopes are distinct from charger management and driver products.CRMadjacent commodity-trading platform work
- Company management systems and QA credentialsOur information-security and quality-management systems are certified under ISO 27001:2022 and ISO 9001:2015, renewed through a multi-stage audit with Quay Audit UK. unicrew has ISTQB-certified QA engineers; project testing is scoped against the session, payment and integration work.ISO 27001with ISO 9001, audited by Quay Audit UK
05Questions
Questions about EV charging software
OCPP (Open Charge Point Protocol) connects charging stations with their management system, and the version matters for integration.
OCPP 1.6 and 2.0.1 are not compatible. Version 2.0.1 adds device management, security, smart charging features and ISO 15118 support. We assess the version, charger firmware and management-system implementation together before confirming the interface scope.
A white-label platform fits where its charger support, tariffs and data interfaces meet your operating requirements.
A custom build fits differentiated operator or driver workflows that need bespoke development. A platform with a custom app or integration is another route: retain the supported core and build the experience around it. We compare hardware coverage, roaming requirements, data rights and maintenance ownership before recommending the scope.
We assess supported hardware and partner interfaces before confirming the integration scope.
Send the inputs for the connections you need:
- Chargers: hardware, firmware and OCPP versions.
- Roaming: OCPI versions, modules and partners, including any Hubject or Gireve hub connection.
- Payments and ERP: provider interfaces, session records and data-access rights.
We agree test access and acceptance criteria with the platform owners. On build engagements, access is least-privilege and agreed with your technical contact, read-only wherever the work allows, with no production write access during discovery.
Most engagements start within two to four weeks of signature. Delivery duration depends on the agreed product and integration scope.
Discovery establishes hardware and protocol coverage, the priority workflow and the partner testing needed for acceptance. We estimate that work before agreeing a delivery plan, whether it is a focused OCPI integration, a driver app or a custom management system.
The delivery plan includes release acceptance with system owners, interface documentation and operating handover. We scope ongoing maintenance separately where required.
We quote EV charging software against the product scope and the hardware, roaming and payment interfaces involved.
- Time and materials: billed hourly, quoted per project.
- Fixed price: quoted per project against an agreed outcome.
- Team extension: billed monthly per team member, with no recruitment or placement fee.
We recommend the model after discovery. Fixed-scope work carries a post-launch warranty, with its length agreed in the contract.
Applicable rules depend on the deployment, payment model, funding and data processed.
- EU public charging: confirm AFIR payment and pricing duties against power and deployment date, including new points of 50 kW and above.
- Germany: establish applicable calibration law (Eichrecht) requirements for meter records and billing.
- US: confirm annual uptime and reporting conditions for NEVI-funded ports.
- Personal data: GDPR applies where driver, location, account or session records identify a person. Agree purpose, access and retention with the data owner.
Your legal and operating owners confirm the requirements used to scope the software.
Plan your operator or driver product
Discuss the charging workflow you want to own and the platform you want to retain. We assess the product boundary and interfaces before recommending configuration, integration or custom development.
What happens after you contact us
- We reply within one business dayTell us which operator or driver workflow you want to build or extend.
- A call about the networkWe review charger firmware, platform interfaces, roaming partners and who bills the driver.
- Route and engagement model, in writingAgree the product route and a time and materials, fixed price, or team extension model.
- NDA, then discoveryMost engagements start within two to four weeks of signature.