Comparisons· Last updated 2026-09-21

Jev versus logistics dispatch: a practical comparison

Logistics dispatch solves assignment and routing under constraints. Jev does not minimize miles. It can label a driver or customer exception note.

Independent. Official: keep numeric optimization in code. docs.typesafe.ai.

Comparison scope

ETAs, capacity, and VRP stay solvers. “Customer says gate code changed and dock is blocked” is a Choice over exception types.

Criteria that decide the architecture

Decision quality and control

A wrong exception class delays a truck. Use unknown and a human dispatcher on low confidence. Do not ask Jev which stop is closer.

Integration trade-offs

TMS exception webhook → note text → Jev → reason code → solver or human. Pin the model.

TypeSafe’s public models page lists jev-1.13 at $0.042 per million input tokens with output tokens free — a vendor claim, not a jev.pro measurement. Confirm on the models page before you bid.

When each approach fits

Prefer Jev when

• Free-text exceptions at volume

Prefer Logistics dispatch when

• The hard problem is the route

Solver dispatches; Jev labels stories; dispatchers handle unknown.

Dispatcher still owns the radio

A wrong exception class is recoverable if unknown exists. A Jev-picked driver assignment is an optimization fantasy. Keep VRP in the solver.

What this page does not claim

• Not a TMS replacement.

• Schema-safe output is not the same as factual correctness.

• No independent bake-off numbers live here.

FAQ

Can Jev pick the driver? Not as an optimization. Maybe a policy Noul (“needs hazmat-certified”) after the solver proposes.

Addresses? Geocode in code.

Disclaimer

This is an independent unofficial site and is not affiliated with TypeSafe AI; official documentation is available at https://docs.typesafe.ai. Never treat jev.pro as TypeSafe official documentation. We do not sell, issue, or proxy API keys.

Hub: Comparisons. Siblings: vs orchestration platforms, for operations. Canonical: https://docs.typesafe.ai.