Charging Station Maintenance System
Keep Charge continuously monitors charging stations, analyzes live charger telemetry, resolves Tier 1 issues with autonomous AI agents, and keeps a complete audit trail across every site, charger, connector and event.
- Uptime focus
- 99%+
- MTTR cut
- ~40%
- CPMS-ready
- OCPP.
Open tickets
12
−4 vs. last week
TKT-1284
Connector 2 — handshake fails (CP-ALPHA-03)
TKT-1283
Charger offline 32m — Site VG-Warsaw-A
TKT-1281
Quarterly preventive maintenance
3 alerts auto-grouped into 1 ticket
liveA service desk that speaks EV charging.
Built ground-up around the domain — sites, chargers, connectors, alerts and SLAs — so your team stops fighting a generic ticketing tool and starts shipping uptime.
-
EV-aware ticketing
First-class concepts for sites, chargers and connectors. A ticket can target a whole site, one charger, or a single damaged connector — and the hierarchy is enforced server-side.
-
Smart alert → ticket grouping
Stop the noise. Repeat alerts from the same charger get auto-grouped onto the open ticket, with the raw payload kept for audit. Swap the rule for time-windows or ML later.
-
SLA tracking & dashboards
Set deadlines per priority, see breach risk in real time, and surface the metrics your operations review actually needs.
-
24/7 charger monitoring
Continuously watch station health, connectivity and alert flow across every site, so operators know which chargers need attention before downtime spreads.
-
Telemetry intelligence
Analyze online charger telemetry statistically to spot recurring faults, weak connectors, noisy stations and network-wide reliability patterns.
-
Tier 1 AI issue resolution
Let AI bots handle first-line remediation: investigate the ticket context, run approved remote actions and escalate cleanly when a human technician is needed.
-
Granular charger history audit
Trace a complete charger record from raw alerts to tickets, comments, assignments and status changes, with views by site, charger, connector or event.
-
Mobile-first dispatch
A phone-friendly tech workflow: My tickets → ticket detail → change status, add comment, attach a photo. Built for someone in front of a charger, not a desk.
-
OCPP & CPMS-ready
OCPP identity is already on chargers, connector IDs on connectors. Pipe alerts in via the v1 REST API today; bolt on full CPMS integration when you are ready.
-
Multi-tenant by design
Every service call is scoped to the calling user’s organization. CPOs, service providers and integration clients each get the right slice — and nothing more.
From live charger telemetry to resolved maintenance issues.
- 1
Monitor every station 24/7
Connect chargers through your CPMS, OCPP bridge or REST API. Keep Charge watches health, connectivity, alerts and telemetry across each site in real time.
- 2
Analyze and resolve with AI
Telemetry is analyzed statistically to detect recurring issues, while AI agents investigate Tier 1 tickets and run approved remote remediation steps.
- 3
Audit, escalate and dispatch
Every alert, action, ticket and status change lands in charger history. Escalate unresolved cases to technicians with full context by site, charger or connector.
Simple plans that scale with your network.
Pay for what you operate. Every plan includes the full app, REST API, role-based access and EN/PL UI.
Starter
Small CPOs and service providers getting started.
- Up to 50 chargers
- Up to 10 users
- Alert ingestion + ticket grouping
- Mobile dispatch workflow
- Email support
Pro
Growing operators that need SLA control and integrations.
- Up to 500 chargers
- Unlimited users & technicians
- SLA tracking & dashboards
- Maintenance scheduling
- REST API + API keys
- Priority support
Enterprise
Networks 500+ chargers, multi-region, custom integrations.
- Unlimited chargers & sites
- Custom CPMS / OCPP integrations
- SSO & advanced RBAC
- Dedicated CSM
- 99.9% uptime SLA
- On-prem deployment option
Prices in EUR, exclusive of VAT. All plans include a 30-day free trial. No credit card required.
Questions, answered.
Do I need to integrate my CPMS to start?
No. You can start by sending alerts and tickets through our REST API with an API key, or by creating tickets manually. Full CPMS / OCPP integration is on the roadmap and the schema is already prepared for it.
Which OCPP versions will be supported?
OCPP 1.6J and 2.0.1. Today the schema already carries `ocppIdentity` on chargers and `ocppConnectorId` on connectors, so when the bridge ships you don’t have to remap anything.
How is data isolated between organizations?
Every service method is organization-scoped server-side, not just in the UI. CPOs and service providers each see only their own sites, chargers, alerts and tickets.
Is the platform available in Polish?
Yes. The app ships with English and Polish day one, and all UI strings live in shared catalogs that are easy to extend with more languages.
Where is data stored?
EU region by default (Frankfurt). Enterprise customers can request a dedicated region or on-prem deployment.
Stop firefighting. Start shipping uptime.
Spin up Keep Charge in minutes — connect a single charger, push your first alert, and watch the ticket appear.