01
Profile the hardware
Document model, firmware, OCPP version, security settings, connectors, metering, commands, and vendor-specific behaviour.
Bundle hardware with a tested software stack
EV charging software for charger manufacturers
Sock8 helps charger manufacturers validate firmware against real OCPP flows and package their hardware with a branded CSMS, driver web app, payments, APIs, and optional native apps.
The OEM can define a repeatable reference configuration for each model and firmware version, then create separately branded buyer deployments under an agreed re-licensing and support model.
What this buyer needs
Outcomes the solution is designed around.
- Validate new firmware before customer rollout
- Sell chargers with a ready operating platform
- Give different buyers their own brand and environment
- Reduce one-off backend integration work for every project
What gets in the way
Operational and commercial friction to remove.
- OCPP support differing across firmware builds
- Customer acceptance depending on complete transaction flows
- Repeated branding and deployment work
- Unclear ownership of custom behaviour and buyer support
How it works
A buyer-specific path from scope to live operation.
02
Run protocol validation
Connect a representative unit and exercise boot, status, authorization, transaction, meter, remote-command, offline, and recovery flows.
03
Create the commercial bundle
Choose the CSMS, driver app, branding, payments, deployment, re-licensing, and support scope offered with the charger.
04
Repeat for buyers
Use the approved charger profile and deployment template while applying each customer's brand, market rules, and integrations.
Inside the platform
The operating detail behind the solution.
The OCPP terminal exposes firmware behaviour message by message, while approved profiles carry forward into buyer deployments.
Representative Sock8 product interface
Relevant products
Use the modules this buyer actually needs.
Compatibility validation
Record support by exact charger model, firmware, configuration, and required flow.
OCPP testing tool
Connect development units, inspect messages, run commands, and retain test evidence.
White-label platform
Bundle a branded CSMS and included driver web app with the hardware offer.
OCPP CSMS
Operate approved OCPP 1.6J and 2.0.1 profiles with raw message visibility.
Buyer integrations
Connect customer applications, support tools, and commercial workflows through APIs and webhooks.
Private deployment
Offer customer-controlled infrastructure when the buyer requires it.
OCPP 1.6JOCPP 2.0.1WebSocketTLSOCPI 2.2.1REST APIs
Implementation
Make ownership and acceptance clear before rollout.
- 1
OEM integration workshop
Agree supported models, firmware release process, OCPP profile, custom behaviour, test ownership, and commercial bundle.
- 2
Reference validation
Test representative hardware and document the approved configuration, known limitations, and required firmware fixes.
- 3
Buyer template
Prepare reusable platform, brand, deployment, documentation, and support inputs without treating every customer as identical.
- 4
Release governance
Retest material firmware changes before updating the approved profile or rolling them into customer networks.
Relevant evidence
12,000 connectors onboarded
Mixed-hardware operating evidence
Sock8's published platform footprint spans multiple charger brands and markets, supported by model- and firmware-level validation rather than a universal compatibility claim.
Deployment
Choose the right operating boundary.
Offer Sock8-managed white-label cloud for standard buyer projects or scope a customer-hosted deployment for buyers with private infrastructure requirements.
Pricing
Match cost to the buyer model.
OEM and re-licensing commercials depend on expected buyer volume, connector scale, separate environments, apps, integrations, hosting, and the division of first- and second-line support.
View platform pricingBuyer FAQs
Questions charger oems ask.
How is new charger firmware tested?+
A representative unit is connected to the OCPP test environment and exercised through boot, status, authorization, transactions, meter reporting, remote commands, offline recovery, resets, and required negative cases. The approved profile records the exact firmware version.
What OCPP versions are supported?+
Sock8 supports OCPP 1.6J and OCPP 2.0.1. The required functional profile and security configuration are confirmed for each model and firmware combination.
Can the software be bundled with hardware?+
Yes. An OEM can package the charger with a branded CSMS and driver web app, with optional native apps, payments, roaming, APIs, or private deployment.
Can every buyer receive separate branding?+
Yes, separate buyer deployments can apply each customer's approved domain, logo, colours, naming, and support details. Native app branding and store publishing are scoped separately.
Is multi-tenant re-licensing available?+
A re-licensing model can be agreed for defined customer environments and volumes. Tenant isolation, rights, commercial limits, branding, data responsibility, and support ownership must be set contractually; unlimited redistribution is not implied.
Is there an OCPP simulator or test tool?+
Sock8 provides a cloud-hosted OCPP testing tool for connecting development chargers, inspecting raw messages, triggering supported commands, and retaining test history for OCPP 1.6J and 2.0.1.
Can Sock8 integrate custom firmware behaviour?+
Documented vendor extensions or non-standard behaviour can be evaluated. Support is added only when it is necessary, testable, maintainable, and included in an agreed engineering and support scope.
Next step