Everything a CSMS needs to run a real fleet.
Flowion isn't just an OCPP endpoint. It speaks 1.6J, 2.0.1 and 2.1 to a mixed fleet, moves the site's power to the cars that need it, and exposes all of it through one multi-tenant API — a single platform, not three integrations glued together.
Operate the fleet
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
1.6J, 2.0.1 and 2.1 chargers all map onto one domain model, so the API and the console look the same whichever your hardware speaks. Each version keeps its own wire types underneath, so nothing is quietly validated against the wrong spec's field bounds.
Commands that answer back
Fifteen CSMS-initiated commands — reset, unlock, remote start and stop, availability, triggers, configuration and variables — each held open until the charger replies, so an operator sees what actually happened instead of a request that vanished.
Live, not polled
Connections, connector status, transaction lifecycle and meter values are pushed from the gateway to your browser the moment they happen. Every page keeps itself current; nothing sits on a refresh timer.
Control the power
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
Describe a site as a tree of circuits with real rated currents. The database itself refuses to store a tree that is oversubscribed, so a capacity mistake is caught before it can ever reach a charger.
Dynamic load balancing
Flowion works out continuously which connectors want more current and which have some to give back, then reallocates each circuit's headroom and pushes fresh charging profiles down to the chargers — scaling down fast and up carefully, because those are not the same risk.
Day-ahead prices, built in
Day-ahead electricity prices for all 73 ENTSO-E bidding zones, collected on a schedule and resolvable per site or per environment — so you can see what the next 24 hours cost before deciding when to charge.
Build on it
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
The OpenAPI document is generated from the handlers themselves and browsable in Swagger UI, so the reference can never drift from what is actually deployed.
Multi-tenant to the root
Organizations own environments, environments own chargers. Every request is authorized against real membership and role — never a tenant id the caller supplied. Run staging beside production without touching the fleet that is charging cars.
Secure by default
Chargers authenticate over TLS using OCPP Security Profile 2, operators sign in through an OIDC provider, and driver authorization tokens are stored encrypted with every reveal written to an audit trail.
Test without hardware
A built-in simulator drives boot, plug-in, authorize and charging flows against the real gateway, so you can exercise an integration — or load-test one — before a charger is on site.
Everything on this page runs today. What's specified and in flight lives on the roadmap — the two never blur.
Ready to bring your chargers online?
Sign in and point a charger at your organization's URL, or read the API reference first — the simulator is there for the days hardware isn't.