The platform that runs your chargers
A hosted, multi-tenant charging station management system. Any OCPP 1.6J or 2.0.1 charger connects to it, and from one dashboard you monitor every port, decide who charges and what they pay, manage site load, take Stripe payments and close the books, run fleets, and roam over OCPI. Load management per site, AI analytics for chargers, V2G, and OCPI roaming are paid modules, switched on per site on either plan.
Connect the chargers you already own
WattWisely speaks OCPP, the open protocol almost every charger on the market already supports. Point a unit at our endpoint and it appears in your dashboard — no proprietary gateway, no vendor tie, no rip-and-replace.
- OCPP 1.6J and OCPP 2.0.1
- AC and DC, single-port wallboxes to fast-charging islands
- Mixed-vendor sites managed as one network
- OCPI roaming, a paid module, so other networks can use your ports
- ISO 15118 on the vehicle side
What the platform does
Six jobs an operator has, and what the platform does for each. The paid modules, each switched on per site and quoted as its own line on either plan, are tagged where they sit.
Operate the network
The screen an operator leaves open all day, and the record that answers what happened when something went wrong.
- Real-time status with alerts on faults and disconnections
- Operation logs for every charger
- Fixed user roles, scoped per site, and new users created by you
- Single sign-on through third-party providers, LDAP, or Active Directory
Decide who charges and what they pay
Public, private, or both on the same hardware, with the price set the way the site needs it.
- RFID cards and app accounts, per site and per bay
- Tariffs by energy, by time, or per session, varied by site or user group
- Tariffs that follow nodal electricity prices, where available
- Charging timed against electricity prices and schedules
Share the power you have
The grid connection is the expensive part of a site. These keep you inside the one you have.
- Load management per site: dynamic load balancing across every charger on a connection Paid module
- V2G, vehicle-to-grid Paid module
- Utility control of site power through SCADA integration
Get paid and close the books
Nothing to invoice and nothing to chase, and the month closes from the numbers the network ran on.
- Stripe payments with automated withdrawals to your account
- Financial reporting and accounting built in
- Revenue share on public paid sessions only
Run a fleet on it
Fleet operations are part of the platform, not a separate product.
- An RFID card per vehicle, so every session is attributed
- Energy, time, and cost recorded per vehicle
- Taxis, buses, and delivery fleets on the same account as public sites
Plan maintenance from the data
AI over the operation logs, so maintenance is scheduled from what the chargers report rather than from driver complaints. This group is one paid module, AI analytics for chargers, switched on per site.
- AI analytics for chargers, over the operation logs Paid module
- Predictive-maintenance updates from the same analysis
- AI visualizations Part of the module
- AI reporting Part of the module
The hard parts, drawn
Three things every operator eventually asks about: the grid connection, who may see what, and where the money goes.
One limit, shared, never exceeded
A site gets a limit the connection can take. The platform divides it between the cars actually charging, and when one leaves its share goes to the rest. The utility can lower that limit over SCADA when the grid needs it.
- A site or circuit limit set once, in kW
- Power redistributed as cars arrive and leave
- Utility control of site power through SCADA integration
Everyone sees exactly their own scope
Tenants on the platform are isolated from each other. Inside a tenant, fixed user roles decide what each person may do: an operator who sees every site, a site manager who acts on one, a landlord who may only look. You create the users and give each one a role and a scope. Staff sign in with the login they already have.
- Fixed roles with set permissions, and as many users as you need
- Scoped per site, so a manager sees one building
- Single sign-on through third-party providers, LDAP, or Active Directory
Written once, used twice
A session is recorded with who charged, where, how much energy, how long, and what it cost. Stripe collects the payment and pays out to your account automatically. The same record is what the financial report is built from, so the month closes from the numbers the network ran on.
- Stripe payments with automated withdrawals
- Financial reporting and accounting from the session records
- Revenue share on public paid sessions only
Built to be built on
If you would rather drive the platform from your own systems — a property portal, a fleet tool, an internal dashboard — that is a supported path, not a special case.
The same API the dashboard runs on
There is no privileged internal interface. Every action the operator dashboard performs is a call to the documented REST API, which means anything you can do by hand you can automate. The API and developer program are part of the Enterprise plan.
- Chargers, sessions, tariffs, and users
- Start and stop sessions from your own front-end
- Webhooks for session and fault events
What technical buyers ask first
Will it work with the chargers I already have?
If they speak OCPP 1.6J or 2.0.1 — which almost all do — yes. You change the backend URL in the charger configuration and the unit appears in your dashboard. No hardware swap and no site visit in most cases.
Is there an API, and is it the real one?
Yes to both. The dashboard is built on the same REST API, which is available on the Enterprise plan, so anything the interface can do, your own code can do. Documentation is at api.wattwisely.com.
Can I run it on my own servers?
No. WattWisely is hosted and multi-tenant, which is what keeps it affordable to start and keeps everyone on the current version. If you need your own branding rather than your own servers, the white-label platform gives you that without the operational burden.
What happens if my internet connection goes down?
Chargers keep working. They hold their access rules and tariffs locally, continue sessions already running, and start new ones for known cards. When the connection returns, the sessions are uploaded and billed as normal.
Which roles are there?
The roles and their permissions are fixed; what you create are the users, and you decide which role and which sites each one gets. A landlord who only sees their building, a site manager who can act on it, and an operator who sees everything are three roles, not three accounts.
Which parts are paid modules?
Four: load management per site, AI analytics for chargers (visualizations and reporting), V2G, and OCPI roaming. Each is switched on per site and quoted as its own line, on either plan, so a ten-port site can add one without moving to Enterprise. White-label and SIM connectivity are add-ons, priced the same way. The REST API and developer program come with Enterprise. Request pricing and the quote lists the platform and each module as its own line.
Where is the data, and who can see it?
Traffic is encrypted in transit throughout. Card details are handled by Stripe and never touch our systems. One tenant cannot see, or affect, another tenant’s sites. Drivers’ data can be exported and erased on request, because the platform is built to be operated under GDPR.
How many sites can one account manage?
The platform is multi-tenant and multi-site by design — one login covers everything you operate, with roles so each person sees only their own sites. There is no separate instance to buy per location.
See it running on your own chargers
Book a demo: a 30-minute walkthrough of the live dashboard and driver app, with your sites, your hardware, and your numbers rather than a canned tour.