EV Charging Software in the US

If you are consumer facing in the US, build as though it does. Demand letters over inaccessible websites are routine and cheap to send, federal work brings Section 508 with it, and the Department of Justice rule under Title II sets WCAG 2.1 AA for state and local government entities on a timetable your counsel can confirm for your size band. We work to WCAG 2.2 AA and test with a screen reader rather than relying on an automated scan, because automated tools catch perhaps a third of real issues and the other two thirds are the ones that end up in a letter.

Nobody can promise you that, and a supplier who does is selling something. We have been building since 2021 and we maintain what we build, which is the honest version of the answer. The useful version is that it should not have to matter. The repository is in your GitHub organization, the domain and hosting accounts are in your company name, the stack is Next.js, Laravel, Flutter and Postgres rather than anything only we can read, and the handover document exists before you ask for it. If we vanished tomorrow, another agency could pick it up without needing to call us.

Yes to the NDA. Send your standard one and it comes back signed within 24 hours, before you describe the project in any detail. Yes to the MSA too, with the caveat that we read it properly rather than signing to be agreeable. The two clauses we usually come back on are unlimited liability, where we ask for a cap tied to the fees, and an IP clause drafted broadly enough to sweep in the internal tooling we bring to every project. Everything built for you transfers to you in full on final payment. We mark up those two and sign the rest.

Two in the afternoon in Chicago is past midnight here, half past midnight in summer and half past one in winter, so the truthful answer depends on what you are paying for. Monitoring does not keep our hours and the alert fires whatever the clock says. Whether a person is awake to act on it depends on your plan, because we are not a 24/7 on-call operation as standard, and we would rather tell you that while you are choosing a plan than while your checkout is down. Without out-of-hours cover written into the contract, the realistic answer is that it is picked up at the start of our day, which is the middle of your night, and you should price that in when you decide.

We build on OCPP 1.6-J today, which around 95% of chargers shipping in India speak, with a mapped upgrade path to 2.0.1 for certificate security, smart charging, and native payment messages. PlugEV runs 1.6-J in production; we scope 2.0.1 as a defined piece of work rather than assuming it out of the box.

Yes. We build UPI and card payment into the charging flow via Razorpay, with per-session, time-based, or per-kWh rating and automatic GST invoices. On OCPP 1.6-J we bridge the payment-to-session link in the backend; we have written a full guide on OCPP and UPI payments.

A small pilot CSMS starts around $4,000. A full production platform like PlugEV, with an operator dashboard, driver app, tariff engine, GST invoicing, and the reliability layer, typically runs $9,100 to $17,000 depending on scope. Hosting and maintenance are separate. We give a flat INR quote after a scope call.

Yes, and both can run on the same network at once. RFID with an offline fallback is how most real-world sessions start; UPI or card covers walk-up drivers. Roughly 70 to 80% of real sessions authenticate by RFID in the networks we have seen.

If your chargers speak OCPP, and most do, yes. We handle the per-vendor quirks between brands, which is one of the messier parts of running a real fleet. Tell us the charger models and we will confirm fit on the first call.