Market Trends
What is a Neocarrier?
Fleet and software as one system.
A Neocarrier is a logistics operator that builds its fleet and its software as one system, under single ownership. Here's what the term means, why it's different from a carrier, a broker, or a fleet-software vendor — and why we coined it.
Samuel Jones
•
What is a Neocarrier?
A Neocarrier is a logistics operator that owns both its fleet and the software that runs it, built as a single system rather than two separate layers. Because the same company controls the vehicles and the technology coordinating them, a Neocarrier generates verified operational data — distance, routing, timing, emissions — as a direct byproduct of the delivery itself, rather than estimating it afterward or stitching it together from third-party tools.
It's a new category, and at the moment a small one. We coined the term because we kept describing what we were building and finding that none of the existing words fit. "Carrier," "broker," "third-party logistics provider," "freight-tech platform" — each captures a piece of it, but none captures the whole. So we named it. Dubs is the first Neocarrier; we don't expect to be the last.
What makes a Neocarrier different
The clearest way to define a Neocarrier is by what it isn't. There are four models people tend to confuse, and the difference comes down to a single question: who owns the vehicles, and who owns the intelligence layer that runs them?
A traditional carrier owns and operates vehicles. Its job is to move goods, and it does that well — but technology, where it exists, is administrative rather than an integrated part of the operation. Operational data like emissions is produced after the fact, estimated from averages, or not produced at all.
A broker or freight-tech platform is the mirror image. It owns software and a network, but no vehicles. It coordinates other people's vehicles — matching loads, optimising routes on paper — but it has no direct control over the physical operation, and no direct line to the primary data that operation generates.
Fleet-management and ERP software — telematics, route planning, logistics ERPs — is a third thing again. This is software sold to carriers: a layer bolted onto an operation the vendor doesn't own. The software company owns no vehicles; the carrier owns the vehicles but not the software. The physical layer and the digital layer belong to two different parties. That seam is precisely where data integrity tends to break down — because no single entity is accountable for both the movement and the record of it.
A Neocarrier collapses all of this into one. It owns and builds both the fleet and the software, as a single system, under one operator. There's no seam between the operation and the intelligence layer, because the same company owns both — and that single point of ownership is the whole idea.
Why the model exists
This isn't a distinction for its own sake. It changes what the operator can actually promise.
When one company controls both the vehicle and the system recording what it does, the data that operation produces is trustworthy by construction — it comes from the actual movement, with a clear trail behind it, rather than being reconstructed later or reconciled across three vendors' tools. There's no chasing a subcontractor for numbers at year-end, and no gap between what happened on the road and what the software says happened. For anything that depends on verifiable operational data — audit-ready emissions reporting under CSRD, customer tenders asking for per-shipment figures, real-time visibility — that single-ownership structure is what makes the promise hold.
The model matters most where operations are dense and complex: city logistics, many stops, mixed vehicles, short legs. That's exactly where estimated data is bluntest, where coordination between separate parties breaks down most often, and where the pressure for verified, real-time information is highest. It's also, not coincidentally, where Dubs operates.
Dubs is the first Neocarrier — a full-stack city-logistics operator built so that the fleet and the software are one system from the start, rather than a carrier with tools added on or a platform coordinating vehicles it doesn't run. The category is new, but the reason for it is simple: the old words described a way of working that no longer matches what city logistics actually needs.
