Transport & Logistics

The corridor is being built. The visibility has to keep up.

Vehicles, trailers, containers and last-mile teams in one operating picture.

Request a Demo

Tell us about your operation. A specialist will get back to you to arrange a demo.

Explore solutions
Who we work with
Carriers, 3PLs, distributors and last-mile operators
Typical estate
Mixed fleets, reefers, yards and depots
Where it starts
One depot, one fleet, live in weeks

/ The context /

Why this sector, why now.

Saudi Arabia is rebuilding itself as a logistics corridor, and the operators moving through it are being asked for a level of proof their systems were never designed to produce. Clients want live status. Regulators want records. Finance wants cost per kilometre. All three questions are asked of the same trip, and they are usually answered by three different exports.

IoT Cube connects vehicles, trailers, containers, cold units and last-mile teams into one operating picture — the one the client asks for, the one the auditor inspects, and the one dispatch actually needs at six in the morning.

  • 01A national logistics ambition

    The National Transport and Logistics Strategy aims to make the Kingdom a regional hub. Operators on those corridors are expected to run to a higher standard of visibility and reliability than before.

  • 02Clients now ask for proof

    Shippers and government buyers increasingly want live status and a trip record, not a phone call. Contracts are starting to be won and lost on the quality of evidence.

  • 03Margins under steady pressure

    Fuel, labour and compliance costs keep moving while rates are negotiated hard. Cost per kilometre has to be known by vehicle and by route, not estimated at month end.

/ The challenges /

What the operation is up against.

01

Three systems answer one trip

Telematics, the TMS and fuel cards each hold part of the story. Reconciling them takes hours, and the answer is out of date by the time it arrives.

02

Idle assets look busy

Trailers and containers sit in yards for days without anyone noticing. Utilisation is guessed, and new equipment gets bought to cover capacity already owned.

03

Cold loads arrive without evidence

A reefer can hold temperature all trip and still lose the claim, because the record is a printout or a gap. The dispute is about proof, not product.

04

Driver behaviour is seen too late

Speeding, harsh braking and fatigue show up after an incident, not before. Safety teams review footage when the conversation should have happened weeks earlier.

/ What we connect /

The whole estate, on one record.

Whatever the brand, protocol or supplier — joined to the systems that already run the business.

On the road

  • Tractor units and rigid trucks
  • Light commercial vans
  • Fuel and driving behaviour
  • Dashcams and driver ID

Behind the cab

  • Trailers and flatbeds
  • Reefer units
  • Containers
  • Door and load sensors

In the yard

  • Yard and depot assets
  • Gate movements
  • Forklifts and handling equipment
  • Charging and fuelling points

Systems of record

  • TMS
  • ERP
  • Fuel card platforms
  • Customer portals
  • Handheld proof of delivery

/ By role /

One platform. Four different questions answered.

Operations director

Which vehicles are earning today, and which are just moving?

  • Utilisation by vehicle, route and customer in one view.
  • Idle and underused assets flagged before the next purchase.
  • Exceptions routed to dispatch while they can still be fixed.

Fleet manager

What will break next, and when do I pull it off the road?

  • Service due by distance and engine hours, not calendar.
  • Fault codes surfaced as work orders, not dashboard lights.
  • Downtime tracked per asset with a clear history.

HSE manager

Which drivers need a conversation before something happens?

  • Driver scorecards built from real driving events.
  • Fatigue and speeding trends by driver and route.
  • An incident record that stands up to review.

Commercial lead

Can we show the client exactly what happened on that trip?

  • Shareable trip records with time, location and temperature.
  • Delivery performance by customer, ready for the review.
  • Evidence that supports claims instead of arguments.

/ How we engage /

From first conversation to the whole estate.

  1. 1

    Map the operation

    We sit with dispatch, fleet and finance to agree the questions that matter and the assets, systems and depots in scope.

  2. 2

    Pilot one depot

    Connect a defined fleet and its yard. Devices go in, data flows to the console, and the first exceptions reach the right people.

  3. 3

    Prove the numbers

    Review utilisation, fuel, safety and delivery evidence against the baseline. Agree what worked, what changes, and what to extend.

  4. 4

    Scale across the network

    Roll out depot by depot, integrate the TMS and ERP, and hand over reporting that runs without us in the room.

/ Compliance /

The record the regulator asks for, produced as you operate.

Confirm the exact format your authority requires and we map the export to it.

  • 01Transport General Authority & WASL

    Vehicle and trip data is structured so operators can maintain the records the Transport General Authority expects, with WASL-aligned tracking designed to support fleet compliance obligations.

  • 02NCA Essential Cybersecurity Controls

    Platform controls, access management and logging are designed to support alignment with the NCA Essential Cybersecurity Controls, with data hosted inside the Kingdom.

  • 03Personal Data Protection Law (PDPL)

    Driver and delivery data is handled with role-based access and retention settings designed to support PDPL obligations overseen by SDAIA.

/ Security & sovereignty /

Sovereign is a place, not a promise.

In-Kingdom residency

Data stored and processed inside Saudi Arabia, on infrastructure you can name in a tender.

Built to national controls

Designed to align with NCA cybersecurity controls and the Personal Data Protection Law.

Isolated by tenant

Tenant isolation, role-based access and a full audit trail across users, actions and devices.

Your cloud or site

Deploy into a sovereign cloud, your private cloud or on-premises without becoming a different product.

Read the data residency statement →

/ Questions /

Frequently asked.

Can we keep our existing trackers?

Often, yes. IoT Cube is device-agnostic and can ingest data from many existing telematics units. We assess what you have first and only recommend replacing hardware where it cannot deliver the data you need.

What happens on routes with poor coverage?

Devices store data locally when the network drops and send it when coverage returns. The trip record stays complete, and gaps are marked clearly rather than hidden.

Does it integrate with our TMS and ERP?

Yes. We connect through APIs and standard integration patterns so trips, assets and costs line up with your systems of record. Integration scope is agreed during the pilot, not assumed.

Where is our data hosted?

Inside the Kingdom. IoT Cube is built as a sovereign platform, so operational and driver data stays in Saudi Arabia under controls designed around local requirements.

How big should a pilot be?

Big enough to answer a real question, small enough to move quickly. Usually one depot or one customer contract, with a clear baseline and agreed measures of success.

Bring us the decision that takes too long today.

Start with the problem. IoT Cube provides the foundation underneath.

Request a Demo

Tell us about your operation. A specialist will get back to you to arrange a demo.