Ship charging stations bundled with a full CSMS under your own brand. Avoid the three-year in-house build. Retain the direct relationship with the end customer.
A production CSMS requires multi-version OCPP, OCPI roaming, payments, multi-tenant architecture, a driver application, an administrative portal, regulatory compliance, and operational processes. For an equipment manufacturer, that is undifferentiated investment in someone else's problem.
When the driver sees another vendor's logo in the application, your equipment becomes an anonymous component of someone else's ecosystem. White-labelling preserves the direct customer relationship — and the cost of switching suppliers.
Tenders increasingly require a mature CSMS story alongside the equipment specification. A reference to 'our partner ecosystem' in a commercial proposal no longer closes deals.
OCPP 1.5 + 1.6 + 2.0.1 side by side with automatic translation. Sell new equipment without orphaning customers who still operate previous-generation fleets.
Full OCPI 2.2 and 2.3 with adaptive serialization. Hubject and Gireve integration. Your branded platform plugs into existing European roaming.
Stripe with Stripe Connect for automated partner payouts, driver wallet with automatic top-up, AFIR-compliant ad-hoc QR payment for public 50kW+ chargers. The platform uses a registry-based provider abstraction that accommodates additional providers on request.
Each of your customers gets an isolated tenant — its own network, employees, data boundary. One deployment can serve your entire customer base.
Admin webapp, driver PWA, QR pay mini-app, OAuth2 auth, landing template — all rebranded per deployment through configuration.
A set of virtual stations across OCPP versions for development, testing, and sales demonstrations. Present the product to a customer without shipping a physical charging station.
The platform does not lock customers to your equipment. A buyer with a mixed fleet can consolidate everything under your brand — which is often what closes the deal when procurement is leaving a previous CSMS lock-in.
gh repo create --template — brand repository pre-wired with compose topology, install / update / check scripts, per-environment structure.
Per-environment overrides (dev / stage / prod), secrets loader (five reference vault integrations), brand tokens, landing content.
./install.sh --env=prod deploys the full stack onto a newly provisioned server, initialises the database, loads seed data, and verifies service health.
./update.sh bumps the platform version with rolling restart. ./check.sh runs health probes. --rollback returns to the previous version if anything goes wrong.
For manufacturers requiring full ownership of the deployment and customer data.
One-time license per brand plus annual support. You operate the infrastructure. We ship platform releases with accompanying migration documentation.
For manufacturers wishing to ship the platform alongside the equipment with no upfront investment.
The platform is operated by us under your brand. Revenue from charging transactions is shared. You focus on selling equipment and closing customer deals.
For manufacturers seeking brand control without operational burden.
The brand repository is yours, your brand appears across every interface, but hosting, upgrades, and monitoring remain on our side.
ChargeMeCar is a European reference deployment on the same platform — AFIR-compliant QR payment in production at pay.chargemecar.com, Stripe integration live, OCPP multi-version fleet running. The deployment mechanics described above are exactly how ChargeMeCar was commissioned. It is the proof that the platform holds together end-to-end.
A typical first conversation lasts 45 minutes. We prepare a technical briefing tailored to your station portfolio, target geographies, and commercial model — substantive content, no generic presentation materials.