Multi-tenant EV charging platform
One console for tenants, stations, chargers and orders. Tariffs split by peak, flat and valley in each station's own timezone. Settlement, payouts and reconciliation that balance to the cent, with OCPP at the device edge and OCPI toward roaming partners.
Energy delivered, 24 h
Recent sessions
Sample Depot Lisbon (placeholder) · Sample data - replace with real operations data
Who it is for
Platform surfaces
The platform team, the operator and the driver each get their own surface and their own permission model, backed by the same ledger. Nothing is copied between them, so nothing can disagree.
/platform
The control room for the platform owner: tenant provisioning, cross-tenant reporting, regional settings, tariffs and pricing templates, commissions and settlement runs, withdrawals, invoices, channel reconciliation, alarms and scheduled jobs.
/mppc /mp
Self-service for charge point operators and their sub-merchants, on desktop: publish tariffs, watch connectors, handle refunds, approve driver accounts, download statements and request payouts. Every view is scoped to the merchant subtree, so operators never see each other's numbers.
PWA · iOS · Android
Drivers get an installable PWA that also runs in any mobile browser, plus native Android and iOS builds from the same codebase. Find a charger, start and stop a session, watch live energy and cost, top up the wallet, download receipts. No app store detour required to charge.
Capabilities
Charging is rarely the hard part. Tariffs, money and auditability are. These are the modules that carry them, each one built to be re-run and explained.
Every business table lives in the tenant's own database rather than behind a filter, so a query cannot leak across customers by forgetting a where clause. Tenant context is resolved from the request and never guessed.
Three levels of asset register with live connector state, telemetry curves, error codes and offline sweeps. Alarms from the same charger and code are merged instead of flooding the list.
Peak, flat and valley energy and service prices are resolved against the station's timezone, falling back to the tenant's. Overlapping or gapped periods are rejected before a tariff goes live.
One session per connector, with the wallet balance frozen up front so a driver cannot overspend. Settlement charges what was delivered and releases the difference automatically.
Multi-level commission rules with tiers and a cooling-off period. Refunds reverse the commission that was already allocated, and every line item points back to its session.
Withdrawal requests move through an approval state machine with the bank account on file. Invoices and channel statements are managed in one place, and payment differences are held for a human instead of being adjusted silently.
Load management is expressed as OCPP charging profiles, so the schedule is executed on the charger itself and survives a dropped connection. Profiles can be simulated before they are applied.
A lightweight scheduler runs idempotent jobs tenant by tenant, so one customer's failure never blocks another. Every run is recorded, and jobs can be replayed by hand during an incident.
How it works
Create the tenant, its database and its first administrator. Currency, timezone, locale and regional module set come from the tenant profile, so a Spanish operator and a Russian operator can run side by side on one installation.
Register stations, chargers and connectors, then point the chargers at the OCPP endpoint. OCPP 1.6J and 2.0.1 connect on the same platform, and vendor devices that speak MQTT are normalised to the same asset model.
Define energy and service prices per period, plus start fee, idle fee, minimum spend and a per-session cap. Tariff periods are validated against the station timezone and snapshot when a session starts, so repricing never rewrites history.
A driver scans, taps or uses the app, authorises a payment method, and follows live energy, power and cost. Card, Apple Pay and Google Pay run through Stripe, PayPal runs alongside it, and bank transfer is available with manual confirmation.
Finished sessions settle at the metered amount, commissions are allocated, statements and invoices are produced, and the channel statement is reconciled line by line. Anything that does not match is parked for review.
Integrations and API
Speak OCPP to the hardware, OCPI to roaming partners, and REST with signed webhooks to everything else. Protocol differences are absorbed at the gateway, so the tariff and settlement logic never forks per vendor.
Boot and heartbeat, status notification, authorisation, start and stop transaction, meter values, charging profiles, remote start and stop, reset, unlock, configuration and firmware triggers.
WebSocket · :9002
Built toward the roaming direction international partners expect: locations, tariffs and sessions exposed between operators rather than a single-country standard.
EMSP direction
Every console action sits on the same documented REST surface. Subscribe to session, settlement and alarm events and receive signed deliveries with a retry log you can inspect.
:8090 · OpenAPI
Manufacturers that expose their own MQTT protocol are mapped to the standard asset and telemetry model, including meters, storage and site loads that are not charge points at all.
TCP · :9003
GET /api/v1/connectors?station=sample-depot-lisbon
Authorization: Bearer <token>
200 OK
{
"station": "Sample Depot Lisbon (placeholder)",
"connectors": [
{ "id": "A-01-2", "status": "Charging", "power_kw": 44.0 },
{ "id": "A-03-1", "status": "Available", "power_kw": 0.0 }
]
}POST /your-endpoint
X-Signature: t=1770000000,v1=...
{
"event": "session.completed",
"tenant": "acme-sample",
"connector": "A-01-2",
"energy_kwh": 41.2,
"amount": { "value": 3860, "currency": "EUR" },
"tariff_periods": ["valley", "flat"]
}[2, "cp-42", "SetChargingProfile", {
"connectorId": 1,
"csChargingProfiles": {
"chargingProfileId": 7,
"stackLevel": 0,
"chargingProfilePurpose": "TxDefaultProfile",
"chargingProfileKind": "Recurring",
"recurrencyKind": "Daily",
"chargingSchedule": {
"chargingRateUnit": "A",
"chargingSchedulePeriod": [
{ "startPeriod": 0, "limit": 32.0 },
{ "startPeriod": 79200, "limit": 16.0 }
]
}
}
}]Illustrative request and response shapes. The live OpenAPI schema is served by the platform itself. Figures are sample data (placeholder).
Security and compliance
Written as engineering facts rather than badges: these are properties of the platform, and no certification is claimed on this page that the product does not hold.
Driver data is scoped to the tenant that collected it, exports are explicit rather than incidental, and where country lookup is used it can run from a local database so visitor IP addresses never leave your infrastructure.
Business tables live in a per-tenant database instead of carrying a tenant column. Isolation is a property of the connection, not of every query being written correctly.
Platform and merchant sessions are separate and their tokens are not interchangeable. Permissions are assigned per role and per merchant subtree, and a missing tenant context fails loudly instead of falling back.
Operator actions, sign-ins, scheduled job runs, remote commands sent to hardware and payment callbacks each keep their own record, including who did it, when, to which device, and what came back.
Payments and money flow
Cards plus Apple Pay and Google Pay through a single integration, with authorisation before the session and capture of the metered amount at the end. Refunds and partial refunds are issued from the same interface as the original charge.
For drivers and fleets that prefer a PayPal balance: the same order lifecycle, the same idempotent callback ledger, and the same settlement line as a card payment.
Some markets still pay by transfer. Drivers or fleet managers upload proof, staff confirm it in the console, and the credit lands on the wallet with the approver recorded.
Language and localisation
A first-time visitor is served the language that fits where the request came from: Traditional Chinese for Taiwan, Hong Kong and Macau, Spanish for Spanish-speaking markets, Russian for Russian-speaking markets, and English everywhere else.
Once someone picks a language, that choice follows them and overrides any geographic guess. If the platform cannot tell where a request came from, it serves English rather than guessing.
Interface language, currency and timezone are three separate settings. Currency is configured per tenant, tariff periods are cut in the station timezone, and changing the language never changes a price.
This site is English by default. Use the language selector in the header: navigation, headings and buttons switch immediately, and the choice is remembered in your browser. Body copy on a static page stays English, which is why the product's own localisation is the thing to evaluate on a demo.
Note: a static page cannot look up an IP address, so this demo detects language from your browser language and timezone. The product itself resolves locale server-side from CDN country headers, a local country database or the user's own choice.
Pricing
Feature grouping follows the product's own module boundaries. Numbers are placeholders: real pricing depends on site count, connectors and settlement complexity.
Single operator, one country, charging and payment working end to end.
$0,000/ site / month
Placeholder price - replace with real pricing
Most common
Several operators or sub-merchants, with money moving between them.
$0,000/ site / month
Placeholder price - replace with real pricing
Private deployment, custom integrations and roaming.
$0,000/ site / month
Placeholder price - replace with real pricing
| Capability | Starter | Growth | Enterprise |
|---|---|---|---|
| Platform console: tenants, stations, chargers, connectors | Included | Included | Included |
| Tariffs split by peak, flat and valley per station timezone | Included | Included | Included |
| OCPP 1.6J charge point connections | Included | Included | Included |
| OCPP 2.0.1 charge point connections | Included | Included | Included |
| Driver PWA and H5 | Included | Included | Included |
| Native Android and iOS apps | PWA only | Included | Included |
| Sub-merchants, commissions, statements, payouts | — | Included | Included |
| Invoices and channel reconciliation | — | Included | Included |
| Smart charging through OCPP charging profiles | — | Included | Included |
| Vendor MQTT devices: meters, storage, site loads | — | Included | Included |
| OCPI / EMSP roaming with partner networks | — | On request | On request |
| Database-per-tenant isolation | Included | Included | Included |
| Role-based permissions and audit logs | Included | Included | Included |
| Deployment model | Shared cloud | Shared cloud | Private or on-premise |
| Custom integrations and migration support | — | — | Included |
FAQ
OCPP 1.6J and OCPP 2.0.1 over WebSocket, plus vendor MQTT for hardware that speaks its own protocol. Both OCPP versions connect to the same platform and share the same asset, tariff and settlement model, so a mixed estate does not need a second system.
Load limits are published as OCPP charging profiles, which means the charger itself holds and executes the schedule. A short network interruption therefore does not release the site limit. Profiles can be simulated first and every applied profile is recorded.
Peak, flat and valley periods are resolved against the station's timezone, falling back to the tenant's. Periods may cross midnight and are validated for overlaps and gaps before a tariff is published. A session snapshots the tariff it started under, so later price changes never rewrite an invoice.
Each tenant gets its own database rather than a shared table with a filter column. Platform and merchant sessions are issued separately with non-interchangeable tokens, and merchant views are scoped to that merchant's subtree. Enterprise deployments can run entirely inside your own infrastructure.
Cards, Apple Pay and Google Pay through Stripe; PayPal alongside it; and offline bank transfer with staff confirmation for fleets and markets where transfers are the norm. Amounts are stored in the smallest currency unit and every callback converges on one idempotent entry point.
Both. Drivers can install the PWA, use the H5 build in any browser, or install the native Android and iOS apps, all backed by the same account and the same session record.
Import stations, chargers and members, point the chargers at the platform's OCPP endpoint, and run a pilot site with production tariffs before cutting over. Existing tariffs are modelled as plans rather than hard-coded rates, so the pilot is a fair test of the real configuration.
Book a demo
Send us a station, its timezone and its tariff table. We will set it up in a demo tenant so you can walk a full session: authorise, charge, settle, refund, commission, reconcile. Then decide.
Demo environments are provisioned by a person, so expect a reply rather than an instant account.
Legal
The links below point at this section because the real documents do not exist in this repository. Replace them with your own pages before launch; nothing here is legal advice.