White-Label CMS for Charger OEMs and CPOs

Multi-tenant architecture so different customers of yours each have their own operator dashboard, drivers, billing and reporting, all running on one codebase you control. Operator branding at every touchpoint: dashboard, driver app, invoices, receipts, notifications.

Deployment on your cloud, source code in your repo, IP transferred to you on payment. No ongoing per-charger fees. Your customers pay you; you don't pay a vendor a percentage of that revenue.

Bundle the platform with your hardware at a higher price point, capturing more of the total contract value. Sell the platform as a standalone subscription that your reseller partners deploy on their own accounts. License the platform to franchise operators who pay you per-charger and keep their end-customer revenue.

Which model wins depends on your channel. What the platform makes possible is charging your customers for software, instead of paying someone else to.

Typical build: 16-24 weeks to a production-ready platform with multi-tenant OCPP core, driver app, operator dashboard, billing engine and tariff manager. Additional modules, advanced fleet management, roaming via OCPI, load management, added in parallel or after launch. Pricing scales with module count, not with charger count.

Once shipped, per-charger cost drops to near zero and stays there. The build-to-spec economics inflect past 300-500 chargers; white-label OEMs typically break even in year one on their own volume, then profit on every charger and every partner deployment after.

• Source-code ownership on delivery
• Cloud ownership on the buyer's account, not the vendor's
• Branding rights across app, dashboard, invoices and driver-facing surfaces
• Full data export rights, in structured formats, at any time
• No hidden per-charger, per-session or per-transaction fees

• OCPP core with 1.6J and 2.0.1 support
• Driver mobile app (Android, iOS, PWA) with branding hooks
• Operator dashboard with role-based admin
• Tariff and pricing management
• Billing, wallets and settlement
• Notifications (SMS, email, push, WhatsApp)
• Reporting and finance exports
• Support tooling for the operator's help desk

• Poor tenant isolation between the vendor's customers
• Weak branding depth (colors change but UX still reads as the vendor's)
• No clean upgrade path when core versions bump
• Vendor-controlled hosting the buyer cannot audit
• Unclear IP handover terms in the contract