The expensive part is explaining what happened later.
The first alert is only the start. A quality team may spend hours comparing exports, checking whether expected readings are missing, and explaining why two systems show different times. Lumra is designed for the readings where those questions can delay a decision or turn into a dispute.
Keep what arrived
The complete JSON uplink delivered to Lumra is retained as the source body. TTN's claimed time and Lumra's receipt record remain distinct.
Make changes detectable
Accepted records are signed and linked in a tenant-scoped history. Exact repeats of a TTN body can resolve to the same event within that tenant.
Export the evidence
A ProofPack gives a reviewer protected records and the material needed for an independent check, 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 one TTN application for a controlled pilot.
- Request an API key.
Email [email protected] to request a tenant-specific 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.
Once your key is issued, under your application choose Integrations, Webhooks, then Custom webhook, and point Uplink messages to your provisioned Lumra ingest endpoint with your
Authorization: Bearer <API_KEY>header. Bulk TTN telemetry points are priced at $0.10 / active sensor / month ($25/month minimum, or from $199/month platform base; see pricing or LoRaWAN guide). - 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 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
The standalone checker inspects protected content and signatures against the supplied trust material.
Only when the pilot defines its device roster and expected intervals in advance. Event-driven sources need different expectations.
The package separates source-claimed observation time, Lumra receipt, and any later external batch timestamp. A batch timestamp does not establish the sensor's observation time.
Yes. The synthetic cold-chain example and checker instructions illustrate the evidence format. They are demonstrations, not TTN customer records.
The record is not structured to certify that a sensor was accurate, recover uplinks that never arrived, or guarantee a legal outcome or EU-qualified status.
Start with one question worth answering.
Tell us the TTN application, 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