Your equipment. Your brand. Your platform.
Ship charging stations bundled with a complete CSMS under your own name - without a multi-year in-house build and without another vendor's logo in your customers' app. ChargeMeCar itself is one such brand on the platform: what you see on this site is what a brand deployment looks like.
Your customers have already decided they need a platform
Every charging-station buyer expects a cloud platform delivered alongside the equipment. The only open question is whose brand is on it.
Building in-house is a multi-year investment
A production CSMS needs several OCPP versions, OCPI roaming, payments, multi-operator architecture, a driver app and a compliance perimeter. The implemented volume of a single station protocol alone is estimated in the industry at 10-16 person-months - and a charging platform has some fifteen subsystems of that kind.
Third-party SaaS commoditises your product
When the driver sees another vendor's logo in the app, your equipment becomes an anonymous component of somebody else's service. Under your brand the platform is part of the product.
The software platform is a procurement criterion
Tenders increasingly ask for a mature CSMS story next to the equipment specification. "Our platform" is a stronger answer than "we integrate with a partner".
A complete CSMS, branded as yours
The full platform capability - station management, payments, roaming, billing, several operators, the end-user applications - deployed under your brand and configured for your market.
Every OCPP version
OCPP 1.5, 1.6 and 2.0.1 side by side with automatic translation. Sell new equipment without orphaning customers on older fleets.
OCPI roaming, hub-ready
OCPI 2.2.1 and 2.3.0 in both roles. The technical prerequisite for Hubject and Gireve is in place; the hub contract is your commercial step.
European payments
Stripe with Stripe Connect: money charged in the station owner's account, receipts in the owner's name, partner payouts, AFIR-compliant QR payment without registration. A pluggable provider layer lets a brand add a regional acquirer.
Several operators on one instance
Each of your customers gets an isolated operator - its own network, staff, data boundary. One deployment serves your whole customer base.
The end-user applications
Operator portal, driver web app, QR pay page, OAuth2 sign-in, a landing template - all rebranded per deployment through one manifest. Eight interface languages.
A built-in station simulator
Virtual stations across OCPP versions for development, testing and sales demonstrations. Present the platform without real hardware on the table.
Configuration, not customisation
Your logo, domain, colours, e-mail templates and legal entity apply across every user-facing surface through one brand manifest - edited in the portal, applied without a rebuild.
Works with any OCPP-compliant station - including a competitor's
The platform does not lock customers to your equipment. A buyer with a mixed fleet consolidates everything in one portal; the customer stays because of the service, and the next purchase is yours to win with hardware.
From a freshly provisioned server to a running platform in minutes
Each customer deployment is a brand repository created from a template. One command deploys the full stack, one updates it, one checks its health.
- 1
Create the brand repository
From the template: compose topology, install / update / check scripts, environment layout - pre-wired.
- 2
Configure
Per-environment settings (dev / stage / prod), a secrets loader with reference vault integrations, the brand licence and manifest.
- 3
Install
One command deploys the full stack onto a newly provisioned server, initialises the database, loads the licence and brings every service up with health checks.
- 4
Maintain
One command bumps the platform version with a rolling restart; another runs the health probes; a rollback returns the previous version with the same mechanics.
Three ways to ship the software
Pick the model that fits your business. All three are operational today and need no unusual legal structure.
Per-brand licence
For manufacturers who want full ownership of the deployment and the customer data.
A one-time licence per brand plus annual support. You operate the infrastructure; platform releases ship with migration notes.
Revenue-share partnership
For manufacturers who want to ship the platform with the equipment without an upfront investment.
The platform is operated by us under your brand. Charging revenue is shared. You focus on selling hardware.
Managed deployment
For manufacturers who want brand control without the operational burden.
The brand repository is yours, your brand is on every surface - hosting, updates and monitoring are ours.
What is included, what is on you
A clean boundary from day one, so everyone knows what they own.
- The full CSMS and periodic platform releases
- The branded end-user applications: portal, driver app, pay page, sign-in, landing template
- OCPP 1.5/1.6/2.0.1, OCPI roaming, Stripe and Stripe Connect
- Several operators on one instance with automatic provisioning
- Install, update and health-check tooling
- Technical support and migration documentation
- Commercial agreements with roaming hubs (Hubject, Gireve)
- Payment provider accounts (Stripe, plus any regional acquirer you enable)
- Infrastructure: cloud account, domains, TLS certificates, DNS
- Driver acquisition, marketing, commercial growth
- First-line support for your end users
There is a working brand on the platform already
ChargeMeCar is a European brand on the same platform: Stripe Connect settlements, AFIR ad-hoc QR payment, GDPR, roaming readiness. The build that runs this site is the build that ships to a manufacturer.
Let us talk specifics
A typical first conversation takes 45 minutes. We prepare a technical briefing for your station portfolio and target markets.
Request a technical briefing