Skip to content

Fleet planning? 60 seconds.

The AI Engine automatically matches every transport order to the best vehicle available right now. Faster and more accurate than your entire planning team — in the time it takes them to open a spreadsheet.

AI Engine ACCURACY >99% ORDERS VEHICLES
M.01 INGEST M.02 FLEET LENS M.03 MATCH CORE M.04 POLICY LAYER M.05 REASON
FIG.02 REV 1.0 INTAKE → EXHAUST AI.ENGINE
M.01 Phase 1
M.02 Phase 2
M.03 Phase 3
M.04 Phase 4
M.05 Phase 5

ONYX AI Engine

Faza 1

Ingest

Reads and structures the load

The engine intakes loads from email, EDI, TMS, and APIs. It extracts locations, dates, dimensions, ADR, certifications — and normalizes everything into one clean structure.

  • Parses email, PDF, EDI, API
  • Geocodes and normalizes locations
  • Validates ADR and load parameters
01 / 05

AI Leadership

Built by AI experts

A team that pairs 40+ years of fleet-optimization experience with state-of-the-art ML. No tricks — just engineering we run ourselves.

  • Head of AI for Logistics

    Dr Tomasz Kaczmarek

    15 years in transport optimization. Previously designed routing algorithms for a global 3PL operator and led the ML team at Inelo.

  • Senior ML Engineer — Routing & Optimization

    Marta Sokołowska

    Specializes in combinatorial optimization for mixed fleets. Previously on the route-planning team at Eurowag and an automotive industry consultant.

  • Data Science Lead

    Piotr Lewandowski

    Builds predictive models for cost and delay risk. Previously Data Science at MAN Truck & Bus and Trans.eu.

North Star

Wyobraź sobie dostęp do każdego przewoźnika w Europie

Masz zlecenie do przewiezienia

Bez spedycji. Silnik znajduje idealnego przewoźnika.

Przewoźnik akceptuje. Realizuje. Na czas.

Bez pośredników. Bez utraty marży. Jeden system.

Frequently Asked
Questions

Does the AI replace the dispatcher?

No. The engine proposes the best choice and explains why, but the human makes the final call.

In practice, dispatchers focus on edge cases while the engine handles routine matches.

How long is implementation?

Typically 2-4 weeks. The first week connects TMS and telematics data; the rest is calibrating business rules.

Where does the fleet data come from?

From your TMS, telematics, tachograph, and service calendars. We connect via APIs or ready-made integrations (including ONYX TMS and ONYX Telematics).

What if I disagree with a recommendation?

One click swaps to an alternative. Every override is a signal back to the model — the engine learns your specifics.

Can I add my own rules?

Yes. The Policy Layer lets you define priority clients, allowed zones, required certifications, and driver assignment preferences.

Transport under control

From one truck to a 1,000+ vehicle fleet

Contact us