Skip to main content

At a glance

Pick Nexus if

You are a partner backend that needs to read the charging network — stations, chargers, connectors, and structured tariffs — and start or stop sessions on behalf of customers you already manage.

Pick FLO if

You are building fleet tooling: an operations dashboard, a driver app, or a backend-for-frontend. FLO adds the fleet concepts Nexus does not model — driver onboarding, a vehicle registry, connector-level charging restrictions, and fleet billing.
The two APIs are independent. Identifiers are not interchangeable between them, and a credential for one will not authenticate against another.