The expensive part is explaining what happened later.
For executives and operations leaders: LoRaWAN protects sensor traffic over the air from the end-device to your network server using shared AES-128 session keys. Once the reading lands in your cloud database, however, an insurer, regulator, or opposing counsel can challenge whether an administrator edited or deleted rows after an incident. Lumra is designed to seal each arriving LoRaWAN uplink outside your administrative reach.
What LoRaWAN session keys protect
LoRaWAN uses shared AES-128 network and application session keys (NwkSKey and AppSKey) to authenticate and decrypt frames between the sensor and your LoRaWAN Network Server (LNS). That answers whether the radio packet arrived intact at your server.
What Lumra is structured to add downstream
Lumra receives the webhook JSON from your LoRaWAN Network Server and signs the canonical record with a non-extractable Cloud HSM ECDSA P-256 key, chaining each record by SHA-256 so an outside reviewer can check later that stored records match what arrived.
Keep what arrived
The complete JSON uplink delivered to Lumra (including end_device_ids, f_cnt, frm_payload, decoded_payload, and rx_metadata gateway array) is retained as the source body. The source's claimed time and Lumra's receipt record remain distinct.
Make post-arrival changes detectable
Accepted records are signed inside a Cloud HSM and linked in a tenant-scoped SHA-256 history. Exact webhook retries of the same uplink body resolve to the same event within that tenant.
Export portable evidence
A ProofPack gives an external reviewer the protected records and trust material needed to run an independent offline check with verify_proofpack.py, without access to a Lumra account.
Quickstart: Request an API key
Self-serve public quickstart credentials are held pending completion of external end-to-end validation. Until then, request a tenant-scoped API key directly and we will provision your LoRaWAN application (The Things Stack, ChirpStack, or LORIOT) for a controlled pilot.
-
Request an API key.
Email [email protected] to request a tenant-specific API key. PriviNet checks the production release and delivery path before issuing credentials. Keep the key out of URLs, screenshots, and public samples.
-
Add a custom webhook in The Things Stack Console (or your LNS).
Once your key is issued, open your application in The Things Stack Console, choose Integrations, Webhooks, then Custom webhook, and point Uplink messages to your provisioned Lumra ingest endpoint with your
Authorization: Bearer <API_KEY>header. -
Test the route with synthetic data first.
Confirm authentication, one event after an exact replay, tenant isolation, response time, and a retrievable package. Connect approved live devices only after those checks pass.
-
Export and independently review.
Agree on batch and export cadence. Run the standalone checker (
verify_proofpack.pyv1.4.0) with an appropriate trust root obtained separately from the package. Record any unresolved timing or completeness limits.
A proposed Lumra template is in TTN pull request #115. It is not available as an official Console tile unless TTN merges and releases it. An approved pilot can use a custom webhook in the meantime.
What the record can answer & sensor pricing
The standalone checker inspects protected content and signatures against the supplied trust material and exits non-zero if a single byte was altered after sealing.
When the pilot defines its device roster, frame counter (f_cnt) expectations, and reporting intervals in advance, sequence gaps are surfaced explicitly.
The package separates source-claimed observation time, Lumra receipt time, and any later external RFC 3161 batch timestamp. A batch timestamp does not establish the sensor's physical observation time.
Yes. The synthetic cold-chain example and offline checker instructions illustrate the evidence format. They are demonstrations, not TTN customer records.
The record is not structured to certify that a physical sensor was calibrated accurately, recover uplinks that never arrived, or guarantee a legal outcome or EU-qualified status.
- $0.10 / active sensor / month ($25/mo min): Drops to $0.08 at 500+ sensors and $0.06 at 2,000+ sensors
- Downstream HTTPS Sealing: Preserves complete LoRaWAN uplink JSON,
f_cnt, and gateway metadata with zero extra over-the-air radio bytes - Self-Serve JSON Exports Included: Check exported records offline anytime with
verify_proofpack.py(v1.4.0) at $0
- Combine LoRaWAN sensors with pharma cold-chain monitors, lab freezers, and MyGeotab fleet telematics on one platform
- $1.00 / standard asset / month and $4.00 / camera or high-liability biologics asset / month
- Optional $450 Standard ProofPack Dossier (3-day SLA) with pre-filled US FRE 902(13)/(14) custodian certification when a dispute lands
Start with one LoRaWAN application worth protecting.
Tell us the LoRaWAN Network Server (The Things Stack, ChirpStack, or LORIOT), the devices and cadence, and the incident or audit question you need to resolve. We will scope a controlled pilot with written success criteria before live traffic is connected.
Discuss a Controlled Pilot