Proof layer for events and evidence

Prove what happened. Anywhere it is captured.

The day a record is challenged, in a claim, an audit, or a courtroom, a plain log only proves your own system stored it, and you control that system. Lumra signs each event at the source and chains it, so anyone can verify it independently, without trusting you.

Request a pilot See the architecture
// live: sign → chain → verify
✓ verified · independent
Event captured
phone · sensor · camera
Signed at source
Ed25519 · device-bound key
Hash-chained ledger
linked to prior entry
Verified by anyone
standalone · no dependency
Ed25519
Signing at the source
end-to-end
Pipeline live
CI-tested
Automated test suite
0-dep
Standalone verifier
webhook
Ingest from any source
The platform

One proof layer. On top of whatever already captures the event.

Lumra does not replace your cameras, sensors, or IoT platform. It webhooks into them and adds cryptographic proof, custody, and independent verification that the source system cannot provide on its own.

Sources of events and evidence
Security cameras

VMS evidence integrity

Dashcams & fleet

tamper-evident footage

IoT platforms

ThingsBoard, MIOTY

Worker phones

NFC tap, biometric sign

Sensors

any signed or raw feed

mioty_webhookhttp_webhookcamera / VMSdashcam

Lumra Edge Proof Network

sign · hash-chain · anchor · verify

Ed25519 at source multi-tenant ledger Merkle anchors
signed export → independently verifiable by any third party
How it works

Three steps, whatever the source.

01 / SIGN

Signed at the source

The event is signed at the moment it happens, by the device or actor responsible, with a key bound to the source. Proof is created where the event lives, not reconstructed later.

Ed25519 · device-bound
02 / CHAIN

Hash-chained ledger

Each meaningful event links to the hash of the one before it in a multi-tenant ledger. High-volume telemetry stays separate and is Merkle-anchored, so volume never bloats the proof.

two data planes
03 / VERIFY

Verified by anyone

The ledger exports as a signed bundle. A standalone tool with no PriviNet dependency checks every signature and the full chain. The record holds up even if PriviNet is not in the room.

no runtime dependency
Why it is different

Encryption protects data. Lumra proves the event, to anyone.

Conventional systems

Encrypted central log

Access control and transport security protect data while it moves and while you hold it. But the record can be altered after the fact, and verifying it means trusting the vendor and their server.

You trust the system that wrote it.
Lumra

Application-layer proof

Every event is signed by the source and hash-chained, so tampering is detectable. A third party verifies the whole record with a standalone tool that needs nothing from us.

The proof survives the vendor going away.
The obvious question

Why not just build it yourself?

You could sign a file in an afternoon. What you cannot do alone is make your own records credible to someone who does not trust you, because proof you issue about your own data is inherently weak. You control it.

The value is that the check does not depend on you. That is why it sits as a neutral layer, not as a feature inside the system being questioned.

Self-issued proof versus a neutral proof layer If you build it yourself, you sign your own record and check it yourself, so the proof depends on you. With a neutral layer, the record flows from you to Lumra to anyone, and the check does not depend on you. IF YOU BUILD IT YOURSELF You sign + check Your record self-issued self-issued · you control it WITH A NEUTRAL LAYER You Lumra neutral layer Anyone the check does not depend on you
Where the need is sharpest

Bounded environments with multiple actors and high-stakes accountability.

Ports & cargo terminals

Custody handoffs and chain-of-custody evidence for high-value, dispute-prone freight.

Dashcam & fleet

Tamper-evident footage for insurance claims, fleet liability, and legal admissibility.

Security & surveillance

Evidence integrity and custody on top of camera and video-management systems.

Airports & aviation

Workforce check-ins, perimeter custody, and emergency acknowledgement as signed events.

Smart cities & utilities

Substations, water systems, and public-asset events with a defensible record.

Maritime & venues

Crew muster, onboard safety, and contractor accountability across large or moving sites.

Common questions

What Lumra is, and what it is not.

What is the Lumra Edge Proof Network?
Lumra is a proof layer that signs operational events at the source, hash-chains them into a multi-tenant audit ledger, and lets any third party verify the record independently. It rides on top of the systems an organization already runs and adds the cryptographic proof those systems cannot provide on their own.
How is Lumra different from an encrypted log?
Encryption protects data while it moves and while you store it, but the record can still be altered after the fact, and verifying it means trusting the vendor and their server. Lumra signs each event at the source and links it into a hash chain, so tampering is detectable and anyone can verify the whole record with a standalone tool that needs nothing from PriviNet.
Is Lumra a blockchain?
No. Lumra uses a hash-chained audit ledger and standard cryptographic signatures such as Ed25519 and SHA-256, not a distributed blockchain or any cryptocurrency. The goal is an independently verifiable record, not a decentralized network or token.
What systems can Lumra integrate with?
Lumra ingests events by webhook from MIOTY gateways, generic sensors and IoT platforms, security cameras and video-management systems, and dashcams. It complements existing systems and integrators rather than replacing them.
Where is Lumra used?
Lumra fits bounded environments with multiple actors and high-stakes accountability: ports and cargo terminals, dashcam and fleet footage, security and surveillance, airports and aviation, smart cities and utilities, and maritime and venue operations.
Is Lumra available today?
The build is demoable today. Source signing, a hash-chained ledger, Merkle-anchored telemetry, MIOTY and HTTP webhook ingest, and a standalone verifier are all working. PriviNet is currently scoping paid pilots.

Run a pilot on real hardware.

The build is demoable today: an event captured, signed, and independently verified. See it on a device, then scope a pilot for your environment.

Request a pilot