Enterprise
From one siteto every border.
For charge point operators, charger manufacturers and energy companies with big plans. We build your CSMS, roaming, payments and apps on an architecture made to scale, with the rules you must meet built in, and hand you the keys.
- OCPP 1.6J · 2.0.1 · 2.1
- OCPI 2.2.1, CPO and eMSP
- Multi-tenant
- NDA, MSA, SOW and DPA
One site
A handful of connectors, up and running.
Illustrative. The CSMS we build for you, from your first site to roaming.
Engineered for scale
A reference of what we build. Each part grows on its own, and every charger event reaches every service that needs it.
Chargers
Ingest
Services
Access
People & systems
Illustrative reference architecture. Every build is shaped around your network.
- 01
Scale out, not up
Microservices behind API gateways: each part grows on its own, so one busy service doesn't hold up the rest.
- 02
Events, not polling
Kafka streams every charger event to every service that needs it, in order.
- 03
Fast where it counts
Rust and Python services, each picked for the job in front of it.
- 04
Workers that watch
Intelligent workers catch anomalies, retry what failed and run payouts without a ticket.
Built to pass audits
The rules for public charging are tightening around the world. We build what they ask for into your platform from the start.
The rule
>97%
Average annual uptime for every NEVI-funded charging port, reported each quarter with session, energy and outage data. Contactless card payment, no membership required.
Source: 23 CFR 680
What we build in
- Uptime and outage history per connector
- Quarterly session and energy exports
- Contactless card payment, no app or account
Sources ›
- 23 CFR 680.116: uptime and data sharing (Cornell LII)
- 23 CFR 680.112: data submittal (Cornell LII)
- GOV.UK: Public Charge Point Regulations 2023 guidance
- California Energy Commission: EV charger data and reliability standards
- AFIR data rules (Fintraffic)
- Renewable Watch: MoP EV charging guidelines 2024
- 23 CFR 680.106: NEVI payment methods
- European Commission: AFIR questions and answers
- OCA: OCPP becomes IEC 63584
- OCA: OCPP 2.1 published as IEC 63584-210
How a large programme runs
Six phases, each ending with something you can check before the next one starts.
- 1
Discover
Your network, markets, chargers and systems, mapped with your team.
You get: Scope, risks and a phased plan
- 2
Design
Architecture, flows and screens, agreed before any code.
You get: SOW with milestones and acceptance criteria
- 3
Build in phases
A dedicated team ships milestone by milestone, with access to work in progress.
You get: A working release at every milestone
- 4
Pilot
Every flow tested against OCPP simulators, then on your real chargers.
You get: Go-live sign-off on your criteria
- 5
Go live and scale
Launch on your domain, then add sites, partners and roaming on the same CSMS.
You get: Monitoring and alerts from day one
- 6
Hand over
Source code and deliverables pass to you once paid. We stay on for support.
You get: Your code, your data, your choice of team
Enterprise-ready by contract.
The paperwork your procurement team expects, before a line of code.
Security & ownership- Mutual NDA before discovery
- MSA, SOW and DPA on request
- Source code passes to you once paid
- Named point of contact
- Changes agreed in writing
- Warranty fixes at no extra cost
Proof, not promises.
Charging platforms we have built and shipped, for clients in 10+ countries.
- clients served worldwide
- 0+clients served worldwide
- countries
- 0+countries
- CSMS projects
- 0+CSMS projects
- app downloads
- 0K+app downloads
Plus a driver app with 150K+ downloads. See all our work
Questions big teams ask us.
Can you work alongside our existing systems?
Yes. We connect to your ERP, BI and support tools through APIs and webhooks, to partners and hubs over OCPI, and your chargers can be re-pointed to the new CSMS instead of being replaced.
Which protocols do you cover?
OCPP 1.6J, 2.0.1 and 2.1 for chargers, and OCPI 2.2.1 for roaming in both CPO and eMSP roles.
Who owns what we build?
You do. Ownership of custom deliverables, including source code, passes to you once they are paid in full. Our pre-existing tools stay ours, with a perpetual licence for you to use them in what we deliver.
Will you sign our NDA, MSA and DPA?
Yes. We sign a mutual NDA before any discovery work, and an MSA, SOW and DPA on request.
How is a large programme priced?
Large builds run as project-based work with a custom quote and agreed milestones, typically 20% upfront and the rest by milestones. Ongoing work can run on a monthly retainer.
Available
Ready to switch on your charging network?
Book a 30-minute call with our team. Whether it’s your first charger or a growing network, you’ll leave with a clear plan.
30 min · video call
L1 · L2 · L3, 120° apart
DC link
DC to the car
- 1
Tell us where you are
Your chargers, your market, and what you want to launch.
- 2
We map the build
CSMS, OCPP and OCPI, payments and apps, scoped to your business.
- 3
Leave with a plan
A clear next step, whether you build your own or start on ours.
Mumbai, India · working with EV teams worldwide