Flowion

About Flowion

Flowion exists because charging infrastructure deserves better than the market was offering.

Why we started Flowion#

After years working in e-mobility, I kept running into the same problem from a different angle every time: the software behind EV charging infrastructure was falling short of what the hardware — and the people relying on it — actually needed. Poor reliability, features that only made sense for the largest operators, platforms that treated charging stations as an afterthought rather than the core of the product.

I decided to take matters into my own hands and build the platform I thought the industry deserved: one built from the ground up for quality and reliability, where a charging network actually behaves the way its operator expects it to.

I believe the features that matter most for a greener tomorrow — like dynamic load balancing and frequency-based load balancing — shouldn't be locked behind enterprise pricing or reserved for the operators with the biggest fleets. They should be easily accessible to any company serious about running charging infrastructure well, regardless of size. That's the principle Flowion is built on.

I've been working in e-mobility since 2016, as a senior software engineer building the systems this industry runs on. Flowion is what that experience turned into.

— Joatin Granlund, CEO

What we believe#

  • Reliability isn't optional. A charging station that doesn't behave predictably isn't just an inconvenience — it undermines trust in electrification itself.
  • Advanced capabilities shouldn't be gated by company size. Dynamic load balancing, frequency-based load balancing, and the other tools that make a charging network genuinely efficient should be available to a five-charger site the same as a five-thousand-charger fleet.
  • Good infrastructure is quiet infrastructure. The best CSMS is one operators stop thinking about — because it just works.

What's next#

Flowion is under active development, built openly against the OCPP specification and real charger hardware, not a simplified subset of it. See our Products page for what's built today, or explore the API directly.