Emobi Platform
Every Layer of the Charging Stack. One Integration Plane.
OCPP 1.6J and 2.0.1 gateway, NOC-grade station operations, OpenADR 2.0b demand response, and pre-built connectors for 40+ EVSE hardware models. Emobi is not a charge management system — it is the integration layer that makes your CPMS, billing platform, and telematics software all speak to the same charging infrastructure.
Core Modules
Four Modules. Complete Coverage.
Each module targets a distinct integration bottleneck: protocol fragmentation, operational visibility, grid connectivity, and external system interoperability. Used together or independently via the REST API.
OCPP Management
Unified WebSocket gateway for OCPP 1.6J and 2.0.1, running simultaneously on the same network. Firmware version differences are abstracted — your operations software sees one normalized event model regardless of hardware vendor.
Network Operations
Live station health heatmaps, session monitoring, and auto-remediation playbooks for common OCPP fault codes. Triage is built in — your NOC team sees actionable alerts, not raw error strings from seven different firmware versions.
Energy Management
OpenADR 2.0b VEN implementation for utility demand response, TOU rate-window scheduling via OCPP smart charging profiles, and carbon intensity reporting against WattTime or Electricity Maps data. Grid-responsive charging without writing a single line of ADR protocol code.
Integrations
Pre-built connectors for fleet telematics (Geotab, Samsara), billing platforms (Stripe, SAP), OCPI 2.2.1 roaming, and utility APIs. Standard REST API and webhooks for everything else. No custom middleware required between Emobi and your existing stack.
Protocol Coverage
Every Major EV Charging Standard
Emobi implements the protocol stack required for modern CPO and fleet operations — from OCPP station control to OpenADR grid response to OCPI roaming settlement. Not wrappers around other vendors' APIs — native protocol implementations built and maintained by Emobi's engineering team.
OCPP 1.6J
Full support for core OCPP 1.6J operations: boot notification, heartbeat, remote start/stop, meter values, firmware update, and diagnostics.
OCPP 2.0.1
Smart charging profiles, ISO 15118 device model, security extensions, and display messaging — the full OCPP 2.0.1 feature set required by CCS Combo and NACS-capable charger hardware entering commercial deployment.
OCPI Roaming
Cross-network roaming settlement, session authorization, and tariff exchange via OCPI 2.2.1 — enabling your network to accept roaming drivers.
OpenADR 2.0b
Demand response signal processing for VEN/VTN communication. Schedule load shed events and report compliance back to utilities automatically.
ISO 15118
Plug-and-charge vehicle authentication via ISO 15118-2 and 15118-20, enabling automatic billing without driver app interaction.
REST API
Full REST API plus webhooks for all platform events. Python, Node.js, and Java SDKs available. OpenAPI 3.0 spec for your team to build against.
Architecture
Designed for Production at Scale
Emobi's integration layer sits between your hardware and your operations software — handling all protocol translation, state management, and event delivery.
Event-Driven Core
All OCPP messages and state changes emit events via webhooks or streaming API. Build real-time dashboards and alerting without polling.
Built with Security Controls
TLS 1.3 for all OCPP WebSocket connections. API key + OAuth 2.0. Role-based access control for multi-tenant network operators.
Scales With Your Network
Horizontal scaling handles hundreds of simultaneous OCPP connections. The same API works for a 50-station pilot and a 5,000-station rollout.
See the Protocol Layer Working on Your Hardware
Book a 30-minute technical walkthrough. Bring your hardware vendor list — we'll run through OCPP compatibility, show you your specific integration architecture, and configure a test OCPP endpoint live on the call.