One copy of the rules
The limits, the rule sets and the equipment live in one place, and everything reads from that place. When a limit changes it changes once, and the desk, the cab and your other systems are all correct the same afternoon.
Works with your systems
Four connection lanes. Four different trust gates.
Customer systems exchange operating records. Google supplies road and corridor intelligence. Bypass providers require commercial onboarding. Physical truck signals require commissioning. AxleGuard keeps those paths separate so one connected service cannot make another look approved.
- 165 registered operations
- Provider-safe fallback
- Physical hardware acceptance gate
The connection map
Do not put an access credential, a provider contract and a truck sensor in one bucket.
Each lane below has a different owner, failure mode and standard of evidence. The product exposes the status instead of smoothing those differences into a logo wall.
01
Customer systems
Live API
Scoped Bearer access, quotas, request logs and 165 registered operations. A named TMS still needs field mapping and rollout tests.
See the boundary02
Google services
Live
Truck routes, maps, geocoding, roads, elevation and current weather are configured and observable by service and call.
See the boundary03
Weigh and bypass
Connection required
Drivewyze, PrePass or a compatible adapter can be configured and tested. Unknown still means plan to pull in.
See the boundary04
Truck hardware
Physical validation required
One credential per truck, normalized ingest, certified-reference comparison and owner approval before use.
See the boundaryHow it fits
Four movements, and only one of them is new work.
The load already exists somewhere. The only new step connects that record to the equipment, freight position, rules and route before the verdict returns.
Your system of record does not move
Orders, rates, invoices, customers and driver files stay exactly where they are. AxleGuard adds the physical operating answer and hands it back.
- 01
The load arrives from wherever it already lives
Your dispatch board, your warehouse system, or a person typing it in. The load comes across with its shipper, its consignee, its freight and its dates, and nobody types it twice.
- 02
It is solved once, here
Axle weights from where the freight sits, every consecutive axle group, the rule set for each jurisdiction it crosses, and the corrective move if it needs one. One answer, computed in one place.
- 03
The verdict goes back to where the load lives
Legal, caution or over, with the group that failed and the fix. It lands beside the load in the system your office already works in, so a planner does not have to be in two places to know one thing.
- 04
What happens in the yard flows back the same way
A status change, a correction made on the dock, a load dispatched or held. It moves in both directions, so the board and the yard do not spend the afternoon disagreeing about which is current.
Four rules
What has to be true for a tool like this to survive a busy week.
These are the four things that decide whether a compliance tool is still being used three months in, and none of them is about the compliance.
Nobody re-keys a load
A compliance tool that needs the load typed into it a second time becomes a data-entry job, and a data-entry job quietly stops happening in the first busy week. Loads arrive from what you already run.
It fits the office as it is
Your system of record stays your system of record. Orders, rates, invoices and driver files do not move. AxleGuard adds the physical load, legal route and live verdict where the people who need them are already looking.
The same rules apply from outside
A connected system has exactly the authority its role allows, and no more. A load that is over cannot be dispatched from another system any more than it can be dispatched from the screen.
The second data-entry job
Forty loads on a Monday, and the eleven nobody checks.
This is what decides whether a compliance tool is still in use in month three, and it has nothing to do with the compliance.
How many of Monday's loads get an answer
One Monday board, two ways of working
loads- Loads on the board that morning40 loads
Every one of them has an axle question in it
- Checked, when it means typing each one in twice29 loads
The eleven that get skipped are skipped because it is Monday, not because they look safe
- Checked, when they arrive from the board itself40 loads
Including the eleven nobody would have found time for
A worked example of an ordinary Monday, not a fleet measurement. The exact eleven is not the point. A tool that needs a second round of typing loses loads at the busy end of the day, when loads are also built in a hurry.
A compliance tool that needs the load typed in a second time becomes a data-entry job, and a data-entry job stops happening in the first busy week.
Where the answer lands
Beside the load, in the place people are already looking.
A verdict on a screen nobody has open is a verdict that changes nothing. The point of connecting anything is to remove the step where somebody has to go and look.
- On the board, beside the load, as legal, caution or over
- With the axle group that failed and the rule that bound it
- With the corrective move, in the units the yard already uses
- On the driver's phone, for the loads that are theirs
- On a read-only link, for a customer who has no account
- In the record, with who changed what and what it looked like before
A verdict on a screen nobody has open is a verdict that changes nothing.
axleguard.app/loads
The argument, in three rungs
What it does, why that beats the normal answer, and what it is worth.
Two claims about fitting into an office that already works, carried through to the thing that actually decides adoption.
The tool survives its first busy week, which is the only test of whether a new system is actually adopted.
Loads arrive from the system you already run, are solved once, and the verdict goes back to sit beside the load there.
The normal arrangement is a compliance tool that lives on its own island and needs everything typed into it a second time.
Nobody has to decide which answer to believe at six in the morning, because there is only one answer.
There is one copy of the rules, shared by the planner's screen, the driver's phone and any connected system.
Most yards run a spreadsheet on the desk and a rule of thumb in the cab, and the two disagree exactly when it matters most.
Straight answers
Five questions, including the one about logos.
Connections are scoped to your stack
Integrations are configured during rollout rather than selected from a self-serve connector library. The source system, fields, ownership and failure path are agreed before data starts moving.
01Which systems do you connect to today?
Google truck routing, maps, geocoding, road snapping, elevation and current weather are live in the audited workspace. AxleGuard also has tested connection controls for Drivewyze, PrePass or a compatible bypass adapter, but no bypass provider is connected in this workspace. TMS and customer-backend mappings are scoped during rollout.
02Does our dispatch system have to change?
No. It keeps being the record of your business. AxleGuard sits alongside it, connects the physical load to the rules and route, and hands the resulting verdict back. Nothing about orders, rates, invoices or driver files moves.
03What if we do not want to connect anything yet?
Start with loads entered in the workspace and Google-backed routing services. A TMS connection, bypass provider or physical truck gateway is a separate decision with its own credentials, tests and fallback. The core load and compliance workflow does not require all three.
04Can another system dispatch a load that is over?
No. The rule is enforced where the change actually happens, so a connected system is refused in exactly the same way a person clicking a button is refused, and the attempt is recorded either way.
05How long does connecting usually take?
It depends entirely on what your system will let out and let in, which is why it is scoped during a rollout rather than quoted on a website. The honest answer on a first call is usually a range and a list of what we would need to see.
Next step
Bring the system your loads live in.
Tell us what it will let out and what it will let in, and we will tell you honestly what connecting it would take.