For years, real-time fleet tracking meant one thing: buy devices, install them on every vehicle, manage them for years. OBD plug & play devices, CAN bus integrations, standalone GPS trackers — variants of the same logic: aftermarket hardware installed at your expense to extract data the vehicle was already producing but kept locked behind a manufacturer’s proprietary app.
In 2026, the question is no longer “which device do I buy?”. It’s “can I track my fleet in real time without installing hardware?”. The answer is yes, and the mode is called Cloud OEM.
This guide explains how it works, which vehicles are compatible, what it costs, and — above all — who it’s right for and who it isn’t. Written for European fleet managers evaluating whether to switch to Cloud OEM or stay on OBD, and for anyone wanting a panoramic view before diving into operational detail.
What “fleet tracking without hardware” means
Technically, fleet tracking without hardware is the mode in which the vehicle’s telematics data (position, consumption, mileage, battery state, driving parameters) reaches the fleet management system directly from the manufacturer via cloud, without any aftermarket device installed on the vehicle.
Modern vehicles — most post-2019 models — leave the factory with integrated hardware connectivity: a SIM card, a telematics module, a GPS antenna. From that moment onwards, the vehicle continuously transmits data to the manufacturer through its own network (or through partner telco operators). That data feeds the manufacturer’s app (e.g., Stellantis Connect, VW Connect, FordPass) and the telematics services the manufacturer sells.
Cloud OEM unlocks that data for third-party providers. With the consent of the fleet owner or user, in compliance with the EU Data Act, the manufacturer transmits the same data to a service provider you’ve chosen — Optivo, another fleet management system, a predictive maintenance platform. You access your data on a dashboard you control, integrated with the rest of your workflow.
Nothing to install. No cabling. No workshops. You activate a vehicle by adding the VIN.
Why in 2026 it’s a concrete choice (and it wasn’t in 2024)
Three things changed in 2024-2026 and turned tracking without hardware from experimental into operational.
First: the EU Data Act has been applicable since 12 September 2025. Regulation (EU) 2023/2854 has transformed access to vehicle data from manufacturer concession into the right of the owner or user. Before the Data Act, accessing data without aftermarket hardware was theoretically possible but operationally hard — it depended on bilateral commercial partnerships between third-party providers and individual manufacturers. After, it’s an enforceable right with defined timing and modalities.
Second: manufacturers have structured the offering. Stellantis has created Mobilisights, an autonomous group company dedicated exclusively to managing telematics data for third parties. Volkswagen Group has opened its data portal with API access. Ford Pro has built in-house a software team for fleet integration. In 2024 this infrastructure was only partly in place; in 2026 it’s operational and scalable.
Third: the share of post-2019 vehicles in fleets has grown. In 2022, most European commercial fleets still had a significant share of pre-2019 vehicles (for which Cloud OEM doesn’t work). In 2026, for most professionally managed fleets, the share of natively connected vehicles exceeds 60-70%.
Result: a mode that in 2024 was “interesting but marginal” in 2026 is the default choice for the connected part of the fleet. The question is no longer “if” but “how”.
Which vehicles are compatible
Cloud OEM compatibility depends on two variables: the manufacturer and the model year.
Supported manufacturers in 2026
Automotive groups that have made their data feed available via Cloud OEM as of 2026:
- Stellantis (via Mobilisights): Fiat, Peugeot, Citroën, Opel, Jeep, Alfa Romeo, Lancia, DS Automobiles, Maserati, Vauxhall — broad coverage, structured process, detailed guide on the Mobilisights process.
- Volkswagen Group: Volkswagen, VW Commercial Vehicles, Audi, Skoda, SEAT, CUPRA, Porsche.
- BMW Group: BMW, MINI.
- Mercedes-Benz: Mercedes-Benz.
- Renault Group: Renault, Dacia.
- Hyundai Motor Group: Hyundai, Kia.
- Toyota: Toyota, Lexus.
- Ford.
- Volvo Cars and Polestar.
- Tesla.
- Nissan.
That’s 30+ brands across 12 automotive groups. The list grows month over month — groups like Mazda, Honda, Subaru are in the roadmap for integration in 2026-2027.
Model year: the key filter
The most stringent filter is model year. With isolated exceptions, Cloud OEM works on MY 2019 and later. The reason is that hardware connectivity (telematics module + SIM card + antenna) became standard on popular-segment commercial and personal vehicles from that model year — before, it was optional or only present on premium models.
For a typical fleet at a 2026 European logistics company, this means most post-2019 commercial vans are compatible — practically all Fiat Ducatos from 2021, all Peugeot Boxers from 2022, all Mercedes Sprinters from 2023.
Pre-2019 vehicles remain in the perimeter of aftermarket OBD — they’re cheap to install, still trackable, and for a fleet with 1-2 residual old vehicles it’s not a problem to maintain a mix of modes.
What you can get (and what you can’t)
Cloud OEM gives access to the data the vehicle produces natively and transmits to the manufacturer. Concretely, the dashboard receives:
- Real-time GPS position — the same data the manufacturer uses for its app
- Actual mileage — read directly from the vehicle odometer, not estimated
- Fuel or energy consumption (for EVs) — native readings, accurate
- Vehicle status — doors, ignition, fuel level, battery state
- Driving parameters — speed, acceleration, braking, dangerous events (for manufacturers that expose them)
- Diagnostic codes and alerts — maintenance, specific alerts (the basis of fleet predictive maintenance)
- EV battery state — SoC, SoH, charging cycles (for electric vehicles)
What you don’t get with Cloud OEM:
- Remote engine immobilisation — anti-theft function requires CAN bus + installed device
- Trade-specific telemetry — multi-zone temperature for cold chain, refrigerated door opening, on-board weight for trucks (these require dedicated CAN bus sensors)
- Data on pre-2019 vehicles — outside the compatibility perimeter
- Separate sub-driver tracking — if multiple drivers alternate on the same vehicle, Cloud OEM typically ties data to the vehicle, not the driver (badge/identification at driver-app level is needed for that)
For the vast majority of cases of a standard commercial fleet — distribution, deliveries, field services, sales — Cloud OEM data covers 100% of operational needs. For specialist cases (cold chain, high-value anti-theft, heavy-vehicle telemetry) CAN bus remains the right mode on that part of the fleet, often in mixed mode with Cloud OEM on the rest.
What it costs vs aftermarket OBD
Cloud OEM pricing is not public — it’s negotiated per customer and depends on number of vehicles, manufacturers involved, data package requested, contract duration. Order-of-magnitude indications for the European market in 2026, based on industry benchmarks:
- Per vehicle per year (Cloud OEM, standard operational package): typically €80-150, comparable to a complete aftermarket OBD
- Upfront hardware: zero (vs €80-200 for OBD)
- Installation: zero (vs 30-60 min per vehicle + workshop costs for OBD)
- Hardware maintenance: zero (vs device replacements, batteries, accidental disconnections for OBD)
- Vehicle change handling: update the VIN from the dashboard (vs uninstall/reinstall for OBD)
On a fleet of 25 connected vehicles active for 5 years, the cumulative difference between Cloud OEM and aftermarket OBD is on the order of €5,000-15,000 in Cloud OEM’s favour — significant savings, but not spectacular. The real value of Cloud OEM is frictionless scalability: when a new vehicle comes in, you activate it in days, not weeks. On high-turnover fleets this is the main operational gain.
Who it’s right for in 2026
Combining technical, contractual and economic criteria, Cloud OEM in 2026 is the natural choice for:
- Mid-sized fleets (10-100 vehicles) with most vehicles post-2019
- Fleets on operational lease or long-term rental where turnover scalability is frequent — 5 contractual points to verify before signing
- Multi-brand-fleet companies with three or four separate manufacturer apps wanting to consolidate into a single dashboard
- Companies transitioning to electric needing native data on battery state, energy consumption, charging cycle — Cloud OEM gives first-quality data without needing to install EV-specific sensors
- Fleets operating across multiple EU countries — Cloud OEM is the simplest mode to scale across borders
And who it’s not right for (or not alone):
- Predominantly pre-2019 fleets — no native data to grab, OBD remains the path
- Operators needing remote engine lock or integrated anti-theft — CAN bus required
- Cold chain, heavy transport with trade-specific telemetry — CAN bus with dedicated sensors required
- Very small fleets (1-5 vehicles) where Cloud OEM contractual setup doesn’t pay off vs a single plug & play OBD
How to start (in 4 practical steps)
If your fleet is a Cloud OEM candidate, here are the four operational steps.
First: census. For each vehicle, gather the VIN, model, year. An Excel sheet does the job. For 20-50 vehicles, it’s 1-2 hours of work.
Second: coverage verification. A serious Cloud OEM provider (Optivo does this in scoping) checks VIN by VIN which are actually covered by Mobilisights / VW portal / the relevant manufacturer portal. Output: list of vehicles activatable today, vehicles requiring additional checks, vehicles outside coverage.
Third: consent chain clarification. If the fleet is on lease, verify the contract: user recognised as Data Act “user”? Data access clauses? Constraints on third-party providers? If anything is ambiguous, clarify with the leasing company before activating.
Fourth: activation. Through the Cloud OEM provider, the formal process starts with the manufacturers. Typical timing: 3-10 business days for immediately activatable vehicles, a few weeks for those needing contractual integrations. Data arrives in the dashboard as activations close.
To take the first step — understand how many of your vehicles are candidates and how many aren’t — request a free VIN census. It’s an analysis requiring a few hours of our work and returns a clear picture on which to decide whether to proceed or not. See what we support on Cloud OEM for operational details, or book a demo.
The future: zero hardware as standard
The underlying trend is clear. By 2028, according to industry projections (Berg Insights, IDC Automotive), over 80% of commercial vehicles in circulation in the EU will be natively connected and accessible via Cloud OEM. Aftermarket OBD will continue to exist for specialist cases and older vehicles, but will be the minority mode.
For anyone managing a fleet today, in 2026, the option is no longer “if” to switch to Cloud OEM, it’s “when” and “which part of the fleet first”. The right answer depends on your fleet composition, existing contracts, and specific operational needs.
But one thing is certain: continuing to install aftermarket hardware on a new 2026 Fiat Ducato, when the same data is available in the cloud without installing anything, is a choice that requires a very specific justification. The default mode is changing.
Read next: Three ways to connect your fleet — Plug & Play OBD, CAN bus integration for advanced telemetry, or Cloud OEM without devices. The three modes combine within the same platform; the point is choosing the right combination for your fleet.
Comparing providers? See the hardware-free fleet tracking alternatives: an honest comparison between Optivo and the other Cloud OEM players (Geotab, Webfleet, Samsara, MICHELIN Connected Fleet, Moving Intelligence).
In the glossary: Hardware-free fleet tracking · Cloud OEM