Product line 03

SPV Factory

DIBS Freight decides and proves what happened. SPV Factory isolates the approved economic exposure, its governance, and its records — and never moves money on its own.

Vehicle types, in priority order

Each vehicle only accepts instructions backed by the evidence its programme requires.

VehiclePurposeEvidence binding
Recovery Capacity SPVContracted standby assets — hotshot, cross-dock, reefers, fuel, air charterIncident confirmation, vendor quote, proof of service
Freight Asset SPVOwn or lease tangible assets — trailers, generators, chassis, edge hardwareUtilisation logs, maintenance records, insurance
Receivables SPVPurchase or finance eligible freight invoicesPOD, rate confirmation, identity and banking checks, dispute clearance
Parametric Protection SPVPeril-specific triggers — port delay, temperature excursion, theft, hurricaneMulti-source oracle rules, freshness limits, dispute process

Factory capabilities

  • Vehicle creation — Delaware LLC series or standalone.
  • Programme configuration — purpose, assets, counterparties, limits, geography, lifespan.
  • Approval policy — manager, finance, risk, dual approval.
  • Separate records — ledgers, documents, expenses, assets, liabilities.
  • Capital and exposure register — reserve, commitments, deployed capital, losses, concentration.
  • Contract administration — vendor, servicing, reinsurance.
  • Evidence binding — shipment, POD, trigger, invoice, recovery action.
  • Reporting and controlled wind-down.

Integration flow

An instruction is authorised inside the factory; execution always sits with a regulated partner.

DIBS Freight
  → validates carrier, shipment, risk, fraud, operational event
  → emits signed Evidence Package

SPV Factory
  → checks vehicle eligibility, reserve, exposure, authority, contract policy
  → creates authorised instruction (not self-executing funds movement)

Regulated partner (bank, insurer, fund admin)
  → executes custody, payment, lending, insurance
  → returns settlement confirmation

Audit Ledger
  → records request, evidence, policy version, approval, partner result

Evidence package

{
  "packageId": "ep_01J...",
  "sourceSystem": "dibs-freight",
  "vehicleId": "spv_recovery_dfw_2027",
  "eventType": "APPROVED_EMERGENCY_RECOVERY",
  "shipmentId": "shp_12345",
  "carrierRiskDecisionId": "risk_456",
  "incidentId": "inc_hurricane_001",
  "requestedAmountUSDc": 18000,
  "authorityPolicyVersion": "recovery-v3.2",
  "evidenceHashes": ["sha256:telematics...", "sha256:weather..."],
  "requiredApprovals": ["OPS_COMMANDER", "FINANCE_APPROVER"],
  "createdAt": "2026-08-27T22:17:00Z"
}