What Lumra adds to mioty's two security layers
For executives and compliance leaders: mioty already protects sensor data while it travels over the air to your system. Once that data lands inside your company's database, however, your own administrators hold the keys and database credentials. Lumra is designed to seal each arriving mioty record outside your administrative boundary so an external auditor, insurer, or court can check later that no record was altered or deleted after arrival.
mioty's two built-in security layers
mioty provides network-level encryption and optional application-layer end-to-end encryption with CMAC authentication, protecting data from the endpoint to the Application Center (AC). That protection is designed to answer: "Was the data altered on the way to me?"
Lumra's downstream evidence layer
Lumra sits downstream of the Application Center (AC) and is structured to answer a different question: "Can I show an auditor, insurer, or court, later, that my records are what arrived?"
Why symmetric CMAC alone cannot settle a later dispute
mioty's CMAC uses shared symmetric keys between the endpoint and the Application Center (AC). Because both sides share the same secret key, an operator who controls the Application Center (AC) could theoretically recompute a valid CMAC on an edited record. As a result, a symmetric CMAC cannot demonstrate to an outside party after the data is stored that the record was not modified inside your environment.
Sealing ciphertext, packet counter, and CMAC
Lumra is structured to seal mioty's own integrity artifacts (ciphertext, packet counter, and CMAC) together with decoded application values inside each record, signing the canonical digest with a non-extractable Cloud HSM ECDSA P-256 key and anchoring batch roots to RFC 3161 timestamps, preserving those artifacts as tamper-evident evidence.
Packet-counter continuity in the sealed chain
The mioty Service Center (SC) already reassembles subpackets and deduplicates traffic across base stations before forwarding. Lumra accepts the Service Center (SC) or Application Center (AC) output as is and binds each endpoint's monotonically increasing packet counter into an append-only SHA-256 hash chain. Packet-counter continuity in the sealed chain is designed to show completeness so no record is silently removed.
See how Lumra seals mioty Application Center & Service Center uplinks in 90 seconds
Press Play 90s Walkthrough or click any of the 4 stages below to inspect how Lumra accepts your Service Center (SC) or Application Center (AC) output as is via /v1/ingest/mioty, seals ciphertext, packet counter, and CMAC inside a Cloud HSM hash chain, detects a 1-byte edit, and supports offline checking.
Zero impact on 10-year sensor batteries. Full preservation of mioty artifacts.
In a mioty deployment, endpoints transmit telegram-split subpackets that the mioty Service Center (SC) reassembles and deduplicates before delivering to the Application Center (AC). Lumra accepts the Service Center (SC) or Application Center (AC) output as is over HTTPS, so your over-the-air radio frames stay untouched while every arriving record is sealed into an external evidence chain.
Downstream HTTPS sealing preserves battery life
Your mioty endpoints continue sending standard ETSI TS 103 357 telegram-split subpackets over the air with zero added cryptographic bytes. Lumra is structured to seal the uplink immediately after your mioty Service Center (SC) or Application Center (AC) forwards it.
Preserve ciphertext, packet counter, CMAC, and decoded metrics
Accepts standard mioty Service Center (SC) and Application Center (AC) JSON uplinks as is: endpoint EUI (epEui / ep_eui), monotonically increasing packet counter (pktCnt / cnt), rxTime, encrypted payload (ciphertext / data), application-layer cmac, base-station reception metadata (bsEui, rssi, snr), and decoded components. The untouched payload is preserved under raw_mioty_uplink.
Completeness across the sealed hash chain
Each arriving record is linked by SHA-256 digest to the prior record and preserves the endpoint's mioty packet counter. If an administrator or intruder later attempts to delete an inconvenient temperature excursion or utility reading from storage, both the SHA-256 chain link and packet-counter continuity expose the missing record.
Portable ProofPacks & standalone offline checker
Export portable ProofPacks designed to support Smart Meter Light (SML) OBIS tariff billing reviews, FDA 21 CFR Part 11 and EU GDP pharmaceutical cold-chain quality reviews, or insurance claims. An optional ?evidence_profile=eu_eidas_qtst profile (in development) binds Merkle batch roots to RFC 3161 tokens for offline checking with verify_proofpack.py v1.4.0.
Connect your mioty Application Center (AC) or Service Center (SC) in 4 steps
Point your existing mioty Application Center (AC) or Service Center (SC) HTTPS webhook or MQTT broker directly at Lumra with no middleware, custom parsers, or payload reshaping required.
-
1. Obtain your tenant-scoped Lumra API key or MQTT subscription
Email [email protected] or use the 24-hour Capture Pack Pilot below to receive a tenant-scoped bearer key or dedicated MQTT v3.1.1 topic binding.
-
2. Configure the HTTPS Webhook or ACMQTTI Broker feed (30 seconds)
In your mioty Application Center (AC) or Service Center (SC) console, add an HTTPS POST webhook pointing to
https://api.privinet.net/v1/ingest/miotywith headerAuthorization: Bearer <API_KEY>, or point Lumra's MQTT v3.1.1 subscriber at yourmioty/<app_root>/+/uplinkbroker topic. HMAC-signed partner webhooks are also supported athttps://api.privinet.net/v1/webhooks/{partner_slug}/mioty. -
3. Send a test uplink and inspect sealed mioty artifacts
Confirm that your Service Center (SC) or Application Center (AC) output is accepted as is, with the endpoint's
ciphertext,packet counter, andCMACsealed into the canonical record alongside any decodedcomponents. -
4. Check records offline in 60 seconds (zero vendor lock-in)
Standard signed JSON exports are included with your monthly sensor plan. Any utility customer, quality reviewer, or insurer can check your exported records offline using our standalone open tool verify_proofpack.py (v1.4.0) or in the browser at privinet.net/audit.html without needing a PriviNet account or calling our servers.
Send one day of Service Center JSON output. Get back a verified ProofPack at $0.
For mioty operators, utilities, and mioty Alliance members: before changing a single production setting, send us a 24-hour JSON or JSONL capture from your Service Center (SC) or Application Center (AC). Within one business day, we return a self-contained ProofPack and 24-hour packet-counter completeness report checkable offline.
24 hours of uplink JSON, zero radio keys
Share 24 continuous hours of JSON uplinks from 1 to 50+ endpoints (a 2-to-6-hour lab bench capture is also welcome). Hashed or masked 64-bit endpoint EUIs (epEui / EUI) and base-station EUIs (bsEui / gweui) work cleanly as long as each endpoint keeps a consistent pseudonym across the window. Never include NWKKEY, APPSKEY, or personal data.
ACMQTTI, LORIOT Hybrid NMS, or native SC / AC JSON
Drop any of these directly into a .jsonl, .json, or .gz export with zero reformatting: (a) Fraunhofer IIS ACMQTTI MQTT dumps on mioty/<app>/<epEui>/uplink carrying baseStations, cnt, data, format, typeEui, and components; (b) LORIOT Hybrid NMS cmd: "rx" and cmd: "gw" outputs with EUI, packetCntUl, data or encdata, and gws; or (c) native Service Center (SC) and Application Center (AC) JSON exports from WEPTECH AVA, Swissphone, LZE, or BehrTech stacks.
mioty ingest profile, MQTT v3.1.1 subscriber, and counter-gap completeness engine are currently validated against the documented ACMQTTI interface specification (simulated) and aligned with documented LORIOT Hybrid NMS mioty output schemas. Operator 24-hour capture packs are replayed in an isolated single-tenant sandbox (retention_policy: "sandbox") as part of our live Service Center (SC) interoperability program.
Request a Private Upload Link
Tell us which Service Center (SC) or Application Center (AC) format you run and we will send a private pre-signed upload URL and return your ProofPack within one business day.
- Self-contained
.proofpack.jsonreceipt bundle for your 24h capture - Per-endpoint 24h Packet-Counter Completeness Report (missing counter ranges, duplicates, out-of-order arrivals, and resets)
- Offline one-click browser check at privinet.net/audit.html and CLI check via
verify_proofpack.py - Sandbox isolation: raw capture purged after delivery at your request
mioty 24h Capture Pack.
Metered per active sensor for utilities. Predictable for pharma & facilities.
Standard JSON ProofPack exports and standalone offline checking (verify_proofpack.py) are included with every monthly plan. Optional turnkey legal dossiers ($450) are only needed when you want PriviNet to assemble a court-formatted or multi-vendor incident package.
Purpose-built for high-density mioty Service Centers (SC), Application Centers (AC), and Smart Meter Light (SML) utility networks.
- $0.10 / active sensor / month ($25/mo min): Volume discounts drop to $0.08 at 500+ sensors and $0.06 at 2,000+ sensors
- Preserves mioty Integrity Artifacts: Seals ciphertext, packet counter, and CMAC from your Service Center (SC) or Application Center (AC) output as is
- Continuous Cryptographic Sealing: SHA-256 hash chains, packet-counter continuity checks, Cloud HSM ECDSA P-256 signatures, and dual RFC 3161 timestamps
- Self-Serve JSON Exports & Standalone Checker Included: Export signed JSON records anytime and check them offline via
verify_proofpack.py(v1.4.0) at no extra cost
Combine mioty warehouse and freezer sensors with pharma reefer trailers, lab monitors, and fleet telematics on one platform.
- Starts at $199/month platform base: Includes 1-year hot retention, SHA-256 chaining, dual RFC 3161 timestamps, and self-serve JSON ProofPack exports
- $1.00 / asset / month for Standard Monitored Assets: Cold-room controllers, lab freezers, pharma reefers, dock doors, and fixed gateways ($0.90 at 100+, $0.75 at 500+, $0.60 at 2,000+)
- $4.00 / asset / month for Camera or High-Liability Assets: Dashcam MP4 digest binding and high-value biologics lots ($3.00 at 100+, $2.25 at 500+, $1.75 at 2,000+)
- Bulk mioty sensors can be added to any platform plan at the $0.10 / $0.08 / $0.06 volume rate
When a major lawsuit, regulatory review, or cargo claim lands and you want PriviNet to correlate multi-vendor feeds and prepare pre-filled court certifications.
- $450 Turnkey Legal Dossier: Assembled evidence bundle with human-readable check transcript, gap analysis, and pre-filled US FRE 902(13)/(14) custodian certification (3-day SLA)
- $1,200 Priority Same-Day Dossier (<24h SLA) or $2,400 Multi-Source Incident Dossier (correlating 2 to 5 feeds across warehouse mioty sensors, carrier GPS, and door logs)
- Optional Compliance Riders: Extended WORM retention (+25% for 3-year, +50% for 7-year), $750/mo Incident Desk Retainer, or +$150/mo EU eIDAS Timestamp Rider
- Free 1-Day ProofPack Test: Send a sample mioty JSON uplink and receive a signed ProofPack at $0
timestamp_trust: "unverified_source_claim" for endpoint and base-station observation timestamps, binds Lumra receipt order and Merkle batch roots, and is structured to preserve received artifacts without claiming sensor calibration accuracy, automatic legal admissibility, or positive EU-qualified status without authenticated LOTL/TL validation. Inspect the full cryptographic specification on the Technical Architecture Page.
Seal your first mioty Application Center or Service Center stream today.
Send us a sample JSON uplink from your mioty Application Center (AC) or Service Center (SC) output and we will return a signed, independently checkable ProofPack free within one business day, or provision your tenant key for https://api.privinet.net/v1/ingest/mioty.