OCPP 1.6J · 2.0.1 · 2.1
Charging infrastructure, made easy.
One CSMS that speaks every version of OCPP to every charger you own — then balances the load across your grid connection, watches tomorrow's electricity prices, and shows you all of it live.
Any OCPP-J charger, any vendor. Free while your fleet is small.
A mixed fleet is the normal case
Chargers bought three years apart rarely speak the same protocol version. All three connect here, and behave the same once they do.
OCPP 1.6J
- Core, Remote Trigger and Smart Charging profiles, plus local authorization lists — built against the OCA Compliance Test Tool's bar rather than the spec's happy path.
OCPP 2.0.1
- Boot, authorization, transactions, meter values and the full device model, over 2.0.1's own schemas and its own generated types — never 1.6's, reshaped.
OCPP 2.1
- Every in-scope CSMS-initiated command, plus transaction limits: cap a session by energy, time or state of charge, and resume it across a station reset.
- 3
protocol versions, one domain model
- 15
commands held open until the charger answers
- 73
bidding zones of day-ahead energy prices
- 0
refresh timers — every update is pushed
Everything it takes to run a charging network
Connectivity, power, and an API — built as one platform rather than three integrations you maintain.
Every charger, every session, in one place
Chargers connect over OCPP 1.6J, 2.0.1 or 2.1 and land in the same console. A mixed fleet is the normal case here, not a migration project.
- Three protocol versions, one model
- Commands that answer back
- Live, not polled
Fit more cars onto the grid connection you already have
Model a site the way it is actually wired, then let Flowion move current between chargers as demand shifts — the difference between queueing cars and upgrading a fuse.
- Sites and circuits, wired as they are
- Dynamic load balancing
- Day-ahead prices, built in
A platform your own systems can talk to
One REST API, generated from the code that serves it, with tenancy and access control built into the model rather than bolted on afterwards.
- Code-first REST API
- Multi-tenant to the root
- Secure by default
- Test without hardware
The cheapest grid connection is the one you never have to upgrade
Most sites run out of amps long before they run out of parking spaces. Flowion treats the site's capacity as the shared, moving resource it actually is — and treats the price of filling it as something worth planning around.
It knows how the site is wired
A circuit tree with real rated currents, enforced in the database — so the platform is reasoning about your actual switchgear, not a number someone typed into a charger's config once.
It moves current where the cars are
Demand is re-inferred continuously from live meter readings and transaction state. Headroom a finished car gives back is handed to a car still charging, without an operator touching anything.
It knows what tomorrow costs
Day-ahead prices for all 73 ENTSO-E bidding zones, per site or per environment. Overnight dwell time is the cheapest energy you will ever buy — this is what lets you see it coming.
Integrate in an afternoon
A charger is one URL away from being live, and everything the console can do, your code can do — same API, same auth, same answers.
Answers, not acknowledgements
Every command endpoint holds the request open until the charger replies. The JSON you get back is the charger's answer — not a job id to poll while you wonder.
A reference that can't drift
The OpenAPI document is generated from the handlers that serve it and browsable in Swagger UI. If it's in the reference, it's deployed; if it's deployed, it's in the reference.
A fleet before you own one
The built-in simulator boots, authorizes and charges against the real gateway — so your integration, dashboards and alerts are proven before a charger is on site.
# 1 · point any OCPP-J charger at your fleet's URLbackend url wss://gateway.flowion.io/ocpp/acme/lot-3-north# 2 · it boots, authorizes, and appears live→ [2,"81f0","BootNotification",{"chargePointVendor":"Garo",…}]← [3,"81f0",{"status":"Accepted","interval":300,…}]# 3 · drive it from your own code$ curl -X POST api.flowion.io/v1/chargers/lot-3-north/commands/remote-start \-H "Authorization: Bearer $TOKEN" -d '{"idTag":"driver-042"}'{"status":"Accepted"} # the charger's answer, not a queue's
One place your whole team can work from
Not a status page bolted onto an API. Field technicians, support staff and engineers get the same live view of the fleet, scoped to the environments each of them is allowed to see.
Because updates are pushed rather than polled, what is on screen is what the charger is doing — including while you watch a session start.
- Fleet health across an environment
- Charger detail, with its live device model
- Sessions, with meter values charted
- Command history and outcomes
- Sites, circuits and their live load
- Driver authorization tokens
- Day-ahead energy prices
- Members, roles and environment access
What we're building next
Everything above runs today. These are specified and in flight — worth knowing about before you pick a platform to grow into.
Tariffs and cost reporting
What a session cost, per driver and per site.
Reservations
Hold an EVSE for a driver before they arrive.
Price-optimized charging
Shift charging into the cheap hours the forecast already shows you.
Priority allocation
Decide which cars get the amps when a circuit is full.
Firmware and certificates
Roll updates and rotate charger credentials from the console.
Outbound webhooks
Push fleet events into your own systems as they happen.
Single sign-on
Bring your own identity provider for operator logins.
Smart charging profiles
Author and push charging schedules from the console, per charger or per site.
The cable is becoming the interface
Charging is moving past RFID cards and apps: the car itself will negotiate identity, energy and price the moment it's plugged in — and give energy back when the grid pays for it.
ISO 15118
The standard that lets the car do the talking: identity, certificates and charging schedules negotiated over the cable itself, not typed into an app.
Plug & Charge
Drivers plug in and walk away. The car presents its own contract certificate — no RFID cards to ship, no app to support, no payment terminal to maintain.
Vehicle-to-grid
A parked fleet is a power plant. OCPP 2.1's bidirectional power transfer and DER control are how chargers will sell energy back in the expensive hours the price forecast already shows you.
The rails already exist: Flowion speaks OCPP 2.1 — the protocol version built to carry ISO 15118-20 and two-way power — to chargers today. These three land on infrastructure that runs, not on a rewrite.
Connect your first charger today.
Point a charger at Flowion and watch it boot, authorize and charge — or drive the whole flow with the built-in simulator before any hardware ships.
Any OCPP-J charger, any vendor. Free while your fleet is small.