Every message between your chargers and your backend, visible.
keepProxy sits between your chargers and your charging backend. It passes everything through unchanged and keeps a copy of every message for you. Nothing to replace, nothing to reconfigure beyond one address on the charger.
The whole conversation, not a vendor’s summary.
-
Invisible to your backend
Every message passes through unchanged, including the charger’s login. Your backend sees the same chargers it saw before.
-
A complete record
Every message, in both directions, timestamped and kept. When a charger misbehaves you have everything it said and everything it was told.
-
Alone, or with keepCharge
Use the record in your own tools, or let keepCharge read it and turn it into alerts, health and cases. Switch that on later without touching the chargers again.
-
Built to stay up
Reconnects handled, idle connections closed, one live connection per charger. Your fleet runs isolated from everyone else’s.
One hop in the middle. A copy to the side.
Chargers talk to keepProxy, keepProxy talks to your backend, and neither notices the difference. The copy of the traffic goes to you, or to keepCharge.
Questions, answered.
Which backends does it work with?
Any backend your chargers can talk to today. keepProxy speaks the standard charger protocol and forwards what it hears, so there is nothing backend-specific to set up.
Can keepProxy send commands to a charger?
Not today. keepProxy only observes. Commands stay with your backend, which is how it should be until you decide otherwise.
Does it slow my chargers down?
It adds one network hop and nothing else. Messages are forwarded as they arrive; the copy is taken on the side.
See what your chargers are saying.
Tell us about your network and your backend. We will set keepProxy up on a few chargers first.