Live today
See it in huntTMS today
The huntTMS dashboard is Live: loads, trucks and exceptions on one board. huntOS is designed to read across it.
huntOS is the command layer for connected freight operations, bringing priority, context and next action into one executive view.
Planned: in the development plan, no release date yet.
huntOS is designed to surface the operational exceptions that deserve attention, with the context required to decide.
01
The view opens on what needs a decision, each item with its owner and the product it came from.
02
Load risk, dispatch impact, driver action, finance consequence — each Planned link labeled as Planned.
03
Every exception names the rule that fired and when its data was read — not an invented confidence score.
The huntTMS dashboard is Live and you can use it today. huntOS itself is Planned: it sits in the development plan, so there is no group using it and nothing to join.
LoadHunter
Finds the load
huntTMS
Runs the trip
huntDRIVE
Driver workflow
huntPAY
Invoicing and payroll
huntOS
You are here
No. The huntTMS dashboard is Live and you can use it today; huntOS, the layer that would read across the five products, is Planned.
Not for the dashboard inside huntTMS, which is the part that is Live. huntOS as a layer across the five products is Planned, so the question of prerequisites does not arise yet.
Which exception to act on first, what it costs if nobody does, and who has to decide. None is supported today, because huntOS is Planned. The exceptions that exist live on the huntTMS board.
It applies specific rules and models to operational events, and a person decides what happens next. We would rather describe the mechanism than the category.
There is nothing to try yet. huntOS is Planned, which means it sits in the development plan with no date attached, and this site does not open a waiting list for a product that has not been built.
Live today
The huntTMS dashboard is Live: loads, trucks and exceptions on one board. huntOS is designed to read across it.
Planned · no date
What kind of operation you run, how large the team is, which products you already use and the exceptions that cost you the most.