Talisman SHIELD

Keep your chargers online, your tests flexible, and your migrations safe with Talisman SHIELD, the smart OCPP “traffic cop” that transparently routes WebSocket connections between multiple CPO backends. It sits between your charging stations and central systems as a pass-through layer, so your OCPP messages stay intact while your routing rules stay fully under your control.

 

With Talisman as your program intermediary, you have no direct obligation to any backend operator, and Talisman SHIELD provides the ability to change backend provider at any time and for any reason.

What Talisman SHIELD does

​

• Connects all your charging stations to one central proxy endpoint and forwards OCPP JSON-over-WebSocket traffic to any downstream CPO backend you define.​

• Acts as a fully transparent pass-through: it does not alter OCPP payloads, so both chargers and backends behave exactly as if they were talking directly.​

• Lets you override authentication details centrally, making backend switching and multi-tenant setups easier without reconfiguring every station one by one.​

• Supports custom routing rules per station or group, so you can dynamically steer traffic for testing, rollouts, or disaster recovery scenarios.​

• Works bi‑directionally, proxying messages from chargers to backends and, when enabled, from backends to chargers.

Why operators and CPOs need it

​

• Eliminate manual endpoint changes on thousands of chargers when you migrate, test, or fail over to another backend.​

• Run safe A/B tests and pilots by routing a subset of stations to new systems without touching field hardware.​

• Improve resilience: if your primary backend fails, switch routing rules and redirect live traffic to a backup system with minimal disruption.​

• Keep operations predictable: transparent pass-through and persistent rules mean no hidden logic and no surprises on reconnect.​

• Preserve commercial freedom: Talisman acts as your contracting authority, so you can renegotiate, replace, or diversify backend vendors without locking your network into a single platform.

 

Key capabilities

​

• Dynamic routing rules

• Define and adjust rules at runtime without restarting Talisman SHIELD.​

• Configure duplex behavior per rule (one-way CS→CPO or full duplex) to control where requests to chargers are allowed to originate.​

• High performance and scalability

• Designed as a lightweight module, consuming modest memory even at large scale (e.g., tests with 10,000 charging stations ran within a few hundred MB of RAM).​

• Horizontally scalable behind standard load balancers such as Nginx, Caddy, or managed cloud load balancers.​

• Broad protocol support

• Supports OCPP 1.6 and 2.0.1, with the flexibility to run separate instances if desired.​

• Flexible persistence

• Uses a simple, flat data model that can sit on databases or EBS-like storage, with low load because it is mainly used on connection (not at high frequency per message).

Deployment made easy

​

• Packaged as a Docker image, deployable on any cloud or on‑prem server that supports containers.​

• Runs as ECS tasks on AWS, ACI containers on Azure, or under Kubernetes for orchestrated, highly available setups.​

• Can be launched manually on any Docker-capable host for lab, staging, or custom network environments.​

• Fits seamlessly into modern CI/CD pipelines (e.g., GitHub Actions, GitLab CI/CD), and our team can support you end‑to‑end in automating the rollout.

​

​

Example use cases

​

• Seamless backend migration

Keep chargers pointed at Talisman SHIELD while you switch routing rules from CPO Backend 1 to CPO Backend 2, then simply reboot stations to reconnect through the new route.​

• Safe traffic multiplexing

Duplicate routing rules so traffic from a given station is sent to two different backends, allowing parallel monitoring or integration, while enforcing that only one system can send commands back to the charger.​

​

Talisman SHIELD gives you centralized control over OCPP connectivity and true commercial independence, so you can move fast with tests, migrations, and expansions—without risking your live charging network or your vendor flexibility.