01
Define the partner offer
Choose target buyers, modules, deployment models, branding, integrations, support boundaries, and commercial assumptions.
Package a charging platform into your offer
White-label EV charging software for resellers and technology partners
Sock8 lets technology partners deliver branded EV charging projects using an established CSMS, driver web app, OCPP layer, APIs, payments, and optional native apps.
Each partnership defines which modules can be re-licensed, how buyer environments are separated, who owns integrations and support, and how commercial limits change with customer and connector volume.
What this buyer needs
Outcomes the solution is designed around.
- Add EV charging capability without building the platform core
- Deliver separate customer brands from a repeatable base
- Integrate charging into an existing technology offer
- Define support and commercial ownership before scaling
What gets in the way
Operational and commercial friction to remove.
- Long build time for a reliable OCPP backend
- Every buyer asking for different branding and integrations
- Unclear redistribution and support rights
- Custom delivery work eroding partner margins
How it works
A buyer-specific path from scope to live operation.
02
Build the reference package
Prepare the reusable platform configuration, customer intake, technical checklist, and acceptance plan.
03
Launch a first buyer
Validate the complete sales-to-handover process with one representative customer deployment.
04
Scale with governance
Reuse approved elements while scoping each buyer's brand, market, hardware, integration, data, and support differences.
Inside the platform
The operating detail behind the solution.
A shared platform core can connect partner applications and interoperability services while each approved buyer keeps its own operating identity.
Representative Sock8 product interface
Relevant products
Use the modules this buyer actually needs.
White-label platform
Branded CSMS and driver web app with optional native applications.
Integration layer
APIs and webhooks for partner portals, apps, and workflows.
Hardware validation
Onboard buyer charger models through documented compatibility testing.
Flexible deployment
Offer managed cloud or scope customer-controlled infrastructure.
OCPP 1.6JOCPP 2.0.1OCPI 2.2.1REST APIsWebhooks
Implementation
Make ownership and acceptance clear before rollout.
- 1
Partnership design
Agree rights, markets, modules, commercial units, buyer ownership, data responsibility, and support tiers.
- 2
Reference solution
Configure the standard partner package, integration contract, buyer intake, and delivery documentation.
- 3
First-customer proof
Run a real deployment through hardware, branding, integrations, acceptance, and handover.
- 4
Repeatable delivery
Track buyer environments and volume while keeping custom work and release responsibilities explicit.
Relevant evidence
40 networks powered
Sock8 platform footprint
The existing platform model spans branded networks and multiple markets, providing a base for scoped partner delivery rather than an unbounded redistribution promise.
Deployment
Choose the right operating boundary.
Partners can lead with Sock8-managed branded environments or include customer-hosted deployment where the buyer and support model justify it.
Pricing
Match cost to the buyer model.
Partner pricing is custom and depends on buyer volume, active connectors, environments, modules, apps, integrations, hosting, and support responsibilities.
View platform pricingBuyer FAQs
Questions technology partners ask.
Can partners resell Sock8 under their own name?+
A white-label and re-licensing model can be agreed for defined markets, customers, environments, and volumes. Rights and limits must be explicit in the partnership agreement.
Can each customer have separate branding?+
Yes, approved buyer environments can use separate domains, logos, colours, naming, and support information.
Is there a multi-tenant model?+
Separate customer environments and partner operating views can be scoped. Isolation, administration, data responsibility, and commercial units are confirmed for the intended model.
Can Sock8 integrate with our existing platform?+
Yes, through agreed APIs, webhooks, identity, and data flows. Custom integration work is scoped from a defined system-of-record and failure-handling design.
Who supports the end customer?+
First- and second-line support ownership, escalation, service levels, charger-vendor coordination, and release responsibility are agreed before launch.
Next step