eMSP software, full service: from charge point to invoice.
i4B designs, builds and runs the software behind e-mobility service providers: the driver app, OCPI and OICP roaming, tariffs and billing, and the integrations that turn every charging session into revenue.
Why eMSP platforms stall after launch
The pilot works. Then partners, countries, tariffs and drivers multiply, and the platform that was good enough for launch starts leaking sessions, revenue and patience. Off-the-shelf stops where your business model starts.
Roaming is never done
Every new hub, every OCPI version, every partner reading the spec its own way - and the integration that worked in the pilot starts dropping sessions.
Revenue leaks at the edges
Roaming CDRs arrive late, tariffs differ by country and partner, corrections pile up. Money disappears one disputed session at a time.
The app is only as good as the backend
Drivers judge you by whether start charging works on the first tap. When it doesn't, they blame you - not the CPO.
Scale is a load test you didn't schedule
Ten times more chargers means ten times more OCPP traffic. Without queuing and fault isolation, one spike takes sessions down across the network.
Inside the platforms that charge Europe's EVs.
What stands out most is the combination of technical expertise and an understanding of the business context of the project. i4B did not approach the cooperation only as a set of IT tasks to complete but tried to understand why certain solutions were needed and what they meant from our perspective.
Full service means we stay after go-live.
Discover
Your business model, roaming partners and existing systems mapped before a line of code. If you don't need a custom build, we say so.
Build
A dedicated team in 1-2 week sprints, test-driven. Working software every sprint.
Integrate
Hubject, OCPI partners, your CSMS and your ERP, connected and mapped to your billing model.
Validate
Roaming and charging flows tested end to end, across instances and charging profiles, before they reach a driver.
Run and evolve
Monitoring, protocol upgrades, new hubs and new markets. The platform keeps up with the spec.
Roaming that holds up on both sides of the session
We build CPO and eMSP software, so we know where roaming breaks - on both ends. Every connection is tested end to end before a driver ever sees it.
OCPI 2.1.1 and 2.2.1
Direct peer-to-peer connections with CPO networks: locations, tokens, sessions, tariffs and CDRs.
Hubject OICP, both sides
eMSP side for your drivers' app, CPO side to publish your stations - remote control, session handling and CDRs across Hubject networks.
ENAPI for the UK
Remote start and stop, token forwarding and CDR processing, so app users charge on UK public networks.
Private roaming hubs
CPOs on the same platform roam on each other's stations without Hubject or GIREVE: token exchange, EVSE visibility and session forwarding.
Pick the scope, integrations and support model - and get an estimate in minutes.
Everything an e-mobility service provider runs on
White-label driver app
Find a charger, start and stop, live status, history and payment. On your backend or on AMPECO.
Roaming connectors
OCPI, OICP and ENAPI - token exchange, EVSE visibility, remote control and CDR processing.
Tariffs & billing
Per-kWh, per-minute and time-of-day pricing, subscriptions, invoicing and corrections in one place.
Authorisation & Plug & Charge
RFID, app-based authorisation and ISO 15118 Plug & Charge, tied to customer and fleet accounts.
Fleet & B2B accounts
Billing isolated per fleet, cost per vehicle and driver, CDR export to the client's ERP.
Event-to-Action automation
Charger events trigger actions: repeated faults mean auto-reset and an operator alert.
Back-office integrations
ERP, invoicing and CRM via REST and webhooks; tariffs synced with your pricing engine.
The CPO side too
A CSMS on OCPP 1.6 and 2.0.1 - registration, diagnostics, firmware - on the same stack.
Starting from zero, or from a platform you already have
Most eMSPs don't start from a blank page. We build the whole platform when that is the right call - and when it isn't, we build around what you already run.
Build: new eMSPs
For eMSPs launching their own offer, or outgrowing a licensed platform: backend, driver app, roaming and billing built for your model.
Integrate: existing platforms
For eMSPs already on AMPECO, another CSMS or an in-house backend: branded app, roaming connectors and billing integrations on top.
Both: one team
The same engineers who build platforms integrate them, so a hybrid - keep the CSMS, replace the app - is a normal project, not an exception.
Not sure which?
That's what the first conversation is for. We look at your stack and partners and tell you which path costs less.
Roaming hub access (Hubject, ENAPI, GIREVE) requires your own agreement with the hub operator. We are happy to advise.
Your business model, not a vendor's roadmap
Work with us the way that fits: consulting and discovery billed hourly or per project, a dedicated team on a monthly fee, or full project outsourcing at a fixed price or time and materials.
Standards first, integrations around what you run
Native OCPP, OCPI and OICP implementations, and connectors to the platforms eMSPs actually use - built and tested by engineers who work inside CSMS cores.
Hubject, CPO and eMSP
OICP on both sides: publish your stations with dynamic EVSE data and real-time status, or give your app users access across Hubject networks.
AMPECO
A branded driver app on AMPECO's backend, or sessions, CDRs and tariffs flowing from AMPECO into your own back office and invoicing.
ERP & invoicing
Session events mapped to your billing model, tariffs synced with your pricing engine, RFID cards linked to customer accounts.
Built to scale
OCPP event flows tuned for high concurrency, message queuing for spike resilience and microservices isolated so one fault stays one fault.
Need a single connector rather than a whole platform? See every project, protocol and tech stack in our EV charging integrations portfolio.
Built for e-mobility businesses that are past the pilot
New eMSPs
Launching their own driver offer and roaming from day one.
Growing eMSPs
Outgrowing a licensed platform, its fees or its roadmap.
CPOs adding an eMSP
Operators who want their own app and contracts on top of their network.
Fleet & mobility operators
Running drivers, depots and partner networks under one account.
Tell us where your eMSP platform is today
30 minutes with an engineer who has built roaming integrations, not a sales script. We'll tell you honestly whether to build, integrate or leave it as it is.
Frequently asked questions
What is an e-mobility service provider (eMSP)?
An e-mobility service provider (eMSP) gives EV drivers access to charging - through an app, an RFID card or Plug & Charge - and bills them for it. An eMSP does not have to own any chargers: it reaches stations operated by charge point operators (CPOs) through roaming agreements and protocols such as OCPI and OICP.
What is the difference between a CPO and an eMSP?
A charge point operator (CPO) owns or operates charging stations and manages them through a CSMS using OCPP. An eMSP serves the driver: the app, the account, the contract and the invoice. Many companies are both, which is why their software has to handle both sides of a charging session.
What software does an eMSP need?
At minimum: a driver app, customer accounts and authorisation, tariff and billing logic, and roaming connections to CPO networks - directly via OCPI or through hubs such as Hubject. Most eMSPs also need integrations with ERP, invoicing and CRM systems, and analytics on sessions and revenue.
What does full-service e-mobility software development include?
At i4B it covers discovery, design, development, roaming and back-office integration, end-to-end testing, and ongoing maintenance after go-live - including protocol upgrades and onboarding new roaming partners. One team is responsible for the whole platform rather than a single component.
Should we build our own eMSP platform or license one?
Licensing is faster to start and works well for a standard offer. Building - or extending a licensed platform with custom software - makes sense when your pricing, subscriptions, fleet or B2B model don't fit the vendor's roadmap, or when licence fees grow with your session volume. i4B does both: builds platforms from scratch and integrates with existing ones such as AMPECO.
Which roaming protocols and hubs do you support?
OCPI 2.1.1 and 2.2.1, OICP for Hubject on both the CPO and eMSP side, and ENAPI for UK networks. We have also built private roaming hubs that let CPOs on the same platform share stations without an external hub.
What is the difference between OCPP and OCPI?
OCPP is the protocol between a charging station and its management system (CSMS) - it starts sessions, reads meter values and pushes firmware. OCPI connects platforms with each other, typically a CPO with an eMSP, so drivers can charge on networks they have no direct contract with. An eMSP platform mostly speaks OCPI; its CPO partners speak OCPP to their chargers.
Can you work with a platform we already run, such as AMPECO?
Yes. We have built branded driver apps on AMPECO's backend and connected AMPECO session data, CDRs and tariffs to clients' own back-office and invoicing systems. Integrating with what you run is often faster and cheaper than replacing it.
Do you also build the CPO side - the CSMS?
Yes. i4B builds and maintains CSMS platforms on OCPP 1.6 and 2.0.1 - charger registration, session control, diagnostics, firmware updates and Event-to-Action automations - and works on the core of large multi-tenant CSMS platforms. Many eMSPs also operate chargers, so both sides can share one stack.
How do you work with us commercially?
Three ways: consulting and project discovery, billed hourly or per project; a dedicated development team working as an extension of yours, on a monthly fee based on team size; or full project outsourcing at a fixed price or time and materials. Most clients start with discovery.