Problem
Solution
Result
About evyve
Headquartered in London, evyve is a UK rapid and ultra-rapid public charging operator. They manage a 100% renewable, nationwide network across business and retail parks, leisure destinations, and roadside sites.
In their own words, they’re a “pure-play CPO providing a fully funded model” – meaning they own the chargers, the sites, and the commercial relationships. Roughly half of their revenue comes from roaming, the rest from their own drivers.
They are also hardware-forward. In October 2025, evyve and Monta became the UK’s first customer to deploy Nidec’s DC Split Power ultra-scaling platform, taking site speeds up to 300 kW. The operational bar – drivers expecting a working, fast, dependable charge every time – is non-negotiable.
The challenge
evyve’s previous CPMS had taken the network as far as it could. It worked reliably as a piece of software, but did not work as the infrastructure layer a fast-growing, roaming-heavy challenger CPO needed underneath it.
Three structural constraints had become commercial constraints.
1. Anonymous drivers, no relationship
Prior to Monta, drivers using evyve’s chargers were effectively invisible to evyve. There was no way to identify them, send them notifications, offer them a discount, or build a loyalty programme. Sessions took place, revenue came in, drivers moved on – but the customer relationship sat with the software provider, not evyve – the brand the drivers had actually plugged into. evyve saw an opportunity to own the driver relationship directly – for a CPO with challenger ambitions, that was a strategic priority.
2. Half the revenue, limited control
Roughly 50% of evyve’s revenue comes from roaming. That makes inbound EMSP traffic, bilateral OCPI agreements, and the technical orchestration of partner connectivity a substantial part of the business. evyve wanted to control that journey end-to-end: from charge point installed to driver served, regardless of which app the driver arrived through. Roaming was being treated as a feature, not a strategic layer.
3. Slow data, slow features
UK rapid charging is a fast-moving market. New regulatory expectations, hardware capabilities, and driver behaviours – operators that aren’t continuously evolving get left behind. With evyve’s previous software system, the realistic timeline for a non-critical feature request was 18 months. Data was hard to extract, dashboards were generic, and the team had no way to build the operational insight they needed on top of the platform. That gap, repeated across dozens of small product needs, was a structural cost to the business.
Why evyve chose Monta
evyve ran a rigorous evaluation before selecting Monta. They named the things they were buying on directly: uptime, operational excellence, payments, branded driver experience, and load balancing. Beneath all of them sat a more fundamental criterion – that Monta operates as infrastructure, not a component, and that evyve and Monta share a challenger identity.
- Infrastructure, not a component – every capability evyve needed – driver app, EMS, OCPP, OCPI roaming, payments, alerting, real-time monitoring – was already built into a single, API-forward foundation. evyve could start with Monta as it comes and extend on top as the business grows.
- Roaming as a core business area – inbound and outbound OCPI flows, bilateral agreements with partners evyve already had relationships with, and the ability to take more control of that orchestration over time
- Matched development pace – with Monta shipping features in weeks where the need is shared across operators.
- A true migration partner – evyve was migrating a live, revenue-generating, nationwide rapid network with multiple hardware brands and active roaming partners. Monta’s willingness to spend three months on joint planning before touching a single charger was decisive.
The solution
1. A driver app that users actually download
The most visible change for evyve was getting its driver relationship back. Built on Monta’s technology and branded as evyve, the app gives evyve direct visibility of the people using its network and a promotional layer through Monta discount and voucher features. This way, a session becomes the start of a relationship.
Practically, that has translated into a recurring pattern in evyve’s weekly ops cadence: app downloads have surged month over month, employee-charging discounts are being rolled out site by site, app-specific tariffs and promotional codes are live. Each of those is a feature Monta shipped during the relationship – and reflects capabilities evyve prioritised as part of its platform upgrade.
The strategic point is simpler than any individual feature. Drivers who used to be anonymous are now an evyve audience: identified, reachable, and segmentable. That is the foundation of every loyalty and growth play a CPO can make.
2. Roaming is treated as a strategic layer
Monta acts as the middle layer between evyve’s chargers and the broader EMSP network: handling inbound roaming traffic from the UK’s major eMSP apps and cards, supporting self-managed inbound agreements as evyve takes more direct control of partner relationships, and unifying roaming sessions and evyve-direct sessions inside the same reporting, settlement and customer-support flows.
That matters commercially in two ways. First, evyve does not have to choose between defending roaming revenue and growing its own driver audience – both flow through the same system. Second, as evyve scales toward 1,000+ rapid chargers, the same orchestration handles more partners, more sites and more session volume without needing a different operational model.
3. Data and pace – operational insight at the speed of the market
evyve told Monta upfront that data was critical to them: tracking customer retention, understanding network utilisation, watching where their own drivers and roaming drivers behaved differently. Monta now provides that as part of the infrastructure: API access to raw operational data, a data warehouse trial that evyve’s analytics team is actively using, and real-time dashboards built directly on top of the Monta API.
Underneath that data layer is a shared development cadence. Monta ships in weeks for needs that are real and shared across the operator base – and the API-forward foundation means anything evyve wants to build on top is reachable, not gated behind a vendor roadmap.
AI is folded into that same picture: agents running across operational workflows rather than a bolted-on feature, with evyve’s ops team using Monta AI to surface and resolve issues.
A migration, done quietly
Migration to Monta was completed in one week, after three months of joint planning between the Monta and evyve teams. Every charger model was mapped and tested for hardware compatibility, site-level load balancing was validated, and each roaming partner relationship was confirmed site by site – so drivers arriving with any major UK eMSP card or app on the migration day would charge normally. The migration itself was seamless: every site moved across in a week – with no downtime or lost revenue.
The results
The most useful evidence for a prospect is how evyve has spent its time since the migration – not the migration itself.
A driver audience evyve can talk to
Where evyve previously had no direct line to its drivers, the evyve app is now a live channel. App downloads and active usage have surged through Q1 and into Q2, with promotions, discounts running through the same surface. evyve runs the customer relationship; Monta handles the heavy lifting underneath.
Roaming and direct, in one operation
Roaming traffic and evyve’s own-driver traffic now run through the same system, with unified session, settlement and support flows. That removes the operational tax of running two parallel businesses – one for roaming partners, one for direct drivers – and gives evyve room to grow utilisation on both sides without changing how the team operates.
Features shipped at pace
Pay-by-invoice, app-specific tariffs, real-time and AI dashboards – all moved from a Monta – evyve conversation in a matter of months. For a CPO scaling toward 1,000+ rapid chargers, that delivery cadence compounds across dozens of decisions.
