EVorada Sancho
Sancho is an independent device that fits inside your charger or sits at a central point on site. It keeps any OCPP-compliant charger online, connected to several backends at once, and ready for AFIR. Named after the most dependable sidekick in literature.
Battle-tested: born from running the Gaia Charge network, where it keeps uptime at 99.7%.
Early prototype shown. The final design may differ.
A charger that loses its network connection can’t authorise sessions or take payments, even when the hardware is fine. A Berkeley field study found only 73% of public fast chargers working, while operators reported 95–98% uptime.
Moving a fleet to a new CSMS takes weeks of planning and sometimes a site visit per charger. A charger tied to a single backend makes every migration, pilot, or provider change harder than it needs to be.
Most deployed chargers still speak OCPP 1.6, which sends everything over an unencrypted connection. Researchers have demonstrated man-in-the-middle and remote code execution attacks against it on production hardware.
Sancho sits between your charger and the outside world. Everything it does works with the charger you already have.
Two modems, each with its own eSIM. When one carrier has a bad day, the other takes over. When a carrier stops being the right choice, you switch providers remotely. Nobody drives to the site to swap a SIM card.
Each port is configured independently as a switch, a router, or a client. Use the site’s wired network as another failover path, or let Sancho route traffic for other equipment at the location.
Your charger connects to Sancho, and Sancho connects to as many CSMS backends as you need: billing on one, monitoring on another, a new provider in parallel with the old one during a migration. Chargers that speak OCPP 1.6 locally can appear upstream as OCPP 2.0.1 or 2.1, which adds TLS, security events, and signed firmware handling without new charger firmware.
Drive external displays with EVorada UI. The design, branding, and information shown to drivers are yours to define. Price display and ad-hoc payment flows cover what AFIR expects at public charging points.
Connect energy meters, actuators, battery storage, inverters, and other site hardware over Modbus using ModDef profiles, or directly through GPIO. Sancho exposes all of it through the OCPP Device Model, so any backend can manage it in a standardised, vendor-independent way.
Planning a backend migration, a connectivity fix, or an AFIR retrofit? Tell us about your site and we’ll tell you whether Sancho fits.
Send InquirySancho works with any OCPP-compliant charger and can be retrofitted into equipment that is already in the field. Chargers running EVerest get a native integration.
Native integration with chargers running
Tested with chargers from
Trademarks belong to their respective owners. Listing indicates interoperability testing, not endorsement.
Get in touch for a technical overview or an evaluation unit. We’ll help you work out where Sancho fits in your network.