OCPP CSS — a live Central System to test your charging station against

Point your station at our server, open the console, send it OCPP commands. No registration, no sales call, nothing to install.

OCPP CSS (Central System as Service) is a production charging station management system. Its OCPP Central System is public: a sandbox tenant is open for anyone who needs a real counterpart for a charge point — firmware developers, integrators, QA engineers, or just someone who wants to see what their station says on the wire.

• OCPP 1.6-J and OCPP 2.0.1 over WebSocket, on the same endpoint — the version is detected from the messages your station sends. OCPP 1.5 (SOAP) on request.
• Live message log — every CALL / CALLRESULT / CALLERROR as it happens, both directions.
• Direct OCPP commands from the console: Reset, GetConfiguration, ChangeConfiguration, TriggerMessage, RemoteStart/StopTransaction, UnlockConnector, ChangeAvailability, ClearCache, DataTransfer, ReserveNow, CancelReservation, SetChargingProfile, ClearChargingProfile, GetCompositeSchedule, GetDiagnostics, UpdateFirmware, SendLocalList, GetLocalListVersion; for 2.0.1 also GetBaseReport, GetReport, GetVariables, SetVariables, RequestStart/StopTransaction.
• A driver app and an operator portal behind the same station, so you can run a full Authorize → StartTransaction → MeterValues → StopTransaction cycle the way it happens in the field, not just a BootNotification.

Connect your station — three steps

1. Set the Central System URL in your station

wss://ws.ocpp-css.com/ocpp/info/<station-id>

Field in the station settings	Value
Server (host)	ws.ocpp-css.com
Port	443 for wss · 80 for plain ws (stations without TLS)
Path	/ocpp/info/<station-id>
Charge Point Identity	<station-id> — must equal the last path segment

info is the sandbox tenant; <station-id> is anything you choose — the serial number is the usual pick. Case matters. No password is required in the sandbox.

Save, reboot the station. When its BootNotification arrives, the station is created automatically — there is nothing to pre-register.

2. Open the console

https://ocpp.ocpp-css.com — sign in as operator / operator.

Your station is in the list, with its connectors and their live status. Open it: the message log streams in real time, and the command panel lists every OCPP command the server can send, each with a form generated from the OCPP schema.

3. Send commands, watch the answers

Pick a command, fill the fields, send. The station's response — or its CALLERROR — appears in the log next to the request. Swagger for the same operations over REST: https://ocpp.ocpp-css.com/docs/ (health check: GET https://ocpp.ocpp-css.com/api/v1/ping).

Run a real charging session

The sandbox is not only a message echo. Behind the station there is a tenant with an operator and a driver, so the transaction path works end to end:

Role	Where	Login
Operator — station map, sessions, tariffs, remote commands	https://cloud.ocpp-css.com	operator / operator
Driver — start / stop charging, session history, RFID tags	https://driver.ocpp-css.com	driver / driver

For Authorize and StartTransaction take an idTag from the driver app (RFID tags), or start the session from the app and let the server send RemoteStartTransaction to your station. MeterValues you report show up in the session as it runs.

Platform REST API (sessions, stations, tariffs — everything the portal does): https://api.ocpp-css.com/docs/, same operator / operator.

Sandbox rules

• Shared and public. Everyone signed in as operator sees every station under info. Do not connect production stations or put anything personal there.
• Not persistent. Stations, sessions and logs in the sandbox may be wiped at any time.
• Fair use. One or two stations per developer is what it is for; a fleet, a load test or a 1-second MeterValues interval is not.
• One connection per station. OCPP-J allows a station a single WebSocket to the Central System, so a new connection on a station's path is taken as that station reconnecting — and the one already open is closed. Do not point a health check, watchdog or monitoring probe at /ocpp/...: every probe knocks your own station offline and it comes back with a fresh BootNotification. To check that the server is up, use GET https://ocpp.ocpp-css.com/api/v1/ping.

When the sandbox is not enough

Your own tenant — free. Sign up at https://cloud.ocpp-css.com (email + password, about a minute). You get a private URL of the form wss://ws.ocpp-css.com/ocpp/<your-login>/<station-id>, your own stations, drivers, tariffs and OCPP log — invisible to anyone else. Up to three stations cost nothing.

Your own server. The Central System is open source and runs as a single container:

docker run -p 9220:9220 --rm --name cs apostoldevel/cs

Source, docs and the OCPP schema files: https://github.com/apostoldevel/apostol-cs.

Your own operation. OCPP CSS is a full CSMS: station owners run a private fleet or take payments from drivers, with the money settled directly to the owner's bank account and the platform charging a per-receipt fee — no subscription, no per-port fee. Details and pricing: https://ocpp-css.com · Russian: https://ocpp-css.ru.

Contact

Found a station that misbehaves against the server, or the server against the station? Tell us — that is exactly what the sandbox is for.

support@ocpp-css.com