Built for telegram splitting and multi-base-station reception.
In a mioty deployment, multiple base stations frequently receive and forward the same subpacket telegram, or a Service Center retries an HTTP delivery. Lumra's native mioty adapter preserves the complete uplink JSON while deduplicating multi-base-station deliveries automatically.
Preserve every radio metric
Accepts standard mSC, BSC, LORIOT-mioty, and Netmore-mioty JSON uplinks: endpoint EUI (epEui / eui), packet counter (cnt / pktCnt), rxTime, base-station array (bsEui, rssi, snr, eqSnr, subpackets), raw hex/base64 data, and decoded components. The untouched payload is preserved under raw_mioty_uplink.
One telegram, one sealed leaf
When no Idempotency-Key header is supplied, Lumra derives a deterministic mioty-payload-sha256 identity from canonical (epEui, pktCnt, data). Multi-base-station deliveries and webhook retries resolve to the identical event_id and a single Merkle batch leaf.
Optional eIDAS QTST profile
Export standard Case Packages (version 1.0) or request ?evidence_profile=eu_eidas_qtst (version 1.1) to bind Merkle batch roots to RFC 3161 tokens and verify against EU Trusted List snapshots with standalone verifier v1.4.0 (--eu-trusted-list).
Connect your mioty Service Center or BSC in 30 seconds
Point your existing mioty Service Center (mSC), Base Station Controller (BSC), LORIOT, or Netmore HTTP output directly at Lumra with no middleware or payload reshaping required.
- Obtain your tenant-scoped Lumra API key.
Email [email protected] or apply via your pilot onboarding to receive a tenant-scoped bearer key. Keep the key in your webhook secret store.
- Configure the HTTP Webhook target (30 seconds).
In your mioty Service Center, BSC, LORIOT, or Netmore console, add an HTTP POST webhook pointing to
https://api.privinet.net/v1/ingest/miotywith headerAuthorization: Bearer <API_KEY>andContent-Type: application/json. (HMAC-signed partner webhooks are also supported athttps://api.privinet.net/v1/webhooks/{partner_slug}/mioty.) - Send a test uplink or run a dry-run preview.
Verify that repeated deliveries of the same
(epEui, cnt, data)return"deduped": truewith the originalevent_id, and that threshold rules on decodedcomponentsordecoded_payloadclassify breaches asiot.threshold_breach. - Verify offline with
verify_proofpack.pyv1.4.0.Export a single-event ProofPack or an incident Case Package (with optional
?evidence_profile=eu_eidas_qtst) and verify it offline using verify_proofpack.py v1.4.0. Self-serve raw JSON verification is always $0.
Pricing for mioty deployments
From $199/month ($169/mo billed annually). Bulk telemetry points (mioty, TTN, ChirpStack, LORIOT environmental sensors) are $0.10 / sensor / month ($0.08 at 500+, $0.06 at 2,000+). Standard monitored assets (reefers, cold-room controllers, doors, fixed gateways) are $1.00 / asset / month. Includes unlimited event sealing, SHA-256 hash-chaining, dual RFC 3161 timestamping, 1-year hot retention, and $0 self-serve verification.
Pay only when an incident happens: $450 Standard ProofPack (single-source, 3-day SLA, includes proofpack.json, verification transcript, pre-filled US FRE 902(13)/(14) or EU eIDAS Art. 41/35 evidence summary, gap analysis), $1,200 Priority Same-Day ProofPack (<24h), or $2,400 Multi-Source Incident Reconstruction Pack (2 to 5 correlated feeds).
+$150/month account rider + $150/ProofPack for the EU Qualified Trust Profile (eu_eidas_qtst Timestamp Rider). Extended WORM retention (+25% for 3-year, +50% for 7-year) and the $750/month Incident Desk Retainer are also available.
Lumra records timestamp_trust: "unverified_source_claim" for endpoint/base-station timestamps, binds receipt order and Merkle batch roots, and never claims automatic legal admissibility or positive EU qualification without authenticated LOTL/TL validation.
Seal your first mioty subpacket stream today.
Send us a sample JSON uplink from your mioty Service Center, BSC, or LORIOT output and we will return a signed ProofPack free, or provision your tenant key for https://api.privinet.net/v1/ingest/mioty.