Built in Bengaluru for India's EV charging networks
Founded in 2023, Kazam addresses the operations gap behind unreliable EV charging networks. We built each capability by listening to operators managing chargers through spreadsheets and phone calls.
The gap we aimed to close
In 2023, India's EV charging infrastructure was expanding fast. Hardware was appearing on highways, at commercial properties, and in fleet depots. Yet operators lacked software suited to running these networks at scale in the Indian market.
Operators combined tools from other regions, used billing systems built for different payment rails, and lacked visibility into demand. Faults were handled after the fact. Revenue matching was manual. Growth planning relied on guesswork.
Akshay began Kazam after seeing this gap through work at an energy analytics firm and a hardware distribution company in the EV space. Our first platform version focused on three operator concerns: knowing when chargers fail, collecting every rupee reliably, and deciding where to add capacity next.
The people behind Kazam
A small team spanning energy operations, embedded systems, product, and customer success.
Experience in energy analytics and EV hardware distribution. Founded Kazam after spotting India's need for operations software.
Background in embedded systems and protocol engineering. Built the OCPP integration layer and real-time fault detection infrastructure behind the platform.
Product experience in fintech and payments infrastructure. Leads billing, reporting, and payment reconciliation for daily operator use.
Experience in customer operations at an enterprise SaaS company. Leads onboarding, operator support, and the early-access feedback program guiding priorities.
What shapes Kazam's decisions
Features start with an operator's real cost in time, money, or vehicle availability. We do not ship ideas just because they look good in a demo.
We account for India's payment rails, grid constraints, and available charger hardware. Our work reflects local conditions rather than adapting systems built elsewhere.
Session logs, demand forecasts, and billing records should support a clear decision. A metric belongs on the dashboard only when it helps an operator act.
Missing a fault event or payment is worse than offering fewer capabilities. We set a higher bar for uptime and data accuracy than for feature speed.
We use OCPP as the open standard and connect with payment gateways operators already trust. Our ecosystem should not create proprietary lock-in.
We remain in direct contact with every early-access partner. Field feedback should reach what we ship next in weeks, not quarters.
Want to work with us or join early access?
Talk with us directly. We are a small team and reply to serious inquiries from operators and potential team members.