Any brand, one way of working
Every charger maps onto one model of your fleet, so the console and the API look the same whichever hardware you bought. Add a new brand next year and nothing about how you work changes.
Products
Connect chargers from any brand, share your site's power between the cars that need it, charge when energy is cheapest, and run all of it from one console and one API. One platform instead of three systems you keep in step.
Operate the fleet
Chargers from different brands and generations land in the same console and behave the same way. A mixed fleet is the normal case here, not a migration project.
Every charger maps onto one model of your fleet, so the console and the API look the same whichever hardware you bought. Add a new brand next year and nothing about how you work changes.
Start and stop sessions, restart, unlock a cable, take an outlet out of service, reserve, change settings and, on chargers that support it, update firmware. All remotely. A command sent to an offline charger waits for it, and every one ends with the charger's own answer, so you always know what happened.
Hold an outlet for a driver before they arrive, so the charger they were promised is free when they pull in.
Connections, outlet status, sessions and meter readings reach your screen the moment they happen. Every page keeps itself current, with nothing waiting on a refresh.
Set a project, a site or a single charger to Open, where any car can charge, or Private, where only the cards on its list can. Each charger follows the rule closest to it.
Status history for every charger and outlet, a list of the chargers stuck in a bad state, and diagnostic logs pulled on request from chargers that support it, so a fault gets looked at instead of guessed at.
Control the power
Draw your site the way it is wired, and Flowion moves current between chargers as demand shifts. That is the difference between upgrading a fuse and simply charging more cars.
Capacity, not conduit
Flowion treats your site's capacity as the shared, moving resource it is, and the price of filling it as something worth planning around.
It knows how your site is wired: a tree of circuits with real rated currents, so every decision is made against your actual switchgear.
It moves current to where the cars are. Headroom a finished car gives back goes straight to one that is still charging, without anyone touching anything.
It knows what tomorrow costs. Overnight parking is the cheapest energy a site will ever buy, and Flowion plans the charge into it.
Describe a site as a tree of circuits with their real rated currents. A layout that would overload your switchgear is refused when you save it, long before it could reach a charger.
Flowion keeps working out which cars want more current and which have some to give back, and shares each circuit's headroom between them. It scales down fast and up carefully, so the site stays within its limits.
Decide which cars get the amps when a circuit is full, per organization or per session, while a guaranteed minimum keeps every car charging.
Give a session an energy goal and the time the car leaves. Flowion plans the charge against tomorrow's prices and your supply contract, and puts it in the cheapest hours that still get the car there.
Define a tariff, version it and assign it to a project, a site, a charger or a single outlet, then read back what every session cost. Chargers that support it get the tariff too, so the driver sees the price at the plug.
Tomorrow's wholesale electricity prices are collected for you, per site or per project, so you can see what the next day costs before deciding when to charge.
Build on it
One REST API, generated from the code that serves it, with organizations, projects and access control built into the model from the start.
The API
The console runs on the same public API, with the same authentication, that you get. Nothing it shows is out of reach of your own systems.
A command is a record you can follow: it waits for an offline charger, ends with the charger's own answer, and a live event tells your code the moment that answer arrives.
The reference is generated from the code that serves each request, so it always matches what is running.
Browse the API referenceThe API reference is generated from the code that answers each request. If an endpoint is in the reference, it is live.
Charger, outlet and session events pushed to your endpoint as they happen. Signed, retried with backoff, kept in a delivery log you can replay from, with a signing secret you can rotate in place.
Organizations own projects, and projects own chargers. Every request is checked against real membership and role. Run a second brand or a client's fleet beside your own without touching the one that is charging cars.
Every charger connects over an encrypted connection, with a password or, where the charger supports one, its own certificate. Your team signs in with Google, GitHub or an email link instead of a password, and driver cards are stored encrypted with every reveal recorded.
Every project has a sandbox next to its live fleet, kept apart from it and never billed. Start virtual chargers there in one call and drive them through a whole session: plug in, charge, pause, fault, unplug.
The stream that keeps the console current is yours too. Subscribe from your own systems and hear about every change to a charger, a session or a meter reading as it happens.
Works with what you run
Flowion talks to your chargers, and to the other systems around them, so you don't have to.
Point a charger at Flowion with three settings and it is online. Our device catalogue shows, model by model, how each one connects.
Link a whole Easee site with one charger's serial number and PIN. Flowion imports how the site is wired, places its chargers on your circuits and connects each one.
Connect Fortnox from the integration directory with one consent on each side, and your Fortnox customers and articles are matched to your records.
For installers
Installers work on chargers that belong to someone else. Flowion gives that work its own access, scoped to exactly what the job needs.
A customer grants your organization access to their chargers and sites, and either of you can end it from the console at any time. Installer access is free.
Give each technician the customers they work for, so they see their own jobs and nobody else's fleet.
Installer access covers commissioning and diagnostics, and never reaches a customer's billing. One organization can be an operator and an installer at once.
Sign in and point a charger at your organization's address, or read the API reference first.