EV Charging Software: Build, Buy or Route?

The five positions

What actually triggers a build

Three things, and rarely cost alone. A workflow no platform supports without concessions you cannot make. A commercial model, such as embedding charging in another product, that per-charger pricing makes unviable. Or a scale at which recurring platform cost exceeds an engineering team.

If none of these apply, building is usually the expensive answer to a question that had a cheaper one.

Routing is the underused option

Where the pressure is optionality rather than functionality, a routing layer between chargers and backends preserves the ability to change platform without changing hardware, and to run different backends for different parts of an estate.

It is materially less work than building a platform and solves the lock-in problem that motivates most build decisions.

The obligation people underestimate

A charging platform is not a project that finishes. OCPP evolves, chargers behave unexpectedly, security expectations rise, and drivers expect the app to work at midnight. Building means staffing that permanently, and the cost of stopping is higher than the cost of never starting.

Our disclosure

RIOD builds custom platforms, supplies a platform, and builds the routing layer. Every option on this page is one we sell, which is a conflict rather than a coincidence, and it is why the page argues against building at the volumes where building does not pay.

Why we stopped reselling a shared platform

We learned this one the expensive way, so it is worth being direct about it.

We used to put customers onto a third-party white-label platform. It carried each customer's brand, and underneath it was one system serving all of them. That arrangement is fine until you want a change. Then it is not fine, because the change either cannot be made or it lands on everybody at once. A request that is reasonable for one operator is a regression for the four sitting next to them on the same platform.

Eventually a change became unavoidable. The only way to make it was to send people out to every charger and do it physically, unit by unit, in the field. That is the point at which a software decision made years earlier becomes a software change that requires a visit to every site.

Charger360 exists because of that. It lets a charger move between management platforms without anyone visiting the site. If a platform is discontinued, if its terms change, or if it simply stops being the right one, the fleet switches remotely. Changing a backend should not require a visit to the site.

The honest split

The decision is not really build against buy. It is about what you are building.

1. 1

   A handful of chargers, charging is not the business

   Use a third-party CMS. It is the right answer and there is nothing clever about the alternative. The cost of building would never be recovered.

2. 2

   Charging is the business, and you intend to scale

   Build toward your own. Not necessarily today, but the direction should be settled now, because every decision taken in the meantime either helps or hinders it.

What makes the second case different is not size. It is that once charging is the business, the software is the business, and every differentiator lives in it: pricing, access, reliability, billing, and knowing your own customers.

What you give up by staying on someone else's

• The data. Without it, customers and performance are visible only through what the supplier shows you
• The billing and the reconciliation, which is where disputes are actually settled
• The pace of change. Charging is still moving, and a feature you need is a request on a supplier's roadmap
• The exit. If the supplier stops, or the terms change, the chargers can become assets you cannot operate

The last one is not hypothetical. A charger tied to a platform that has gone away cannot be reached to be repointed, and you cannot send an engineer to every site to change a charge box identifier.

You do not have to choose today

The reason this decision feels binary is that most people believe the migration is impossible once the fleet is in the ground. That is what Charger360 exists to fix.

It sits between your chargers and whatever platform they report to, and it lets a fleet be repointed remotely. So a network can start on a third-party CMS, keep control of where the chargers connect, and migrate to its own platform later without anyone visiting a site.

That turns build against buy from a decision you make once, badly informed, into a direction you can move in when the business is ready.