OCPP network operations

OCPP CSMS software with protocol-level visibility

Sock8 connects OCPP chargers to a central system for status monitoring, transaction control, configuration, diagnostics, and commercial operations. Operators can move from the fleet view to the underlying protocol messages without changing tools.

Support for OCPP 1.6J and 2.0.1 is paired with a validation process for each charger model and firmware. That keeps interoperability claims grounded in tested flows rather than a logo list alone.

Plan Your Network Book a Technical Demo

Who it is for

Built for teams accountable for live charging.

CPO engineering and operations teams
Charger OEM integration teams
Networks moving from proprietary backends
Support teams diagnosing OCPP behaviour

Problems it solves

Replace operational blind spots with one system.

Opaque charger-to-backend communication
Firmware differences hidden behind an OCPP label
Long fault-resolution cycles
Protocol data disconnected from business sessions

How it works

A clear path from connection to daily operation.

Register the charge point

Create the charger identity and connect it securely to the assigned OCPP endpoint.

Validate core messages

Check BootNotification, Heartbeat, StatusNotification, Authorize, transaction, and MeterValues behaviour.

Map operations

Associate protocol identities with locations, connectors, tariffs, access rules, and users.

Monitor and diagnose

Follow live state, issue remote commands, and inspect raw requests and responses when behaviour diverges.

Product view

See the operating detail behind the promise.

The terminal ties raw charger messages to a specific unit and timestamp for faster OCPP diagnosis.

Representative Sock8 product interface

Features

Capabilities included in the product scope.

Live OCPP message stream
Request and response inspection
Remote command controls
Session and meter-value correlation
Model and firmware compatibility records
Exportable diagnostic history

Protocols and interfaces

Designed to connect the charging stack.

OCPP 1.6JOCPP 2.0.1WebSocket transportOCPI 2.2.1REST APIsWebhooks

Implementation or migration

Move from technical discovery to a controlled launch.

1
Protocol profile
Document the required OCPP version, security profile, messages, smart-charging needs, and vendor extensions.
2
Bench connection
Connect a representative unit or simulator and resolve identity, networking, and certificate requirements.
3
Transaction validation
Exercise authorization, start and stop, metering, offline recovery, resets, and error states.
4
Production onboarding
Approve the model and firmware profile, then onboard field units with operational monitoring.

Customer evidence

Mixed-brand network unified

6 wks to migrate · 400+ connectors

Echarge Moldova · Moldova

The migration brought more than 400 connectors from a legacy platform into one OCPP-based operating environment.

Evidence shown is limited to the named deployment facts currently approved for this site.

Deployment

Choose the operating boundary.

Run the CSMS as a managed cloud service under your brand or install it within customer-controlled infrastructure.

Pricing information

Scope the commercial model.

Managed pricing is based on active connectors. Private deployments are quoted for the agreed protocol, infrastructure, integration, and support scope.

View platform pricing

Buyer FAQs

Questions technical and commercial teams ask.

Does OCPP support guarantee charger compatibility?+

No. OCPP version support is the starting point; model, firmware, configuration, networking, and message behaviour still need validation.

Can we inspect raw OCPP messages?+

Yes. The charger terminal exposes timestamped requests and responses so support teams can trace a transaction or command.

Is OCPP 2.0.1 available?+

Yes. The exact 2.0.1 feature profile required by your charger and operating model is confirmed during discovery and testing.

Can Sock8 send remote commands?+

Yes, for commands supported by the connected charger profile, including common start, stop, reset, and availability operations.

How are vendor-specific messages handled?+

Required vendor extensions are reviewed during integration and included only when they are documented, testable, and part of the agreed scope.

Next step

Plan the software behind your charging network.