Thruster

A B2B logistics control tower whose byproduct is a linked order-to-delivery event stream for Mexico/LatAm import freight: purchase orders tied to specific containers, multi-leg routing (sea arrival at Manzanillo / Veracruz, then drayage/truck legs to Guadalajara, Monterrey and León), container and shipment status events with ETA and delay flags, customs-clearance and document-completeness state (pre-alerts, missing packing lists, clearance blocks), detention/demurrage risk events, and last-mile delivery evidence — plus, on the forwarder product, quote-to-leg-to-margin economics per shipment.

Open buyer room →

Sample

Brickroad customers

Sample this dataset before you buy it.

Your sourcing agent asks Thruster and files the sample in your catalog — private to you.

Start 7-day trialNothing is charged until the trial ends.

Coverage

Universe, instruments and categories.

Industry: Marine ShippingApplication Software
Instruments: equities
Categories: Alternative

Dataset card

Type: not stated
Format: Event-stream / tabular — status events per container and per PO with timestamps, port and leg assignments, document and clearance state flags, and alert records; served through a SaaS control-tower dashboard with analytics
Volume: Currently modest and explicitly early-stage: ~87 containers in transit with ~471 orders in the compliance window on the displayed account. Extrapolating a young multi-account control tower, the cumulative event corpus is plausibly 10^5-10^6 status/document events (GBs, not TBs) — dense per shipment but narrow in absolute count.
Users: Est. 20-150 enterprise accounts (importers, manufacturers, forwarders) with perhaps 200-1,000 seats — a self-serve 30-day free pilot plus a Starter tier for smaller volumes implies a long tail of small accounts on top of a few enterprise pilots
History: 2 years
Update frequency: not stated
Growth: Active but early — the product is live with a self-serve 30-day pilot, published tiering including a Starter plan, and current marketing aimed at the nearshoring wave; the low in-platform container counts indicate pre-scale rather than maturity
Launched: ~2024-2026 — a 'Logistics Visibility 4.0' positioning, a free-pilot self-serve motion and an explicitly nearshoring-led pitch all mark a recent launch; the operating entity's registered vintage is consistent with a post-2023 build
Delivery: not stated
Entity mapping: not stated
Sample: not stated
Point-in-time: not stated
Licence: not stated

supplier index read from their site