About Emobi
Protocol-First. Operator-Built. Jacksonville, FL.
Emobi builds the integration layer between EV charging hardware and the operations stacks that manage it — covering OCPP protocol translation, NOC operations, and utility demand response in one API. We are not a full CPMS platform. We are the integration substrate that makes any CPMS work with any hardware.
Founding Story
Why We Built Emobi
Lin Sun Fa built his technical foundation managing infrastructure deployment projects across Southeast US charging corridor expansions — work where the limiting factor was never hardware availability but protocol fragmentation. ABB stations speaking one OCPP dialect, Kempower stations another, each requiring a custom connector before any meaningful network management was possible.
Emobi was incorporated in Jacksonville in 2024 around a specific thesis: the EV charging industry needs an integration layer that sits above the hardware and below the CPMS — handling the OCPP dialect differences, the utility protocol bridging, and the session data normalization that every operator currently builds themselves. That layer should be a commodity, not a bespoke project.
The company is angel-funded, working with early CPO and fleet customers across the US, and is not a managed service or a full charge management system. Emobi is the integration middleware — the part that makes everything else work together.
Mission
"Any OCPP charger. Any grid signal. Any ops stack. Through one API — without building connectors for every combination."
We measure success by OCPP connection time, integration hours saved per hardware onboarding, and demand response event compliance rates — not feature count or dashboard complexity.
Founded
Headquarters
Backed
Mission & Values
How We Work
Protocol-First Thinking
We read the spec and implement it. OCPP 1.6J and 2.0.1, OpenADR 2.0b VEN/VTN, OCPI 2.2.1 — at the message-level, not just the block diagram. That implementation depth is the difference between an integration that holds under load and one that fails when firmware versions diverge.
Operator-Centric Design
The people using this platform manage charging networks under real operational pressure — downtime costs, SLA commitments, driver complaints. Every product decision is evaluated against that context. We don't add features to signal sophistication.
Infrastructure-Grade Reliability
EVSE is physical infrastructure on public and commercial property. When a charger goes offline, a driver is stranded. We build the integration layer to the same uptime expectations — 99.7% SLA, sub-120ms OCPP command latency, and alerting that catches faults before the customer does.
The Team
Meet the People Behind Emobi
Talk to Us — Operator or Candidate
If you're a CPO or fleet operator evaluating integration middleware, we'll validate your hardware stack and walk you through the connection architecture. If you're an engineer with OCPP or distributed systems background looking to work on real charging infrastructure — we want to hear from you.