Founding Partners Wanted: Run Your EV Charging Network on a Self-Hosted OCPP + OCPI Platform

Most EV charging software stops at "connect a charger." The hard part starts after that: who pays, who owns the charger, who else’s network your drivers can roam onto, and who picks up the phone when a connector faults at 8 PM.

We built the Simplico Charging Platform to cover all of it in one self-hosted system. It is running today, and we are now opening a founding-partner program for the first operators who want to deploy it on their own network.

This post explains what you would actually be getting, what is not included, and how to join.

Who the founding-partner program is for

You are a good fit if you are one of these:

• A property owner or operator (condominium, resort, serviced apartment, shopping centre) who wants chargers under your own brand and your own payment flow.
• A fleet or depot operator that needs session data, remote control, and reporting without sending it to a foreign SaaS.
• An EV hardware reseller or installer who wants to hand clients a working platform with the hardware, not a PDF of integration instructions.
• A company with sites in Thailand or Southeast Asia whose head office, auditors, or customers care where charging data lives.
• An existing operator unhappy with a platform that bills in USD, has no local support, or shows someone else’s logo to your customers.

What is live today

Everything in this section is running now. The setup guide and demo are public, so you can check it before you talk to us.

One network, four audiences.

• Operators get a live operations dashboard: active sessions, faulted connectors, today’s revenue, fleet management for stations, connectors, vehicles, users and RFID tags, remote start and stop, payment history and an audit log.
• EV drivers scan a QR code at the charger and charge from a mobile web page. There is nothing to install. They can set a spend limit, watch live energy and cost, and find nearby chargers, including partner networks.
• Charge point owners (whoever physically hosts the charger) get a lightweight owner app that logs in with the same credential already on the charger. They see live status and revenue, set the rate per kWh, and hide a connector for maintenance.
• Roaming partners connect through OCPI 2.2.1, in both the CPO and eMSP roles, with Locations, Tariffs, Tokens, Sessions, CDRs and Commands. Session and CDR data goes through a retrying outbox so billing data is not lost.

Protocols. OCPP 1.6J is the production baseline. OCPP 2.0.1 is available as an upgrade path for new deployments.

Thai payment rails. QR30, PromptPay and 2C2P are part of the payment layer, with receipt generation and reconciliation exports.

A clean architecture. The charger-facing OCPP WebSocket layer is separated from the REST API, and all services share one MongoDB. Your dashboard, mobile app and third-party systems talk to HTTP, never directly to the charger socket.

flowchart TD
    A["Charge points - OCPP 1.6 and 2.0.1"] --> B["OCPP WebSocket service"]
    B --> M[("MongoDB shared by all services")]
    D["Operator dashboard"] --> M
    F["FastAPI - driver actions"] --> M
    O["OCPI service - CPO and eMSP"] --> M
    P["Roaming partners - OCPI 2.2.1"] --> O
    D --> B
    O --> B

You can see the screens, the architecture and the feature list on the Charging Platform page, and walk a real or simulated charge point through the public setup guide without signing up for anything.

What is not included, so you can plan around it

We would rather you hear this from us before you sign than discover it in week three.

• OCPP 2.0.1 and ISO 15118 Plug and Charge are an upgrade path, scoped per project. They are not the default deployment.
• The public demo is for evaluation only. Its data can be reset. If you need a stable environment to test your own hardware, ask for a dedicated evaluation environment.
• Charger compatibility is by protocol, not by brand list. Anything that speaks OCPP 1.6J should connect, and we have run sessions against several brands, but we test your specific model during commissioning rather than promising it in advance.
• Roadmap items are marked as roadmap in your proposal. We do not sell features that do not exist yet as if they do.

What founding partners get

• A scoped proposal within 48 hours of telling us your site, charger count and timeline.
• Priority onboarding for your first sites.
• A direct line to the engineers who built the platform, in Bangkok time, by LINE, WhatsApp, phone or email.
• A say in the roadmap. What we build next is shaped by the first operators who run it.
• Your brand on the platform. Your logo, colors and domain, with Simplico in the background.

Commercial terms for founding partners are agreed with you in the proposal. Standard package pricing is published on the EV CSMS page if you want a reference point first.

How to join

1. Look first. Open the setup guide or read the practical demo guide to see it working on a real charger.
2. Tell us three things: your site, how many charge points, and when you want to be live.
3. Get a scoped proposal in 48 hours, then decide.

Email us to become a founding partner

Prefer chat? LINE: iiitum1984, WhatsApp: +66 83 001 0222, or call +66 97 496 6397.

FAQ

Is this a SaaS I rent, or something I run myself?
It is self-hosted: you can run it under your own brand and domain, and we can manage the hosting for you. Hosting options and instance type depend on the package, and we scope that with you in the proposal.

Which chargers does it work with?
Any charger that supports OCPP 1.6J over WebSocket. We validate your exact model during commissioning.

Do I need to build a mobile app?
No. Drivers charge from a QR-opened web page. A branded mobile app is optional.

Can drivers roam onto other networks?
Yes, through OCPI 2.2.1 with partner networks you connect. Roaming works once both sides complete the OCPI Credentials handshake.

Is there a fixed founding-partner discount?
We do not publish one. Terms are scoped per partner in the proposal. Standard packages are on the EV CSMS page.

How long does deployment take?
A hosted onboarding for up to 20 chargers typically takes 1 to 2 weeks. A full white-label deployment with payment integration usually takes 4 to 8 weeks, depending on scope.

Where does the data live?
In Thailand by default, with a PDPA Data Processing Agreement available on Platform-tier engagements.