Partnership

Who It Is For

• Site owners, property managers, campuses and commercial complexes with chargers already purchased
• Operators with a growing charger fleet whose current platform underperforms
• Individuals or enterprises operating self-built chargers who need billing and app capabilities

Core Value

• No hardware replacement — connect your existing chargers and protect your investment
• Dual-protocol support for OCPP 1.6 and 2.0.1 — most mainstream chargers are connectable
• Full operational capabilities after onboarding: app QR-code charging, online payment, order management, remote monitoring and fault alerts

Onboarding Process

1. Protocol Verification Confirm whether the charger supports OCPP 1.6 or 2.0.1, and verify WebSocket URL, Charge Point Identity, TLS / security configuration and other parameters.
2. Integration Testing Complete core message testing in a sandbox: BootNotification, Heartbeat, authorization, start/stop charging and status reporting.
3. Configuration & Launch Push platform address and credentials, then configure sites, connectors, tariffs and payment methods once chargers are online.
4. Operational Handover Activate operating accounts and configure app presentation, pricing strategy and revenue settlement.

Before You Start

• "OCPP support" does not mean "plug-and-play": some vendors implement the protocol incompletely (e.g. TransactionEvent or the device model in 2.0.1) — integration testing is required.
• Older chargers may not support TLS or security profiles; we will assess whether basic authentication or a firmware upgrade is acceptable.
• Chargers with proprietary protocols need individual evaluation and may require adapter development.

Commercial Terms

• Onboarding / integration service fee (per connector or per project)
• Platform usage fee or revenue share
• Optional value-added services: agency operation and O&M hosting

Who It Is For

• Charger manufacturers and brands
• Vendors who want connected-device capabilities without building their own platform
• Manufacturers targeting overseas markets who need OCPP compliance and a mature management console

Core Value

• Platform connection pre-configured in firmware — end users are ready to go out of the box, reducing after-sales and integration costs
• App and console branding can be white-labeled to the manufacturer
• One platform carrying OCPP 1.6 / 2.0.1 — no need to build your own protocol stack or operating system
• Upgrade from "selling hardware" to "selling hardware + operating services"

Integration & Delivery Process

1. Protocol & Firmware Review Confirm the OCPP version (1.6 / 2.0.1), security profile and device-model completeness supported by production firmware.
2. Factory Configuration Preload the platform WebSocket URL, Charge Point Identity rules and certificates / keys into firmware or production configuration.
3. Production Line Testing Run smoke tests (BootNotification, heartbeat, authorization, start/stop) before shipping to guarantee "online out of the box".
4. Branding & UI Customization App name, logo, color scheme, domain and console branding white-labeled to your requirements.
5. After-sales & O&M Split Define fault ownership (hardware vs. platform), firmware upgrade channels and SLA boundaries.

Model Variants

• White-label model: the platform is presented under the manufacturer brand; the manufacturer owns the end customer while we provide the underlying support.
• Joint operation model: the manufacturer supplies devices and we supply the system, with revenue shared as agreed.
• Pure technology licensing: platform capability is embedded into the manufacturer's own service system, billed per device or per call.

Commercial Terms

• Per-unit shipment billing / annual licensing / revenue share
• White-label customization fee, dedicated deployment fee (e.g. private deployment)
• Ongoing maintenance responsibility for firmware upgrades and protocol compatibility