Project44 vs FourKites vs Shippeo, Compared

Pick a freight visibility platform on tracking accuracy alone and you'll end up negotiating the wrong contract. For a European enterprise shipper, the binding constraints aren't dashboard polish or ETA accuracy percentages, they're GDPR exposure on named-driver location data, how deep each vendor's carrier network actually runs into Belgium, Poland, or Romania, and whether procurement can get a straight answer on price before signing a multi-year deal. This comparison looks at project44 vs FourKites vs Shippeo on exactly those terms: pricing transparency, EU data residency, and continental carrier coverage, not feature checklists.

Why this is a procurement decision, not a feature decision

All three vendors sell real-time location data tied to trucks, and in most cases to named drivers. That makes every visibility contract a GDPR matter, not just an IT integration. A platform that stores that data outside the EU, or that can't tell you where it's stored, becomes your legal team's problem the day a data subject access request lands. Separately, a shipper running freight across a dozen European countries will hit carriers who have no telematics hardware at all, particularly smaller hauliers in Central and Eastern Europe. A visibility platform that assumes GPS/ELD penetration like the US market has will leave gaps in exactly the lanes where you need visibility most.

Three criteria matter more than feature parity here:

• Pricing transparency — determines whether you can build a defensible TCO model before the RFP closes, or whether you're negotiating blind against a vendor who knows your volume and you don't know their price book.
• EU data residency and GDPR posture — determines legal exposure, especially where truck location is tied to an identifiable driver and processed by a US-headquartered entity.
• Continental carrier network depth — determines whether the platform actually sees your freight, or just the large carriers who already run modern telematics.

The three platforms, briefly

project44 is Chicago-headquartered and built around an API-first architecture, with a developer portal, documentation and sandbox environments designed to plug shipment data into ERP, OMS, TMS and WMS systems. project44 is generally aimed at mid-market and enterprise logistics operations with significant shipment volume, and its multimodal network has a particular edge in ocean freight visibility.

FourKites, also Chicago-based, built its reputation on North American road and rail. One analyst read of the market puts it plainly: FourKites is the closest direct competitor to project44 in the North American market, with network strength concentrated in North American road and rail and international coverage layered through partnerships rather than built natively. FourKites has been in Europe since 2017, and by its own account has onboarded hundreds of European carriers and integrated with top regional telematics providers, per its 2018 European expansion announcement.

Shippeo is the odd one out, and that's the point. Paris-headquartered and founded in 2014, the company has raised over $40 million and built 150+ carrier integrations serving clients including Carrefour, Saint-Gobain, and L'Oréal. It's European by design rather than European by expansion, which shows up directly in its data residency posture.

Worth noting for the shortlist: if your actual gap is carrier booking and rate management rather than pure tracking, Cargoson is a European TMS and multi-carrier connectivity platform worth an RFI alongside these three — it solves a different problem (execution, not just visibility) but shippers often discover that's the problem they actually had.

The comparison table

The pricing rows look identical for a reason. As one procurement-facing review puts it, when you visit the websites for project44, FourKites, or Vizion, you won't find a clear pricing page, because these platforms operate on a custom, enterprise pricing model. That's not a Shippeo weakness specifically, it's standard practice across the category — but it means your leverage in negotiation comes entirely from benchmarking, not from a rate card.

Where each one wins

project44: one API across every mode

Pick project44 when the same control tower has to see ocean, air, rail, and road through a single developer surface, and your freight book is genuinely global rather than Europe-concentrated. Its API-first design and ocean freight depth are the real differentiators here, not the road visibility, where FourKites and Shippeo both compete harder.

FourKites: North America-anchored with a European tail

FourKites makes sense when your network's center of gravity is North American road and rail and Europe is a secondary lane set rather than the core business. Reviewers consistently note it's often more responsive to mid-large North American shippers, with the international and ocean story being the gap most frequently raised in competitive evaluations. Its published GDPR data transfer agreement is a genuine procurement asset: it's on the table for your legal team to review before you sign, not something you have to request and wait for.

Shippeo: continental Europe, data residency as a hard requirement

Shippeo wins outright when GDPR and data residency are non-negotiable procurement criteria rather than nice-to-haves. It was named a Leader in the 2025 Gartner Magic Quadrant for the second consecutive year, and is GDPR compliant, ISO-certified, and trusted by global companies such as Renault Group, Coca-Cola HBC, Carrefour Belgium, and Leroy Merlin. If your freight is predominantly intra-European and your legal team wants to see EU-only storage in writing rather than inferred from a privacy policy, Shippeo is the only one of the three that states it outright on a dedicated security page.

What none of the three solve

All three are visibility-only products. They sit on top of your existing stack and tell you where freight is; none of them plan, book, or tender it. For a mid-market shipper juggling a TMS, an ERP, and a visibility layer, that's a third system to govern, a third vendor SLA to track, and a third contract renewal date to calendar. Budget for a separate execution layer and treat the visibility contract as a bolt-on, not a TMS replacement — the two decisions have different owners, different scoring criteria, and should never be bundled into one RFP if you want clean accountability later.

Verdict

Choose Shippeo if your freight is predominantly intra-European and GDPR/data-residency is a hard contractual requirement, not a preference. Choose FourKites if your network is North America-anchored with a European tail, and road and yard visibility matter more than ocean depth. Choose project44 if your book is genuinely global and multimodal, with ocean as a meaningful share of volume, and a single developer-facing API across all modes is the priority. None of the three replace a TMS — if execution and carrier booking are the actual gap, evaluate a carrier-connectivity platform like Cargoson in parallel rather than stretching a visibility contract to cover a job it wasn't built for.

Procurement checklist before you shortlist

• Get the GDPR Data Processing Addendum or Data Transfer Agreement on file and reviewed by legal before the demo stage, not after the contract is drafted.
• Confirm in writing where personal data (driver location, named-driver ELD feeds) is physically stored, not just where the vendor is headquartered.
• Ask for the percentage of your named carriers already onboarded to the platform, by country, not as a global aggregate number.
• Get the implementation week-count written into the contract as a milestone with penalties, not as a verbal estimate from the sales team.
• Negotiate the exit and data-export clause before signing, including what happens to historical shipment data if you switch vendors at renewal.