Charge point operators, eMobility service providers, and fleet operators with growing networks find that off-the-shelf charging platforms handle the basics but break down on the specifics: custom tariff logic, white-label driver apps, roaming settlement, energy load balancing across depot sites, and the real-time visibility their operations teams need to hit 97% uptime targets.
Charge point management systems built on OCPP 1.6 and OCPP 2.0.1, with real-time monitoring, remote control, and fault alerting
Driver billing apps and fleet portals with tariff configuration, payment processing, and automated invoice generation
OCPI-based roaming integration with Hubject and Gireve for multi-network interoperability and CDR settlement
Energy load balancing and smart charging controls that cap site demand and schedule fleet charging around grid tariffs
Recognition
Drivers failing on your network because uptime monitoring catches faults after the session fails, not before?
Finance team rebuilding billing data in spreadsheets because the platform's invoice export doesn't match how you charge fleets versus public drivers?
New charger hardware you want to add refusing to connect because your current software locks you to a single vendor's stack?
The short answer
RaftLabs builds custom EV charging software for charge point operators (CPOs), eMobility service providers (EMSPs), fleet operators, and property developers. We deliver charge point management systems, driver apps with real-time billing, OCPP/OCPI integration, energy load balancing platforms, and roaming settlement tools. Most EV charging software development projects deliver in 12 to 20 weeks at a fixed, agreed cost.
EV charging software covers the systems that connect charging hardware to the businesses that operate it: charge point management systems (CPMS) that communicate with chargers via OCPP, driver-facing apps and fleet portals with billing and session history, energy load balancing platforms that prevent site demand overruns, and roaming interoperability layers built on OCPI that let drivers charge across multiple networks.
01 Diagnosis
Your uptime monitoring catches faults after the driver session fails
When a charger goes offline or a connector gets stuck in a faulted state, most platforms log the event after the session fails. The driver gets a rejection. They write a one-star review. Your support team fields the call. By the time the fault is in your dashboard, the damage is done.According to a 2026 GlobeNewswire market report, the EV charging management software platform market is growing at 24.8% CAGR through 2035, driven directly by operators needing real-time fault visibility and network reliability tools to meet NEVI-mandated 97% uptime requirements. Meeting that target requires proactive monitoring: heartbeat analysis, status-transition alerts, and automated remote reset sequences that resolve the most common fault types before a driver arrives.A custom CPMS built for your network monitors charger health in real time, executes automated recovery sequences for known fault patterns, and escalates to your maintenance team with the fault code, charger location, and recommended action before the first driver complaint arrives.
Fleet billing doesn't match how you actually charge your clients
Fleet operators need invoices that reflect their rate agreements: cost per kWh with time-of-use adjustments, fixed session fees for specific vehicle types, monthly caps per vehicle, and separate cost centres per depot site. Off-the-shelf platforms typically offer one or two billing models.When the platform can't produce the invoice your fleet clients expect, your finance team exports raw session data and rebuilds it in spreadsheets. That process works until the fleet grows. At 50 vehicles it takes a day. At 200 vehicles it takes a week and introduces reconciliation errors that delay payment.Custom billing logic built to your tariff structure generates accurate invoices automatically, regardless of how complex your rate agreements are. Fleet portals give client account managers their own session history and usage reports, so invoice queries go down and payment cycles shorten.
Your energy costs at depot sites are unpredictable because charging is unscheduled
When 40 vehicles return to a depot and every charger activates simultaneously, the site draws peak demand that triggers demand charges on your utility bill. Those charges can exceed the cost of the energy itself. Without software that controls when charging starts and how much power each session draws, every fleet return creates an uncontrolled demand spike.Smart charging controls that read the site's live power draw, enforce a configurable site power limit, and schedule session start times around off-peak grid tariffs cut depot energy costs without reducing vehicle readiness. For operators in demand response programs, the same system can shed load on request from the grid operator and log the curtailment for incentive payments.
Roaming settlement with partner networks is a manual reconciliation exercise
EMSP platforms that support roaming via Hubject or Gireve receive charge detail records (CDRs) from partner CPOs covering sessions your drivers completed on external networks. Reconciling those CDRs against your billing system, matching tariffs, handling disputed sessions, and generating settlement invoices manually is a process that works for low roaming volume and breaks as your driver base grows.OCPI integration built into your platform automates CDR ingestion, tariff validation, and settlement generation. Disputed sessions trigger an automated workflow rather than a support email chain. Your finance team reviews exceptions, not every transaction.
02 What we ship
We build CPMS platforms on OCPP 1.6 and OCPP 2.0.1 that connect to any compliant charger hardware regardless of manufacturer. Real-time monitoring gives your operations team live charger status, active session data, and site-level power draw across every location in one view. Remote commands cover start and stop, remote reset, firmware update, and availability toggles for planned maintenance windows.
Fault management goes beyond logging. The system monitors heartbeat intervals, detects status transitions that precede faults, and executes configured recovery sequences automatically. When human intervention is needed, it routes the alert to your maintenance team with the fault code, charger location, and suggested action. Smart charging profiles per charger group enforce site power limits and support OCPP Smart Charging profiles for time-of-use scheduling.
Built for CPOs managing public networks of 20 or more sites, fleet depot operators needing depot-level control, and property developers who want a managed charging product for tenants rather than a third-party platform they can't brand or configure.
Driver-facing iOS and Android apps cover charger location discovery, real-time availability, session start and stop, live energy meter data, and in-app payment via Stripe or card-present payment terminals. RFID card management covers card issuance, balance, and access control for operators who offer subscription or pre-paid access models. Push notifications cover session start confirmation, completion, and any mid-session fault.
Tariff configuration in the backend drives what drivers see: per kWh, per minute, per session, and idle fee structures display accurately at the charger and in the app before the session starts. Session receipts and downloadable history satisfy corporate expense requirements without a call to your support team.
Built for CPOs who want a white-label driver app that matches their brand, EMSPs building a driver-first product to compete with existing networks, and property developers who want tenant EV charging as a managed service.
Fleet portals give operators visibility across every vehicle, charger, and depot in one view: current state of charge per vehicle, estimated charge completion times, session history per vehicle or driver, and energy consumption per cost centre. Access control via RFID or driver app restricts chargers to authorised fleet vehicles and blocks public use during depot hours.
Billing runs per vehicle, per driver, or per cost centre with the rate structure your fleet agreements require. Monthly invoice export in the format your finance system accepts removes the spreadsheet rebuild step. Integration with telematics platforms including Samsara, Geotab, and Verizon Connect pulls vehicle routing data so the charging schedule reflects actual departure times rather than a fixed overnight window.
Built for logistics operators, last-mile delivery fleets, municipal vehicle fleets, and any organisation managing 20 or more electric vehicles across one or more depot sites.
Site-level power management enforces a configurable maximum draw across all chargers at a location, distributing available capacity dynamically as sessions start and end. When a new session starts on a site already near its power limit, the controller reduces output on lower-priority sessions rather than rejecting the new connection.
Integration with energy APIs from Octopus Energy, utility demand response programs, and real-time electricity price feeds allows time-of-use scheduling that shifts load to off-peak windows automatically. For operators in grid demand response programs, the system sheds load on request and logs the curtailment event with timestamp and power data for incentive payment claims. Solar and battery storage integration allows the controller to draw from on-site generation before pulling from the grid.
Built for depot operators managing demand charges, commercial property owners with high-power charging installations, and energy retailers adding managed EV charging as a grid flexibility product.
OCPI 2.2 integration connects your CPMS or EMSP platform to roaming hubs including Hubject and Gireve, covering the full exchange: location and tariff publication, real-time availability feeds to partner networks, CDR ingestion, tariff validation against published rates, and settlement invoice generation. Drivers on your EMSP can use partner CPO networks without a separate account; drivers on partner EMSPs can use your chargers with their existing app.
Disputed CDR handling routes exceptions to a review queue with the source CDR, the matched tariff, and the discrepancy amount. Your team resolves exceptions rather than auditing every transaction. Monthly settlement reports reconcile what you owe to partner CPOs and what partners owe you, in the format your finance system accepts.
Built for EMSPs needing multi-network driver coverage, CPOs wanting to accept drivers from partner networks, and operators expanding from a national network into cross-border markets in Europe.
Maintenance management starts with the CPMS fault data: every fault event creates a ticket with the charger ID, location, fault code, and session impact. Ticket routing assigns to the right field engineer based on location and certification. The engineer app provides the work order, fault history for that specific charger, and parts requirements before they arrive on site.
Planned maintenance schedules integrate with charger availability management so the CPMS sets chargers to unavailable during the maintenance window and returns them to service automatically on completion. SLA tracking reports first-response time, time to resolution, and repeat fault rate per charger model, so your procurement team can factor reliability into hardware decisions. Integration with Salesforce Field Service and ServiceNow covers operators who already run field operations through those platforms.
Built for CPOs managing their own field service teams, network operators with third-party maintenance contracts needing visibility, and property owners who want fault reports without managing field operations themselves.
03 How we work
Companies we've built for
04 Track record
06 Client voices
Three-year average engagement. Founders and operators describing the work in their own words. No marketing varnish.
USARaftLabs nailed what other agencies couldn't. They started with our business problem and worked backwards to the right product. We were live in 14 weeks.
07 Why us
The industry changes. The broken process usually looks the same. Across 14+ industries and 100+ products, we recognise your problem fast, and we frame the fix around your margin and your operations.
We measure success the way you do: hours saved, revenue earned, margin recovered. We stay through launch and growth, so the result is ours to own.
Vodafone, T-Mobile, Cisco, Energia, Aldi, Nike. Six years, 100+ products in production, 4.9 on Clutch. Serious businesses keep coming back because we stay accountable long after launch.
08 Questions
Yes. A custom CPMS built on OCPP 1.6 or OCPP 2.0.1 communicates with any OCPP-compliant charger regardless of manufacturer. We build the backend to handle multi-vendor hardware, so you can add new charger models, switch hardware suppliers, or run a mixed estate without a software rebuild each time.
Yes. We implement OCPI 2.2 to connect your CPMS or EMSP platform with roaming hubs including Hubject and Gireve. This covers location and tariff publication, charge detail record (CDR) ingestion, tariff validation, and settlement automation. Your finance team reviews exceptions rather than auditing every roaming transaction.
A focused CPMS with real-time monitoring, remote control, and billing typically delivers in 12 to 16 weeks. A driver-facing app with payment integration adds 4 to 6 weeks. A full platform covering CPMS, driver app, fleet portal, energy load balancing, and OCPI roaming runs 20 to 32 weeks. Costs start around $35,000 for a focused CPMS and scale with scope. Fixed cost is agreed before development starts.
Yes. We build smart charging controllers that read real-time energy data from APIs including Octopus Energy and utility demand response programs, then schedule charging sessions across depot chargers to stay below site power limits and shift load to off-peak windows. The configuration is per site, not hardcoded, so tariff changes don't require a software update.
Off-the-shelf platforms cover standard public charging well. Custom software becomes the right choice when your tariff structure, white-label requirements, energy management logic, fleet billing rules, or hardware mix cannot be configured in a standard platform without significant compromise. We scope the boundary during discovery and will say clearly if an existing platform covers your requirements without a custom build.
OCPP 1.6 remains the most widely deployed version and is required for compatibility with the largest installed base of charger hardware. OCPP 2.0.1 adds improved security, device management, and smart charging capabilities and is the right choice for new deployments where hardware supports it. We build backends that handle both versions concurrently so you can support your existing estate while onboarding new OCPP 2.0.1-compliant hardware.
Charge point management system development
OCPP 1.6 / 2.0.1 backends, real-time monitoring, remote control, fault management
EV charging app development
white-label driver apps, RFID, in-app payment, session history
Fleet EV charging software
depot management, vehicle scheduling, cost centre billing, telematics integration
EV charging billing software
tariff configuration, invoice generation, payment gateway integration, fleet billing
EMSP platform development
driver account management, OCPI roaming, CDR processing, settlement
Energy load balancing software
site power management, smart charging, demand response, solar integration
OCPI roaming integration
Hubject, Gireve, CDR exchange, tariff publication, settlement automation
EV charging maintenance software
fault ticketing, field engineer dispatch, SLA tracking, planned maintenance
Tell us what you are building: a CPMS, a fleet portal, a driver app, or a full network platform. We will scope it out together.