AmpNexus

OCPP Connect

A resilient OCPP backend for mixed hardware fleets

Connect and control chargers from multiple vendors and OCPP versions through a single, hardened backend and one clean API.

OCPP Connect

One backend for every charger you run

Running mixed hardware across sites and countries means juggling different OCPP versions, firmware quirks and network conditions. AmpNexus abstracts that complexity so you onboard chargers faster, keep sessions stable and expose one consistent API to the rest of your stack.

Multi-version support

Run OCPP 1.6 through 2.1 side-by-side on one backend — modernise hardware on your schedule, not with a big-bang migration.

Resilient event handling

Handle out-of-order messages, intermittent connectivity and retries without losing session data or commands.

Live status

Connector availability and health in real time, streamed to your systems via webhooks or SSE.

Smart automation

Detect issues early and improve uptime with automation hooks into the rules engine.

Full event history

Boot, Status, Heartbeat, MeterValues and diagnostics retained for audit and root-cause analysis.

Future-ready

Built to evolve with new standards and compliance requirements as the protocol landscape moves.

Core capabilities

  • Charge point inventory with model, firmware and site metadata
  • Remote commands: start/stop, reset, unlock, change availability
  • Real-time connector availability and health
  • Complete OCPP message history for audit and troubleshooting
  • Automatic session recovery across connection drops
  • Consistent behaviour across vendors and firmware versions

Who it's for

OEMs & manufacturers

Standardise connectivity across your installed base.

Charge point operators

Run mixed hardware at scale with one backend of record.

Enterprises

Integrate EVSE into existing systems through a clean API.

API-first

Connect platform workflows to your systems

  • Charge point CRUD and metadata
  • Remote control actions (remoteStart, remoteStop, reset)
  • Real-time events via webhooks or Server-Sent Events
  • Full OCPP message history for audit and RCA
remote-start.sh
curl -X POST \
  https://api.ampnexus.co.uk/v1/chargepoints/cp-2481/remote-start \
  -H "Authorization: Bearer $TOKEN" \
  -d '{ "connectorId": 1, "idTag": "fleet-042" }'

# → 202 Accepted
# { "status": "Pending", "requestId": "req_8f31" }

Make every connection reliable

Onboard OCPP devices quickly, keep sessions stable, and control everything through one API.