Skip to content
OCPP platform

OCPP compliant by default

Bring any OCPP charge point. Switch from any backend. Get OCPP auto-reset, AI-driven post-incident diagnosis, and a migration path that does not require per-charge point reconfiguration.

OCPP transparency

All of OCPP. None of the lock-in.

Every modern CPMS supports OCPP. That’s the baseline. At Monta, OCPP and our API are the core. What separates us is what you can do with your OCPP data.

Your logs, readable

The full OCPP stack is yours. Read every message in Monta. Pull every event through the API. Stream production data into your own warehouse via Snowflake. Some CPMS platforms lock OCPP data inside their backend, Monta hands you the keys.

Your configuration, editable

OCPP configuration keys are not buried in a support ticket. Edit one charge point or ten thousand. Adjust at the brand, model, or firmware level.

Your hardware, portable

OCPP keeps your charge points portable across backends. Stay on Monta because it is the best fit, not because you are locked in.

OCPP support

What Monta supports

If your charge point speaks OCPP, Monta works with it. Monta runs OCPP 1.6J and 2.0.1 in production. The Open Charge Alliance Core Profile is the floor. Your charge point can do more if it supports these OCPP extras:

SmartCharge 1

Smart Charging

for load balancing and dynamic power allocation. Any charge point that supports Smart Charging can load balance with any other on the same site, AC or DC.

3 layers

Firmware Management

for remote firmware upgrades over OCPP.

list

Local Auth List Management

for offline RFID approval when connectivity drops.

rocket

Remote Trigger

to request messages such as MeterValues on demand.

Hardware compatibility

Works with the hardware you actually have

Grid layout featuring various electric vehicle charge points from brands like Schneider Electric, Ampure, Easee, Siemens, Hardy Barth, and RolecEV, on a dark background.

If your hardware lacks one of these extras, Monta still runs the charge point. You lose only the matching capability.

  • Proprietary OCPP variants are not a deal-breaker. We extend our OCPP layer when needed.
  • Tested across hardware. Every Monta release is OCPP-tested. Every hardware firmware update gets re-tested. Monta publishes an OCPP toolkit and emulator used by manufacturers across the industry.

Read more about hardware compatibility

Switch backends without touching your hardware

capabilities

Beyond standard OCPP

OCPP gets your charge point to talk. Monta does the rest.

OCPP migration

Built for enterprise migration

Most operators discover the OCPP cutover the hard way. Each charge point has to be reconfigured with a new OCPP URL. Firmware versions mismatch. Logs from the old system are gone. Monta’s migration takes all three off your team’s plate.

  • Don’t touch your portal. Point your charge points to Monta’s proxy domain. Traffic forwards to your old backend or to us. Cut over in waves or all at once.
  • Cellular charge points? Just swap the SIM. Our SIM cards just work. No network lock-in, no messy VPNs. Pop them in and flip your OCPP URL.
  • No firmware surprises. We validate your firmware version with the manufacturer before cutover. If it needs updating, we do it over OCPP.
  • Logs from day one. Every OCPP message is readable in Monta Hub the moment your charge points connect.

Read EnviroSpark case study

EnviroSpark

EnviroSpark beat their migration target by five months. EnviroSpark projected 2,175 ports live on Monta by June 2026, a nine-month plan. They hit that target in January and had 2,965 ports live by March. The migration included new SIM cards, re-labelling, and firmware updates.

FAQs

Yes. Monta supports OCPP 1.6J and OCPP 2.0.1.

Yes. If your charge points support OCPP, you can move them to Monta without replacing hardware. Monta provisions pre-configured SIM cards that point to our OCPP endpoint, so you do not have to update the OCPP URL on each charge point one by one. We validate your firmware versions with the manufacturer before cutover. The OCPP cutover usually happens in a single coordinated swap.

Yes. OCPP logs are readable in Monta Hub for every connected charge point. For programmatic access, OCPP events and configuration are exposed through Monta’s API.

Monta requires the OCPP Core Profile defined by the Open Charge Alliance, which every OCPP-compliant charge point meets by default. To unlock the full operator toolkit, we recommend manufacturers also implement Smart Charging, Firmware Management, Local Auth List Management, and Remote Trigger.

Yes. Monta streams your production data into your own warehouse via Snowflake. Pull OCPP events, charge sessions, charge point health, and configuration data on your terms.

Native. Your charge points talk directly to Monta over OCPP, not through your hardware vendor’s cloud relay.

Move your charge points without changing hardware

We validate your firmware with the manufacturer, provision pre-configured SIMs, and make every OCPP message readable from day one.