---
updatedAt: 2026-09-21T08:34:19.000Z
---

Fetch the complete documentation index at: https://developer.easee.com/llms.txt. Use this file to discover all available pages before exploring further. Append .md to any documentation page URL to get its markdown version.

# OCPP Introduction

Overview of the (native) OCPP offering - currently in beta release.

<Callout icon="far fa-info" theme="info">
  ### Please ensure that your charger is running on firmware version >= 344.&#x20;
</Callout>

## OCPP Implementations in Easee

Easee offers two distinct implementations of OCPP 1.6J, each with its own operational model:

1. **Cloud-emulated OCPP**<br />Operation: The charger communicates with the Easee Cloud, which then interfaces with a 1.6J compatible back-office.
   Key feature: Proxied communication through Easee Cloud, allowing a higher level of support from Easee, more functionality.
2. **OCPP**<br />Operation: This is the native version where the charger communicates directly with a compatible 1.6J server / back-office.
   Key feature: No intermediary Easee Cloud proxy is required, meaning a lower level of support from Easee.

**Comparison**<br />Both implementations have their own set of advantages and disadvantages some of which are listed below.

| Feature                   | Cloud-Emulated OCPP            | OCPP   |
| :------------------------ | :----------------------------- | :----- |
| Latency                   | Slightly higher (due to proxy) | Lower  |
| Easee Cloud Dependency    | Yes                            | No     |
| Implementation Complexity | Lower                          | Higher |

Note: The benefits and drawbacks of each implementation may evolve as new features are added to OCPP.

## Future developments

As OCPP continues to evolve, we anticipate further enhancements to both implementations. Developers should stay updated with our documentation for the latest features and best practices.

## How to provide feedback to us

If you have any questions or would like to provide us with some feedback on our OCPP implementation please contact us via [Easee Connect](https://github.com/easee/connect) or via our [Support](https://support.easee.com/hc/en-gb/requests/new?ticket_form_id=5689810819217) form.

Note: Since the charger primarily connects to a server other than Easee Cloud, support is limited due to the reduced diagnostics and telemetry available. Therefore, [Easee Connect](https://github.com/easee/connect) is the primary support channel for our initial native OCPP offering.