Supply the brand kit
Provide approved logo, colours, naming, domain, support contacts, and store assets where applicable.
Offer a branded charging management platform and driver web app alongside your chargers. Sock8 applies your domain, logo, colours, and support details across the operator and driver experience.
Start by reviewing your charger models, market, and project requirements with our team. The driver web app is included in white-label cloud; native apps, new payment integrations, and regional requirements are scoped separately before rollout.
Provide approved logo, colours, naming, domain, support contacts, and store assets where applicable.
Set registration, access, tariff, payment, receipt, and support flows for the target market.
Validate operator and driver experiences in a branded staging environment.
Launch the custom domain first, then publish optional native apps through the agreed store accounts.
The branded driver experience and CSMS share the same live session, tariff, and payment records.
Representative Sock8 product interface
Confirm brand assets, product naming, domain ownership, customer support, and legal text.
Apply the identity to operator and driver surfaces and configure market-specific journeys.
Test representative devices, chargers, payment outcomes, email content, and support links.
Move the web experience to production and complete optional app-store submission work.
The network launched with a branded platform, driver apps, and a local payment-gateway integration.
Evidence shown is limited to the named deployment facts currently approved for this site.
White-label cloud is Sock8-managed. Customer-hosted licensing is also available when infrastructure control is a requirement.
White-label cloud onboarding is $3,000 plus $10 per active connector per month. Native apps and custom integrations are optional quoted items.
View platform pricingThe offer includes the branded CSMS, driver web app, custom domain setup, and core charging operations.
No. Native apps and their store-publishing work are optional add-ons; the branded driver web app is included.
Yes, subject to gateway API availability, market requirements, and a validated integration scope.
Your approved brand is presented to users. Commercial ownership and data responsibilities are documented in the deployment agreement.
A straightforward managed setup can target seven days after required brand, domain, charger, and gateway inputs are ready; custom integrations extend the schedule.
Share your charger manufacturer, model and firmware where known, connector count, target country, payment gateway, and intended launch date. We use these details to assess compatibility and define a deployment scope before quoting.
A staged rollout can begin with representative chargers and agreed acceptance checks. Any pilot's price, duration, support, payment flows, and production transition are defined in a written proposal before work starts.