Know whose fault it was, in minutes
Every excursion and every logger gap is tied to the company holding the shipment at that moment, straight from the raw logger files.
For pharmaceutical manufacturers, shippers and their cargo insurers
When a shipment goes out of range it is quarantined, and someone eats the loss. Usually that is the shipper or its insurer, because the carrier and the warehouse each have a story and nobody's logger data settles it. Pharma Custody settles it.
A quarantined vaccine or biologic shipment can be worth hundreds of thousands of dollars, and industry estimates put temperature-related losses in biopharma logistics in the tens of billions of dollars a year. After a loss, the shipper collects logger files from several parties, each covering a different part of the route, and the claim drags on for months. Most of the time the shipper or its insurer absorbs the cost.
Every excursion and every logger gap is tied to the company holding the shipment at that moment, straight from the raw logger files.
A signed allocation splits the value of a quarantined shipment by the minutes each custodian caused, within its liability cap: the evidence your claim, or your insurer's recovery, needs.
Carriers and warehouses sign their handoffs as a condition of carrying your freight. Missing or edited data stops being an excuse and becomes a finding against whoever held the shipment.
No call needed: open the service, see the price, and run it on the spot. You are charged only when the result is delivered, and the signed result is yours to download and check.
Upload each custodian's logger export and get release or quarantine, with every excursion and gap attributed.
$4 per shipment
Do it nowA signed split of the loss between carriers, within their liability caps.
$150 per claim
Do it nowAlready have a BSVKey result file? Check that it is genuine, no account needed.
Each party signs a small record at the moment it takes responsibility. The records chain together, so a missing, edited or forged one is caught.
| Record | Signed by | Says |
|---|---|---|
| pharma.handoff/1 | the receiving custodian | received this shipment from that custodian at this time, these packs (one fingerprint over all product identifiers), in this condition |
| pharma.leg/1 | the custodian holding the shipment | which logger, which time window, a fingerprint of exactly those samples, and what they show: range, excursions, gaps |
| pharma.release/1 | the final receiver's quality function | total excursion and gap time against the stability budget, and the decision |
All records use canonical JSON, a SHA-256 fingerprint and an Ed25519 signature, the same primitives proven in our space custody work.
A 1,200-pack vaccine shipment kept at 2 to 8 C, 45-minute excursion budget Verified from the raw logger CSVs: PASS Excursions 20 min + logger gaps 50 min = 70 of 45 min allowed: "quarantine" excursion air-carrier 20 min, peak 9.6 C logger_gap distributor-dc 50 min Pack SN100417 in this shipment: true Counterfeit serial SN999999: false Tampering: carrier deletes its excursion rows from the logger export caught someone edits the leg to hide the excursion caught carrier re-signs a clean leg for itself caught pharmacy's release is forged by another party caught packs swapped mid-route caught warehouse leg withheld caught
The carrier's excursion alone was within budget. The warehouse's logger gap is what pushed the shipment into quarantine, and the record says so.
Send us the logger files from one shipment that went wrong. We will show you whose fault it was.
Email embryospace@gmail.com