Use one operating system for sites, customers, drivers, assets, billing, payments, faults, maintenance, and AI-run workflows across solar-backed power and EV charging networks.
The screens, data model, and workflows adapt to the work your team runs. Utility OS is for solar-backed power networks. Charge OS is for EV charging networks. Both use the same operating record, permissions, audit trail, and AI control layer.
Manage customers, clusters, meters, inverters, batteries, billing, payments, support, and maintenance from one workspace.
Manage stations, chargers, plugs, sessions, tariffs, prepaid payments, faults, uptime, and field work from one workspace.
Customer, driver, payment, asset, and telemetry data enter one record.
The system ties the signal to evidence, impact, owner, and recommended action.
Cases route to billing, support, maintenance, finance, or operations.
Every decision, approval, message, and action stays auditable.
Operators should not jump between billing sheets, device portals, WhatsApp notes, maintenance lists, and payment exports. The workbench puts the current record, history, blockers, and next action in one place.
Power customers need a simple account view. EV drivers need a quick QR-to-payment flow. Both portals keep the support and payment experience tied to the operator record.
GriiD OS can recommend, prepare, and run approved workflows. Equipment control stays policy-gated. Every action keeps the evidence, actor, approval state, and result attached to the record.
Find payment risks, abnormal readings, charger failures, low battery risk, overload risk, and maintenance signals before they spread.
Draft cases, messages, invoices, tickets, customer follow-ups, and field work with the supporting evidence attached.
Let routine workflows run inside permission limits while sensitive equipment actions remain gated by policy and approval.
Show us your sites, assets, customers, drivers, billing rules, payments, and maintenance workflow. We will map how GriiD OS would run it.