Post-Montgomery v. Caribe Transport II

The independent records layer for carrier selection.

FreightGrid captures tamper-evident, hash-bound, contemporaneous records of every carrier selection decision your brokerage makes — composing whatever data sources you trust into a single defensible legal asset. Not another vetting platform. Not another scoring engine. The records layer.

Composes your existing data subscriptions
FMCSA Highway DAT CarrierWatch Tea Technologies Bluewire Carrier411 GenLogs
The Problem

On May 14, 2026, the Supreme Court turned every carrier selection into a discoverable record.

The federal preemption shield is gone. Brokers can now be sued in state court for negligent selection of motor carriers. The Court did not define the standard of care — that will be tested, load by load, in depositions and jury trials over the coming decade.

Montgomery v. Caribe Transport II — 9-0, May 14, 2026
"The Federal Aviation Administration Authorization Act does not preempt state-law negligent-selection claims against motor-carrier brokers."

Defense lawyers are now uniform on the operational response: contemporaneous documentation of every carrier selection decision is the broker's litigation defense. The vetting record produced before the load moves is the evidence at trial three years later. A reconstructed story from recollection is not.

What FreightGrid Is

The records layer for whatever data sources you already use.

FreightGrid is not a vetting platform, a scoring engine, or a carrier intelligence database. We do not compete with Highway, DAT, Tea Technologies, or Bluewire. We compose them — and the federal FMCSA baseline — into a single contemporaneous, hash-bound legal record per load.

01 / SELECT YOUR SOURCES

Bring your own data.

FMCSA is the baseline. Plug in whatever commercial sources you already pay for — Highway, DAT, Tea, Bluewire, GenLogs, your internal blacklists. We don't resell their data. We capture what each one returns at the moment of selection.

02 / REP MAKES THE DECISION

Your team, your policy, your call.

Each rep sees the composed view at the moment of carrier selection. They apply your written policy. If a threshold is crossed, they capture the override rationale and the named approver. We don't decide for them — we document what they decided.

03 / RECORD IS PERMANENT

Hash-bound. Append-only. Yours forever.

Every Vetting Event is SHA-256 hashed at capture, bound to your written policy version, and written to an append-only audit log. No path exists to modify it after the fact. When the subpoena arrives, you produce the record.

Why FreightGrid

Independence is the structural property that makes records defensible.

Your data sources have commercial interest in their own carrier networks. Your TMS has commercial interest in keeping you using their workflow. The records of your decisions cannot be defensibly maintained by parties with skin in the game.

Independent by design
FreightGrid has no commercial relationship with any data source. We don't earn per-query commissions, per-carrier referral fees, or revenue share from any data provider. Your records are independently maintained by a non-party with no financial interest in the carriers being vetted.
Multi-source neutral
Highway can't include DAT data. DAT can't include Highway data. Neither can include Tea or Bluewire. We can include all of them. The defense narrative is materially stronger when the broker can produce records showing federal, identity-verification, and authority-monitoring sources were all queried at the moment of selection.
Attorney-reviewed
Every customer's Foundation Policy is reviewed by qualified transportation-defense counsel before records are relied upon in production. The legal artifact that records bind to is itself the subject of legal review. Records produced under an attorney-endorsed framework carry different evidentiary weight than records produced under a vendor's marketing claims.
Tamper-evident architecture
Every Vetting Event is SHA-256 hashed at capture across the full payload — data, policy version, decision, named rep, named approver, load reference, timestamp. Any subsequent modification produces a different hash. Append-only Postgres storage means there is no modification path. Standard infrastructure pattern from financial-services audit logs, applied to broker carrier selection.
Records-only revenue
We don't sell carrier scoring. We don't sell identity verification. We don't sell load board access. Our revenue comes from one place: the records-layer service. That focus is the moat. Anyone can build a hash chain. Nobody can build a hash chain that's also independent of every data source in the market unless that's their entire business model.
Pricing

Built for brokerages of every size.

Three tiers. Records are the product across all of them. Choose the level of data composition and operational tooling that fits your brokerage.

FOUNDATION
Records Foundation
For small brokerages establishing the legal defense baseline.
$1,500 one-time
  • Attorney-reviewed framework, ready for adoption by your counsel
  • FMCSA baseline integration
  • Single-tenant cloud deployment
  • Up to 5 reps
  • 1,000 vetting events / month
  • Hash-bound append-only records
  • One-year retention; export on termination
PLATFORM
Enterprise Platform
For large brokerages and agent networks.
Custom · $2,500/mo+
  • Everything in Managed
  • Multi-tenant for agent networks
  • API access for TMS integration
  • SSO + role-based access control
  • Custom policy variants per agent
  • Dedicated counsel-review program
  • SLA-backed uptime + dedicated support
  • Records-format consulting for litigation prep

The first wave of post-Montgomery negligent-selection suits is being filed now.

A vetting record produced contemporaneously is the broker's defense. A vetting story reconstructed from recollection is not. The window to put records infrastructure in place is the window before the first subpoena.