Skip to content
PinakashieldTech
Free health checkHealth check

GridSEAL

A security and evidence layer for EV charging networks. The first release is targeted for about Q2 2027, and this page shows what exists today and what’s planned.

Request a free health checkSee what exists today
Evidence packDemo data

GS-PK-2026-1024-07, 41 items

Manifest

9f3a…c71e

Alert

41bd…0a92

OCPP frames

e07c…5f18

Approval

2a6e…d4b3

Action

c81f…77a0

Hash chain41 of 41 links match
TimestampRFC 3161, 24 Oct 02:18:53
Dual signatureECDSA P-256 + ML-DSA-65

NIS2 early warning draft

23:54:49

At 02:14:07 CEST, unsigned firmware was pushed to six DC charge points at one site. EV-02

Prototype screen with demo data.

What GridSEAL will do

Four jobs on one record, from the first signal to the report a person signs.

Know

A register of charge points, identities, firmware and cryptography, with a source beside each field. OCPP 1.6-J and 2.0.1 first.

Roadmap, first release

Detect

Deterministic rules on back-end events, such as an unsigned firmware job, and on fleet-wide commands: how many chargers got one, and how fast. Tying a station ID to its SIM and certificate needs network data as well as the export. Alerts name the rule that fired.

Research pilot, rules engine in the second release

Contain

Actions through your back-end, after a check for active sessions. A named person approves, and steps that can be undone have an undo.

Isolation lab-tested, approval in the second release

Prove

Hash-chained, timestamped evidence packs with hybrid post-quantum signatures, a NIS2 clock, and an offline verifier for your auditor.

Roadmap, first release

At 02:14, someone pushes unsigned firmware to six chargers

A demo scenario at a fictional Hamburg operator, on prototype screens with demo data. The product isn’t shipping yet.

Six charge points out of 14,820, found by name

The register shows what each charger is and where each field came from. One identity doesn’t match.

InventoryDemo data
CP-HH-001-DC-06 of 14,820
CP-HH-001-DC-01ChargingID verified
CP-HH-001-DC-02IdleID verified
CP-HH-001-DC-03ChargingID mismatch
CP-HH-001-DC-04IdleID verified
CP-HH-001-DC-05IdleID verified
CP-HH-001-DC-06ChargingID verified

What exists today

One status per capability. “Live” will appear here only when a capability runs at a paying customer.

CapabilityStatusWhere it has runNext
Asset and identity registerRoadmapNot yet in GridSEAL. PST-GridTrace is a separate AEGIS prototypeR1
Fleet-wide command rulesRoadmapNot yet runR1
Edge detectionResearch pilotAEGIS, tested with Pilot 7 on a live 5G-connected charging network, using a different architectureFleet rules from R1, rules engine R2
Isolation with undoLab-testedDemo bench with emulated stationsApproval gate R2
Hash chain and ML-DSA-65 signingLab-testedPrototype on the demo benchSealed packs R1
Sealed packs and offline verifierRoadmapNot yet runR1
NIS2 clock and report draftsRoadmapNot yet runClock R1, drafts R2
SIEM exportRoadmapNot yet runR3

Last reviewed 5 November 2026.

What ships when

Planned releases. The dates are targets and may move.

  1. Today

    Prototype in AEGIS

    Station and platform simulator, hash-chained evidence with ML-DSA-65 seals, and a lab dashboard.

  2. R1, about Q2 2027

    Observe and prove

    Charger inventory, identity binding, posture findings, fleet-wide command rules, sealed packs and the NIS2 clock.

  3. R2, about Q4 2027

    Detect and respond

    Rules engine, approved containment, German and English report drafts, and firmware and vulnerability lifecycle.

  4. R3, 2028

    Validate and extend

    Test campaigns on a digital twin, SIEM exports, supplier assessments, roaming and Plug & Charge observation.

Where GridSEAL sits

The rules we’re building to. GridSEAL sits beside your charging back-end and outside the charging path, so your security engineer can review the data flow before anything connects.

Design intent. Solid lines are read-only data, and dashed lines are actions a person has approved.
Outside the charging path
GridSEAL will read a back-end export or a read-only API, so OCPP traffic doesn’t pass through it.
Read-only first
Access starts read-only, and you choose if and when actions are switched on.
Fail-open
If GridSEAL goes offline, charging will carry on. It sits outside the charging path.
A named approver
A person on your team approves each action. Steps that can be undone will have an undo.
Rules decide
Detection is deterministic, so you can audit why an alert fired. Machine learning only advises.
Safety stays in the charger
Electrical protection and charger safety functions stay outside GridSEAL.
EU-hosted
EU hosting is planned. We’ll publish the region and sub-processors before the first customer connects.

How a sealed record works

Each line’s fingerprint includes the line before it, and the end of the chain is signed. Change a line later without the signing key and the record stops matching.

  1. Alert

    41bd…0a92

  2. Approval

    2a6e…d4b3

  3. Action

    c81f…77a0

  4. Signed head

    signature over all of it

Each fingerprint includes the one before it, and the last one is signed. Illustration with sample values.

Try altering a sample record

GridSEAL Grid, for the whole vehicle-to-grid chain

GridSEAL Grid is our mid-term plan for vehicle-to-grid security, from the vehicle and charger to the aggregator and grid operator. When vehicles feed power back, each dispatch has to be verified, bounded and stoppable, and it’ll carry the same evidence record.

Roadmap, design partners only

Join the design-partner programme
High-voltage switchyard lit up at night, with pylons and power lines above it

Know where your network stands in two weeks

A free health check: an outside-in scan plus one read-only export, with a written report. Nothing is installed.

Request a free health checkSee a sample report

What comes next

A six-week paid pilot at one site, with success criteria agreed up front. Then an annual subscription: evidence first, then Detect and Contain.