Broadpath Logistics is a Canadian company building an AI-powered logistics platform — multimodal tracking, predictive ETAs, trade intelligence and carbon accounting — for the teams who actually have to move things, on schedule, without burning a Tuesday afternoon on five carrier portals.
The shipping industry runs on a strange paradox. Every container has a satellite up there reporting its vessel's position every two minutes. Every carrier has a database with the gate-in time, the loaded time, the discharge time, the customs status. And every operations team spends half its day chasing that data through five different portals because the people who own the systems aren't the people who need the answers.
Broadpath was started by people who'd been on the operator side — forwarders, brokerages, the importers and exporters who pay the bills and bear the risk. The pitch is simple: aggregate it. Stitch it. Show it. Carrier APIs in, AIS in, port indexes in, one clean timeline out. No more "let me check Maersk, then MSC, then the terminal site, then the satellite tracker."
"If your tracking system makes you switch tabs, it's not tracking. It's bookkeeping with extra steps."
We're a small team — engineers, ex-forwarder ops, a designer — building in public on a deliberately small infrastructure footprint. Postgres. Node. Caddy. A few well-chosen API partnerships. We don't think the answer to container visibility is more meetings; we think it's a couple of well-designed REST endpoints and a fast UI.
Broadpath is built in Canada, incorporated in Toronto, with infrastructure in Nuremberg (closer to the European trade lanes where most of the AIS firehose originates). Customers are mostly in North America and Europe, with a growing slice in the Gulf and Southeast Asia.
Carriers, AIS networks, port authorities — they all publish data. Our job is to stitch it together cleanly. We're not in the business of duplicating what already works; we're in the business of removing the friction between you and it.
Live data tells you what's happening. Historical data tells you what happened, why it slipped, who owes you a credit. We keep history indefinitely — even after polling ends, because the dispute always comes after the credit window has closed.
Every event we ingest, every position we capture, every charge that lands — it should be in the dashboard, with a timestamp, queryable. Most "visibility" platforms summarise to a fault. We surface what happened and let you decide what it means.
Most container "visibility platforms" are CRMs with a tracking module bolted on, three sales reps, and a managed services tier. We are something different.
Broadpath is a pipeline. Carrier APIs and AIS streams come in one side; a queryable timeline comes out the other. Everything in between is a queue, a worker, and a Postgres table.
Snapshot at end of Q1 2026. Updated quarterly.
Broadpath is remote-first. The legal company lives in Toronto; the servers live in Nuremberg, where the European AIS firehose has the shortest hop.
Broadpath Logistics Inc. is a Canadian corporation. Customer contracts, hiring, billing, and the people who answer the phone all live here. There is no walk-in office — we're remote-first across Eastern Time.
The platform runs on a single Hetzner box in Nuremberg — close to the European AIS aggregators where most of the firehose originates. Cloudflare in front, Postgres on the box, Caddy doing TLS. Boring infrastructure, on purpose.
No call centre, no offshore support team. The person who writes the code is the person you email when something breaks.
15+ years building data pipelines and B2B logistics tools. Writes most of the core platform.
Former forwarder ops manager at a mid-size North American 3PL. Knows what breaks and why customers care.
Wakes up every 60s, walks the queue, hits the carriers, writes the events. Filed 482,109 events last quarter. Never complains.
But we'd rather know you exist before we open a role. If you've worked freight ops, written carrier integrations, or built logistics dashboards that actually got used — drop us a line.
There's no chatbot. There's no offshore tier-1 routing email replies through a Zendesk queue. You email [email protected] and a person who knows the platform writes back, usually within a few hours.