Signed supply chain optimization.
Every cuOpt route plan signed on-chain. NVIDIA's GPU optimization engine plus Hive's post-quantum receipt rail. Court-admissible, auditable, regulator-ready — from the moment the solver returns.
Supply chain AI without receipts is a liability waiting for a subpoena.
Optimization is now non-deterministic, GPU-bound, and changes every release. Yet the receipts shippers, insurers, customs officers, and ESG auditors demand are still PDFs. HiveLogistics replaces "the dispatcher's word" with a signed, replayable artifact — generated the instant cuOpt returns a solution.
Regulatory audit-readiness
Hours-of-service violations, ELD records, and the routing decisions that led to them are auditable for years. When an inspector asks "why did this driver take this route on Oct 4th?", a signed cuOpt receipt answers it in seconds — solver version, constraints, and chosen path, every byte attested.
Insurance subrogation
After a loss, carriers reconstruct routes to apportion blame. HiveLogistics gives insurers a deterministic chain of custody from purchase order to delivery: the route plan, the inputs that produced it, the operator who approved it, and the chain anchor that proves none of those were edited after the fact.
Customs & CBP attestation
Cross-border freight has to declare its planned and actual route at every checkpoint. Signed cuOpt receipts integrate into the C-TPAT and CBP ACE programs as machine-verifiable trade-data attestations — admissible under 19 CFR §163 record-keeping and the FRE 902(13)/(14) self-authenticating regime.
ESG reporting that holds up
Scope-3 emissions claims now require receipts the same way SOX requires audited books. Every signed route includes the chosen distance, the avoided distance vs. an unoptimized baseline, and the kg-CO2e saved — published as a verifiable artifact your auditor can replay against the GLEC framework.
Four steps. Roughly the time it takes cuOpt to solve.
The route is computed on NVIDIA infrastructure. The proof is computed on Hive infrastructure. Neither side trusts the other on faith — the cryptography does the trusting.
Submit a route problem.
Post a standard cuOpt JSON — TSP, capacitated VRP, pickup-and-delivery, or generic MIP/LP. We sign the request payload before it leaves your environment so the inputs are pinned forever.
cuOpt solves on H100.
NVIDIA Cloud Functions dispatches your problem to a managed cuOpt endpoint backed by H100 GPUs. The solver returns the optimal — or best-feasible — solution along with a deterministic objective value.
Hive signs everything.
Solution, inputs, solver binary hash, GPU class, and start/finish timestamps are bound into a single receipt and signed with ML-DSA-65 (NIST FIPS 204). The signing key is non-exportable.
Anchored on Base, forever.
The receipt hash is anchored on Base 8453 within the next block. Verifiers can replay the receipt offline at any time — no Hive servers required, no chain-of-custody to defend.
Try a 50-stop VRP.
Push 50 random stops, three vehicles, and capacity + time-window constraints to a cuOpt solver. Get back a signed solution with route legs, total distance, total drive time, and a receipt URL you can hand to a regulator.
Pay for what you sign — not for seats.
Same three-tier shape as the Hive Counsel Engine, tuned for logistics. Every plan includes signed receipts, on-chain anchors, and unmetered verification.
- Up to 500 stops per route-set
- cuOpt managed endpoint (NVCF)
- Signed receipt + Base anchor
- FRE 902(13)/(14) self-authenticating PDF
- Email + chat support
- Unlimited solves · 5,000 stops max
- Dedicated cuOpt concurrency
- SOC 2 Type II evidence room
- DOT / FMCSA + ESG report bundles
- API + Slack + webhook integrations
- 99.9% solve SLA
- Up to 50,000 stops per solve
- Reserved H100 capacity (NVCF private)
- Custom MIP / LP / column-gen problems
- SAML SSO + audit log export
- Named solutions architect
- Master Service Agreement & BAA
Three verticals where a signed route is worth more than a fast one.
HiveLogistics is solver-agnostic — the receipt is what matters. These three verticals are where the receipt is currently the difference between "we delivered" and "we can prove we delivered."
Last-mile delivery & gig fleets
For DSPs, gig delivery, and on-demand grocery — every batch of routes is signed before it hits the driver app. Disputes (missed deliveries, geofence violations, hours-of-service questions) get resolved against a single receipt rather than three contradictory dashboards.
- Hours-of-service compliance, signed per route
- Geofence + ELD telemetry receipts
- Customer SLA attestation (delivery windows)
- Subrogation-ready replay for missed scans
Cold-chain & pharma distribution
Vaccine, biologic, and specialty pharmacy routes carry FDA-track-and-trace obligations under DSCSA, plus payer-specific custody requirements. Signed cuOpt solutions integrate with temperature loggers and chain-of-custody scans to produce a single attested artifact per shipment.
- DSCSA Title II track & trace receipts
- Temperature-excursion attestation
- HIPAA-safe handling of patient stops
- FDA inspection-ready archive (10 years)
Bulk freight, intermodal & customs
Container, drayage, and cross-border freight ride a paper-thin tolerance for documentation gaps. Signed route plans tie together CBP ACE filings, FMCSA carrier identity, GLEC emissions, and the actual planned route — one receipt per consignment, replayable forever.
- CBP ACE-compatible attestation packets
- C-TPAT-aligned route & carrier evidence
- GLEC-framework emissions receipts
- FMCSA + SCAC-bound did:hive identity
Optimal, Routific, Wise Systems are routing tools. HiveLogistics is a routing tool with a receipt.
We don't claim to out-solve cuOpt — we use it. What none of the incumbents do is co-sign their output so it survives a regulator, an insurer, or a litigator.
| Capability | HiveLogistics | Optimal | Routific | Wise Systems |
|---|---|---|---|---|
| GPU-accelerated solver (NVIDIA cuOpt) | ● Native | ○ CPU only | ○ CPU only | ○ CPU only |
| Cryptographically signed solution (ML-DSA-65) | ● Yes | ○ No | ○ No | ○ No |
| On-chain anchor (Base 8453) | ● Per solve | ○ No | ○ No | ○ No |
| FRE 902(13)/(14) self-authenticating output | ● Out of the box | ○ No | ○ No | ◐ Manual |
| DOT / FMCSA / CBP report bundles | ● Yes | ◐ Partial | ○ No | ◐ Partial |
| GLEC-framework emissions receipts | ● Yes | ○ No | ◐ Partial | ◐ Partial |
| Replayable offline (no vendor server) | ● Yes | ○ No | ○ No | ○ No |
| Post-quantum signatures (NIST FIPS 204) | ● ML-DSA-65 | ○ None | ○ None | ○ None |
| Pricing transparency (no per-stop hidden) | ● Public | ◐ Quote | ◐ Quote | ○ Quote |
● = full · ◐ = partial · ○ = none. Competitor capabilities reflect public product documentation as of Q4 2026; corrections welcome at [email protected].
Eight questions every logistics buyer asks before signing.
Does HiveLogistics replace my TMS?
No. HiveLogistics sits next to your TMS the way an auditor sits next to your books. We ingest the same route problems your TMS sends to its solver and produce a signed, anchored receipt — your TMS keeps dispatching. The first integrations ship with McLeod, Manhattan Active, Project44, and Samsara feeds.
Why NVIDIA cuOpt instead of OR-Tools or a custom solver?
cuOpt is the only commercial GPU-accelerated VRP/MIP solver with a managed cloud surface (NVCF). For 5,000-stop problems it routinely returns solutions 10–100× faster than CPU baselines. Solver choice isn't ideology — when a regional DSP needs a new wave plan in 30 seconds, sub-second solves matter. cuOpt is also open source on GitHub, so the binary you sign against is the binary anyone can audit.
What exactly is in a HiveLogistics receipt?
A receipt contains: (1) a SHA3-256 hash of the input cuOpt problem JSON, (2) a SHA3-256 hash of the returned solution, (3) the solver version, GPU class, and NVCF function ID, (4) start/finish timestamps in monotonic + wall-clock form, (5) the operator's did:hive signature, (6) the Base 8453 transaction hash of the anchor, and (7) the ML-DSA-65 signature over all of the above. A reference parser ships in our open-source verifier.
Can a HiveLogistics receipt be used as evidence in court?
Yes — that's the design target. Receipts are produced as FRE 902(13) (records of regularly conducted activity certified by a qualified person) and FRE 902(14) (records generated by a process producing accurate results, with a certification from the maker of the process) self-authenticating artifacts. We provide the standing certification language and a court-grade exhibit packet on every receipt at the Operator tier and above.
What happens if cuOpt or NVCF is down?
The platform falls back to a feasibility-only CPU solver and clearly marks the receipt with solver:fallback. You never get a "silent downgrade" — every receipt cryptographically declares which solver produced it, so a court or auditor always knows what they're looking at. SLA credits apply per the Operator tier MSA.
How do you handle PII in last-mile delivery stops?
Delivery addresses are hashed and signed; the cleartext stays in your tenant boundary. Receipts ship with a Merkle commitment over the stop list, so you can later prove that a specific delivery was in the original plan without revealing the rest. The same Bloom-filter and Merkle-proof patterns we use in HiveWallet apply here.
How does ESG reporting work?
Every signed route includes the chosen distance, the avoided distance vs. an unoptimized baseline (e.g., naive nearest-neighbor or operator-submitted comparator), and the kg-CO2e delta computed under the GLEC framework with your fleet's published emission factors. The receipt is exportable as a CSRD-compatible XBRL artifact for European reporting.
What does the Gumroad SKU lineup look like?
Five SKUs, matching the Hive Civilization 5-verb taxonomy: Make ($199 DIY template), Hire ($5 single signed route), Rent ($999/mo for 50 routes/day), Lease ($9,999/yr unlimited routes), and Buy ($49,999 white-label deployment). See logistics_gumroad_skus.md for the full proposal.