Demonstration preview · synthetic data only
Multi-source Incident ProofPack · demonstration preview

One incident. Four vendors. One proof no single platform can give you.

A cold-chain loss is never one sensor. A reefer runs warm, a door is held open, the trailer sits stopped, a pallet takes a shock, and each of those signals comes from a different vendor's device. Any one vendor can vouch for its own data. None can independently corroborate the others. This demo shows Lumra verifying four vendors' own source signatures and binding them into one incident that anyone can check offline, with no single vendor acting as the arbiter.

Four vendors, one incident

Each device signs its own reading at the source with its own key. Lumra verifies every signature against the vendor's published key, seals each record, and binds the four by a shared incident label into one fused, time-ordered readout.

ThermoGuard LoRa
Reefer temperature logger
Records the cold-chain excursion, the high-risk anchor of the incident.
SealSense
Door and seal sensor
Shows the reefer door held open while the temperature climbed.
TrackPoint LoRaWAN
GPS asset tracker
Places the trailer stationary during the excursion window.
EnviroTag
Humidity and shock sensor
Adds a handling shock during the same window.

What the incident ProofPack seals

  • Each vendor's own device signature, verified against its published key
  • Lumra's seal over each record, so any later change to any record is detectable
  • A fused, time-ordered timeline anchored on the highest-risk event, with corroboration raising confidence, never inventing risk
  • One complete, independently verifiable ProofPack per source, inside the incident document
  • Exported so anyone can verify every source signature and every seal offline, no PriviNet servers involved

What this proves, and what it does not

Proves

Each record is exactly what its own vendor device signed and what Lumra sealed, at the stated times. The four came from four independent vendors, so the timeline does not rest on any single vendor's word. Anyone can re-verify every source signature and every seal with open tools and no PriviNet involvement.

Does not prove

That any sensor observed its reading completely or accurately, what caused the excursion, who is at fault, or that a tribunal will admit these records. The fused classification is automated context, not a determination of fact or liability.

Records are supplied by each vendor's device. Lumra verifies and seals exactly what it receives, and binds them by the incident label you assign.

Why no single platform can do this

A temperature-monitoring platform can sign its own readings. A lock vendor can sign its own. A telematics vendor can sign its own. Each is a strong witness for its own data and a stranger to everyone else's. None of them is a neutral party across all four, and none can bind a competitor's signed record into the same verifiable incident.

That cross-vendor, vendor-neutral binding is the whole point. A locked bucket at one vendor says nothing about another vendor's record. An incident ProofPack carries each vendor's own signature, side by side, checkable by an outsider who trusts none of them. In a dispute, that is the difference between four competing accounts and one corroborated timeline.

How four vendors become one proof

Break it yourself

Real document · live engine
Open the real sample incident →

Below is a real incident pack generated by the live engine from four synthetic vendors. Open it, or download the machine JSON, pull out any one source's ProofPack, and run the standalone verifier against it: it checks that vendor's own source signature and Lumra's seal offline. Change a single character of any hash, and verification fails. Every source key is published at keys.txt.

For logistics, cold-chain, and IoT platforms

If you run telemetry, tracking, or sensor infrastructure, the strongest version of this is the one your devices sign at the source. Enroll your keys once, keep sending events the way you already do, and every record comes back verified against your own signature and ready to bind into a cross-vendor incident. If you want your data to carry independent weight in a dispute, that is the version worth building together.

brad@privinet.net