Bridge Kernel
Reduce reconciliation from weeks to days. Sign every reading at the edge with Ed25519, chain it into cryptographic proofs, and deliver audit-ready evidence — before disputes start.
Signatthesource.Provebeforeitmoves.Governbeforeitpersists.ThatistheBridgeKernelguarantee.
From source telemetry to reviewable evidence
Capture at the edge
Receive structured telemetry and operational events at the source — DLMS meters, OCPP chargers, Modbus devices — through protocol-native adapters.
Produce deterministic proof
Canonicalize the record, hash it, sign it with Ed25519, and attach the metadata required for later independent review.
Apply policy before persistence
Run policy checks before records hit the ledger so stale, malformed, or risky events are quarantined instead of silently accepted.
Store and prepare evidence
Persist verified records locally first, then use controlled sync and evidence-pack flows for broader operational use.
Protocol adapters for every energy source
Webhook / REST
HTTP-based telemetry and system integrations
File ingest
Controlled imports and deterministic replayable input
Scanner and edge inputs
Operational event capture at the edge
GPS / NMEA
Location-aware field event trails
Modbus RTU/TCP
Industrial energy meter telemetry
DLMS / IEC 62056
Smart meter data capture and normalization
OCPP 1.6/2.0
EV charging session verification
IEC 61850
Substation and grid event capture
Custom adapters
Protocol-specific work scoped through pilots
How Bridge Kernel generates tamper-evident proof
1. Canonicalize
Sort keys, normalize text, and produce a deterministic representation of the event payload.
2. Hash
Compute a SHA-256 digest so later systems can identify whether the content changed.
3. Sign
Use Ed25519 to attach identity and integrity metadata to the digest.
4. Envelope
Wrap the event, signature, and verification metadata into a proof object that downstream systems can inspect.
{
"event": {
"current_a": 12.4,
"power_kw": 3.1,
"voltage_v": 230.5
},
"key_id": "site-gw-01",
"key_version": 3,
"signature_context": "bridge-kernel-v1",
"signatures": [
{
"algorithm": "Ed25519",
"value": "b7e2f1c3d8a9..."
}
],
"proof_metadata": {
"hash_algorithm": "SHA-256",
"digest": "8af3c2b1e9d4f7a2...",
"timestamp": "2026-03-07T10:15:00Z",
"verified": true
}
}Deploy where the evidence needs to begin
Edge Gateway
ARM or x86 gateway close to the data source for edge-first verification.
On-Premise Server
Linux or Windows host inside an operator-controlled environment.
Containerized Runtime
Container-based deployment where local operational controls already exist.
Cloud-Adjacent Instance
Useful for controlled integrations, demos, and platform-adjacent workflows.
Security controls that sit inside the runtime itself
Built for the teams that have to defend what happened
Bridge Kernel is the edge runtime — it signs, verifies, and governs telemetry where the data is born. Cloud control, dashboards, and settlement layers build on top.
The result: operators, auditors, and counterparties get a cryptographically verifiable record of what happened — not a spreadsheet someone assembled after the fact.