The European CSMS that speaks every OCPP version and every roaming hub. Ready to deploy on day one.
- OCPP 1.5 + 1.6 + 2.0.1
- OCPI 2.2.1 + 2.3.0
- AFIR-compliant
- 700+ REST endpoints

Small operators (1-10 stations)
You bought chargers. Now you need to accept payments, issue invoices, and prove compliance.
Cloud signup in minutes. Stripe-ready. AFIR-compliant QR payment. No dev team required.
Network operators (10-500 stations)
Your current CSMS is locked to one vendor, slow to change, and invoicing breaks monthly.
OCPP-agnostic platform. Migrate without downtime. Open REST API. Partner commission on autopilot.
Developers, hotels, retail
You want charging on your premises for ESG reports and tenant value — not to become a CPO.
Turnkey partnership: we accept payments, you receive monthly payouts. AFIR compliance handled.
EV fleets and car-sharing
Drivers charge everywhere. Reimbursement is a mess. No single view of TCO per vehicle.
Per-driver RFID, per-vehicle reports, fleet API. Pull session data straight into your ERP.
Station manufacturers
Your customers ask for software. Building it in-house costs years and tens of millions.
White-label the platform under your brand. Multi-tenant isolation built in. Revenue-share or per-station license.
Fuel retailers and travel centres
EV charging is not your core business, but you need it live — with roaming, uptime, and reports for corporates.
OCPI 2.2.1 + 2.3.0. Hubject and Gireve integration. Proven production uptime. Enterprise-friendly onboarding.
Think of a CSMS like Shopify for EV charging. Your stations are the inventory, drivers are the customers, and the platform handles everything in between: identity, payments, roaming, invoices, and compliance.
- 01
Driver arrives
Scan a QR code, tap an RFID card, or open the driver app. The platform identifies the driver and checks authorization.
- 02
Payment is held
For ad-hoc QR payment, Stripe authorizes a hold (30 to 100 EUR depending on charging speed). For registered drivers — a saved card or wallet balance.
- 03
Charging starts
The platform sends OCPP RemoteStart to the station. The connector locks, power flows to the vehicle, and the session is live.
- 04
Usage is metered
Real-time MeterValues arrive every 30 seconds. Cost is calculated per sampled reading with tariff rules (day/night, peak hours, idle penalties).
- 05
Session ends
Driver stops charging or unplugs the vehicle. The platform builds the invoice, captures the exact amount from the hold, and releases the rest.
- 06
Everything is logged
Session, invoice, payment, OCPP messages — all auditable. Roaming partners receive CDRs. Reports export to your accounting system.
OCPP — station protocol
OCPP 1.5 (SOAP)
Legacy support for stations from 2012-2015. Most modern platforms dropped it. We kept it because your old hardware still works.
OCPP 1.6 (JSON/WebSocket)
The market mainstream. 25+ Central System commands, 10 station messages, full spec coverage. JSON↔SOAP conversion for mixed fleets.
OCPP 2.0.1 (JSON/WebSocket)
Next-generation protocol with three-tier data model (Station → EVSE → Connector) and string transaction IDs. Core production-ready.
OCPI — roaming protocol
Full OCPI 2.2.1 + 2.3.0 implementation. 11 of 15 modules live. Hubject and Gireve hubs integrated. Adaptive serialization for older partners and Hubject 2025+.
CPO sender
Publish your stations to roaming hubs. Receive authorization requests and commands from foreign drivers.
eMSP receiver
Your drivers charge on any partner station. Locations cached locally. Sessions and CDRs synchronized in real time.
Works with any OCPP-compliant station
Automatic station registration on first boot. Vendor profiles handle BootNotification quirks, status code mapping, and charging profile semantics. Onboarding a new vendor typically takes one to three days of integration testing.
Scan the QR
Each connector has a QR printed or displayed. No app install, no account.
See the price
Tariffs shown per charging mode (slow / standard / fast / ultra) with hold amounts in EUR.
Pay with Stripe
Stripe Checkout handles 3DS when required. Hold of 30-100 EUR placed on the card.
Charging starts
Platform creates a guest driver record, sends OCPP RemoteStart, connector locks.
Real cost captured
At session end, Stripe captures the actual amount used. The rest of the hold is released.
Full audit trail
Every step is logged. Regulators can request a compliance report at any time.















