The public roadmap for the Pitvolt operator console and driver app, drawn from the internal product spec. Items here are committed direction. Sequencing depends on customer signal, and a real conversation can move the queue.
Ordered by how soon a customer conversation is likely to move each one, not by build order.
A live signal from a site load meter tells the console to throttle each charger in real time, so a hotel or factory can add EV bays without upgrading the transformer. The OCPP SetChargingProfile mechanism is already wired; the missing pieces are the meter ingest and the control loop.
When a driver finishes charging but leaves the cable plugged in, the console detects the idle occupancy (session terminal, connector not Available) and nudges the driver by email while alerting the host. Once the tariff cycle lands, an optional idle fee accrues after a grace window.
Server-Sent Events push session state changes, heartbeats, and payout arrivals live over the existing broker. The dashboard stops polling and two tabs stay in sync; the driver app switches from phone to laptop mid-session and sees identical live state.
The console goes responsive so field techs and site attendants can use it on a phone without pinch-and-zoom. Read-only paths first, then the write-heavy flows (Add-Charger wizard, refunds) once phone demand is proven.
CSV downloads for Sessions, Payments, Payouts, Audit log, and Activity feed with the earnings-split columns (gross, platform fee, host share) so the accountant reconciles in seconds. PDF receipts for individual sessions and payouts complete the paper trail.
Every provisioned charger gets a print-ready QR code the host sticks on the unit. A driver standing at the charger scans it and lands straight in the charge flow, no app install required.
If a customer conversation surfaces a real need that reshuffles priorities, we reshuffle. The best channel is direct: talk to the team, and if the shape of the need is clear, we land the ticket the same week.
Email the team →