ValveRide Custody / In development. Offered by invitation.

Every Handoff. On the Record.

Before you take the load, and every time it changes hands.

ValveRide Custody is a sourced, signed record of every handoff and the conditions in transit, for high-value and temperature-sensitive freight. Built as the load moves, not reconstructed after the loss.

No driver app. No hardware at the dock. Nothing added to the load.

Three answers only: agree, disagree, or unknown. Deterministic rules. Same inputs, same answer.

How the Proof Works

See the proof, then check it yourself.

Every Custody load is a chain of events that each party stated on the record. Below is one demo load, end to end: how the chain is checked, how it is sealed, what you can download, and how Custody reads conditions and handoffs. Every pack is signed and timestamped. Any alteration is detectable.

Demo data. The load, parties, and readings below are sample values.

Chain check

Clean. All 11 events recompute to their stored hashes, and each one links to the one before it.

Custody runs this check again every time the page loads, so what you see is the current result, not a saved badge.

Demo data

Seal

The load is signed with an AWS KMS key and timestamped by DigiCert. The seal covers positions 1 to 11, at the head of the chain.

If anything in those 11 events changes after sealing, the seal no longer matches.

Demo data

The proof pack

One download holds everything needed to check the load without us:

  • events.json (the events)
  • manifest
  • seal.json
  • signing-key.der (the public key)
  • timestamp.tsr (the DigiCert timestamp)
  • VERIFY steps
  • a standalone verifier

Customers run the verifier, or follow the openssl route in VERIFY. They don't have to trust us to check it.

Demo data

Conditions

The shipper says 34 F. The broker says 38 F. That pair reads Disagree, 2.2 C apart.

The carrier has nothing on file, so its pairs read Unknown. Missing never counts as agree.

Custody records what each party stated. It doesn't decide who's right.

ConditionsDisagree
The required temperature each party stated on one load, as each one supplied it.
PartyRequirement as suppliedMode
Shipper34 Fcontinuous
Broker38 Fcontinuous
CarrierUnknown. No requirement on file.
  • Shipper and brokerDisagreeSetpoints 2.2 C apart. Mode: agree.
  • Shipper and carrierUnknownNo requirement on file for the carrier.
  • Broker and carrierUnknownNo requirement on file for the carrier.
Each pair reads agree, disagree or unknown.
Demo data

Handoffs

The shipper gate-out and the carrier pickup are 20 minutes apart, inside a 60-minute window, so the handoff reads Corroborated.

Demo data

At Booking

Before the Load Is Yours.

Custody starts before the freight moves. The moment a carrier or a broker commits to a load, what that load requires is already written down: the insurance on file, the equipment the lane needs, the endorsements the driver has to hold, the steps in the broker SOP. Custody reads those requirements against the commitment and answers while there is still time to put a different truck on it.

1

The Load Arrives.

A tender or a booking lands from the system your desk already works in, a TMS or an API. Nobody retypes a load to start a check.

2

Custody Checks the Requirements.

Insurance, equipment, driver endorsements, and the broker SOP, each read from the record that states it and set against what this load asks for. Deterministic rules. Same inputs, same answer.

3

The Answer Comes Back.

To the desk that booked the load, over email, Teams, Slack, or your own system through the API. Never to a driver. Custody has no way to reach one.

Agree.

Everything the check was asked to look at is on the record, and it lines up with what the load asks for.

Disagree.

At least one requirement does not line up. The answer names which one, and what each side said about it.

Needs Review.

Something the check needs is missing or silent, so there is no answer to give and a person looks. Silence is never read as agreement.

The same three answers the rest of Custody runs on, in the words a booking desk uses for them. A booking check states what the records said at the moment it was asked. It is not a judgement about the carrier, it is not a rating, and the booking stays yours to make.

Three answers only: agree, disagree, or unknown. Deterministic rules. Same inputs, same answer.

The Gap

The Paperwork Matched. The Freight Did Not.

Modern freight theft rarely breaks a lock. It hides in the space between parties: a swapped carrier, an altered document, a pickup nobody can show. When the claim lands, everyone rebuilds the story from emails, PDFs, and memory, and every party brings a different version.

One Load, Six Systems.

The PO, the load number, the BOL, the ELD, the gate log. Nothing ties them into one record.

Proof Built After the Loss.

Most custody records get assembled once something has already gone wrong. By then the gaps are permanent.

Nobody Owns the Handoff.

Each party documents its own side. The moment freight changes hands is the moment the record is weakest.

The Product

One Load. One Record. The Evidence Pack.

For every covered load, Custody assembles an Evidence Pack: a single, sourced record of who had the freight, where, and when. It is built from the systems already running the move, so nobody retypes anything and nobody reconstructs anything.

Agree, Disagree, or Unknown.

Each handoff shows your record beside the carrier's. Where they agree, the pack says so. Where they disagree, or one side is missing, it says that too. Every entry shows its source and when it was recorded.

One Identity per Load.

The PO, BOL, PRO, and load number are tied to one record, so every party is looking at the same load.

Handoffs, Not Breadcrumbs.

The pack records the moments that matter: pickup, transfer, delivery. It is a custody record, not a tracking feed.

Ready When Someone Asks.

Hand claims, audit, or your insurer one record instead of a folder of screenshots.

Conditions in Transit

Not Only Who Had It. What It Went Through.

A custody record that stops at who signed for the freight cannot answer a rejected reefer load. Custody reads the conditions in transit from the same systems, applies deterministic rules, and states agree, disagree, or unknown on the record.

What Each Side Required.

The shipper API, the carrier TMS, and the broker record each carry a required temperature. Custody compares them and states whether they agree, disagree, or are unknown, at tender and before a single reading is looked at. A setpoint that matches within two degrees Fahrenheit agrees. Continuous against cycle is a disagree on its own, even when the numbers match.

What the Trailer Reported.

Readings come from the unit already on the trailer, through Thermo King TracKing and ORBCOMM, with the owner approval. The pack reports them as air temperature at the unit, with the source and the time. It reports the readings; it does not grade them.

What Happened at the Doors.

Door events, electronic seals, and gate records from the equipment already there, set beside the handoffs on one timeline. Where a side is silent the pack says unknown. Silence is never read as agreement.

Three answers only: agree, disagree, or unknown. Deterministic rules. Same inputs, same answer.

How It Works

Three Steps. No New Work at the Dock.

1

Connect.

You send Custody your loads and facility records through a secure API, and we help your team integrate. Your carriers approve access to the records their systems already produce for those loads, and only those loads.

2

Assemble.

As the load moves, Custody builds the Evidence Pack from system records: the handoffs, and the conditions in transit each source reported. No driver input. No scanning. No extra paperwork.

3

Hand It Over.

At delivery the pack is complete. Share it with the people who need it, and keep it for the day someone asks.

Connections

Both Sides of the Handoff. Then Locked.

A record built from one party's data is a claim. Custody reads your side and the carrier's side of every handoff and shows where they agree, where they disagree, and where one side is silent. Then the finished pack is signed and timestamped.

Custody API

Your tenders, reference numbers, and facility events, sent straight from your systems.

Carrier Systems

TMS, ELD and GPS, and shipping documents, read with the carrier's approval.

Carrier of Record

Federal authority and insurance status recorded at tender and at pickup.

Signed and Timestamped

Every pack is sealed against alteration, including by us.

By Design

A Record. Not a Tracker.

Custody works quietly, behind the systems already moving the freight. It is defined as much by what it refuses to do.

No Driver App. No Driver Texts.

Custody never contacts drivers. There is nothing for them to install, answer, or tap.

No Live Map.

Custody is not a dot on a screen. It records custody events and leaves real-time tracking to the tools you already run.

No Labels. No Scanners.

No ValveRide stickers, QR codes, or devices to manage at the dock.

No Commercial Data.

Custody never reads rates, pricing, or discounts between you and your carriers. It sees the move, not the money.

For Shippers, Carriers, and Brokers.

Three desks, one record. Quiet for the driver in all three: Custody never contacts one.

For Shippers

One Standard Across Every Carrier.

A sourced, signed custody record on the loads you cannot afford to lose, and one standard across every carrier you use.

For Shippers

For Carriers

No App. No Disruption.

The handoff pack costs carriers nothing. Your drivers never hear from us, you control what is shared, and you earn Custody Premier status. The booking check is a paid product.

How It Works for Carriers

For Brokers

Check It Before You Cover It.

Your SOP, the insurance on file, the equipment, and the endorsements, read against the load the moment a carrier commits to it. Agree, disagree, or needs review, back at your desk.

Talk to Us About Brokers

Security

Evidence Is Only as Good as the System Holding It.

Dedicated infrastructure.

A dedicated database, dedicated sign-in, and dedicated keys. Nothing is shared.

Isolated from day one.

Every customer's data is walled off by default, not by exception.

Read only.

Custody reads the records it is granted. It does not write back.

Tamper-evident.

Events are append-only, and every finished pack is signed and independently timestamped.

Questions

What the Pack Does and Does Not Say.

Does Custody record temperature?

Yes. Custody records what each side said the temperature should be, taken from the shipper's API, the carrier's TMS, and the broker's record, and states whether those requirements agree, disagree, or are unknown. It then reports what the trailer's own equipment reported as air temperature, with its source and time. Connected sources today are Thermo King TracKing and ORBCOMM.

Does Custody say whether my product was damaged?

No. Custody reports what each source said and never draws a conclusion about the freight itself. The pack shows the required temperature from each side, whether those requirements agree, and the readings the equipment reported. What that means for the load is your call, your carrier's, and your insurer's.

Does Custody need new hardware on the trailer?

No. Custody reads the equipment already on the trailer through its maker's own API, with the owner's approval. Thermo King TracKing and ORBCOMM are connected today, alongside partner door sensors, electronic seals, and cameras. There is nothing to install at the dock and nothing for a driver to carry.

What answers does an Evidence Pack use?

Three, and only three: agree, disagree, or unknown. Deterministic rules produce every answer in the record, so the same inputs give the same answer every time. Where one side is silent the pack says unknown; silence is never read as agreement.

Does Custody check a load before it is booked?

Yes. When a carrier or a broker commits to a load, Custody reads the requirements that load carries, the insurance on file, the equipment, the driver endorsements, and the steps in the broker SOP, and answers agree, disagree, or needs review. Those are the same three answers the rest of the record uses. The answer goes back to the desk that booked the load, over email, Teams, Slack, or your own system through the API, and never to a driver. Silence is never read as agreement.

Proof Package Questions

What Is in the Package, and How to Check It.

The proof package

What is the proof package?

Automatic sealing is rolling out now and is not yet on for every account. Once it is on for yours, when a load closes, Custody seals its record and emails a link to the proof package to the address you gave us at setup. There is no button to press and nothing to request. Open the link, sign in with the link or code we email you, and the package downloads.

The package is a zip file with one folder inside, named for the load and the point in the record where the seal was made. The folder holds everything needed to check that load's record on any computer: the events, the seal, the public key, the timestamp, a short instructions file, and a small checker program. Once it is downloaded, nobody needs an account, an internet connection, or anything from ValveRide to check it.

Can I see all of my loads in one place?

Yes, once the shipper sign-in reaches your account. It is rolling out now and is not yet on for every account. Sign in to Custody to see every load we have recorded for your company, each with a link to its proof package. You can search the list by your load reference and filter it, for example by date. Signing in is up to you: packages still arrive by email on their own when each load closes.

Can my teammates see our loads?

Yes, once the shipper sign-in reaches your account. It is rolling out now. An admin on your company's account can add teammates by email as admin or read-only. Admins can add and remove people. Read-only teammates can see loads and download packages but cannot change who has access.

What is each file in the folder?

  • events.json: every event in the load's record, in order, with the exact bytes each event's hash was taken over. You can read each event straight out of it.
  • manifest.txt: the plain text document that was signed and timestamped. It lists the events and their hashes in order.
  • seal.json: a summary of the seal: which events it covers, which key signed it, and which timestamp authority stamped it. The checker compares every field in it against the other files, so nothing in it is taken on trust.
  • signing-key.der: the Custody public key the signature was made with.
  • timestamp.tsr: the timestamp response exactly as the independent timestamp authority returned it, with the authority's certificate inside.
  • The instructions file: step by step instructions, including how to do every check by hand with openssl.
  • The checker folder: the checker. You run cli.mjs, and the five other files in the folder support it. It needs only what comes built into Node.js, so there is nothing to install and no outside code to review.

How do I run the check?

You do not have to run anything yourself. Whoever wants to check the record (you, your insurer, or your lawyer) takes the zip downloaded from the link, unzips it, opens a terminal in the folder, and runs the one line command printed in the instructions file.

You need Node.js version 20 or later. The checker only reads the files in the folder and never connects to the internet, so it works on a machine with no network at all. If you would rather not run our code, the openssl steps in the instructions file cover the same checks with a tool you already have.

What does a pass or a fail mean?

The checker prints one line per check, marked "ok" or "FAIL", then a summary. A pass (exit code 0) means every event matches its hash, every event links to the one before it, the signature matches the Custody public key, and the timestamp was issued for this exact record. In short: nothing in the package has changed since it was sealed. A fail (exit code 1) names the check that did not hold. If the checker cannot read the files at all, it says so and exits with code 2.

Who timestamps the record, and why does that matter?

An independent timestamp authority using the RFC 3161 standard, DigiCert today, stamps each seal. The authority's name is in seal.json and its certificate is inside timestamp.tsr. The stamp shows the record existed in this exact form at the stated time, from a party that is not ValveRide. Only a 32 byte fingerprint goes to the authority, never the record itself, so it cannot see your shipment details. If the authority ever changed or shut down, existing packages would keep checking the same way, because everything needed is already in the folder.

What does a passing check not tell me?

It shows the record has not been altered since it was sealed. It does not show that the freight arrived in good shape, that every event in the record is accurate, or that nothing happened outside the record. Custody records what each source said and who said it; signing that record does not turn it into a statement about the freight. A gap in the record means unknown, never proof of anything. Whether to trust the timestamp authority is also your call: the instructions file shows how to check its stamp against the authority's own published root certificate.

Can I share the package with my insurer, my lawyer, or the other side?

Yes. Download the zip from the link and send it to anyone. Once the shipper sign-in reaches your account, teammates at your company can also be added to it. The package is self contained, so whoever receives it can run the same check and get the same result without asking ValveRide for anything.

Each seal covers the record up to the moment it was made. With automatic sealing, which is rolling out now, if events arrive after the load closes, such as a late delivery receipt, Custody seals again and emails a link to an updated package. Earlier packages stay valid for the record they cover.

Photo checks (rolling out)

Does Custody look at photos?

Photo checks are rolling out now and are not yet on for every account. Custody compares seal, BOL, and signature photos against the shipment record, one claim at a time. For example: the record says seal 0010002, so does the seal in the photo match? Each check comes back agree, disagree, or unknown.

How does Custody handle a photo it cannot read clearly?

Photo checks are rolling out now. An automated AI image check asks each question three separate times. Custody keeps agree or disagree only when all three answers are the same. A split, an error, or a timeout comes back unknown. Custody also never accepts a guessed reading, like a partly readable seal number. It only accepts agree, disagree, or unknown, so anything uncertain stays unknown. Three matching answers make a wrong answer less likely, but they do not rule one out.

What happens after a photo check answers?

Photo checks are rolling out now. A consistent agree or disagree is recorded against the shipment and can confirm that part of the record. Unknown changes nothing, and the record stays as it was. Photo checks never edit or remove earlier events. Each photo check is logged with the photo's fingerprint, the claim it was checked against, all three answers, and the time.

Status

In development. Offered by invitation.

Custody is being built with the shippers, carriers, and brokers who care what the record says before a load is taken and every time it changes hands. Tell us what you need checked at booking, and what a custody record has to show in your operation.