Skip to content
AxleGuard
Demo

Compare

Every claim on this site, in one table.

Twenty-four rows across six categories, including the rows where our own column is a plain no. Anything a vendor has not published is marked not published rather than scored against them.

  • 24 capabilities
  • Six categories
  • Public documentation, August 2026

The matrix

What each category does, and does not, take responsibility for.

These are category generalisations rather than vendor claims. Individual products inside a category vary, and the category pages name them one by one.

Showing all 24 capabilities.

Capability matrix comparing AxleGuard with routing and navigation platforms, dispatch systems, telematics, onboard scales, and bypass and permit services
CapabilityAxleGuardRouting & navigationDispatch / TMSTelematics / ELDOnboard scalesBypass & permits
Truck-aware route requested from stored dimensions and weightYesYespartNoNoNo
Low bridges and restricted roads avoided on the planAxleGuard marks the route for manual review if the provider relaxes a restrictionpartYespartNoNoNo
Per-axle weight solved from cargo positionBefore anything is loadedYesNoNoNoNoNo
Bridge formula on every consecutive axle groupYesNoNoNopartNo
Tire and axle-rating limits layered on statuteYesNoNoNoNoNo
Which rule bound, named on the verdictYesNoNoNoNoNo
Corrective slider position in holes and inchesYesNoNoNoNoNo
Answer available before the trailer is sealedYespartpartNoNoNo
Compliance recomputed per leg as freight comes offYesNoNoNoNoNo
Fuel burn changing the verdict mid-tripYesNoNoNopartNo
Restriction-ignored warning surfaced to the plannerYespartNoNoNoNo
Derived replay now; physical axle signal after commissioningpartNoNopartYesNo
Weight history plotted across the whole runCurrent AxleGuard samples are a named derived replay; physical measurements require commissioningYesNoNopartpartNo
HOS planning clocks on the same timeline as the loadPlanning arithmetic, separate from the legal log-of-record workflowYesNoYesYesNoNo
Editable jurisdiction rule setsYesNopartNoNopart
Permit pathway when no legal position existsIdentifies candidates and tracks the filing record; the issuing agency still controls the permitYesNopartNoNoYes
Escort and travel-window conditions recorded on a permitAxleGuard records the controlling conditions; it does not derive or issue thempartNopartNoNopart
Weigh station and bypass status along the routepartNoNopartNoYes
HOS record workflow and roadside transferNot an FMCSA-registered ELD; telematic/local transfer unlocks only when registration evidence is recordedpartNopartYesNoNo
Orders, rates, settlements and invoicingNoNoYesNoNoNo
Hardware fitted to the truck requiredNoNoNoYesYespart
Provider cost linked to the individual loadThe call record can carry a load ID; the current report does not aggregate a per-load ledgerpartNopartpartNopart
Before-and-after audit on governed changesYesNopartNoNoNo
The same verdict on the desk and in the cabYespartpartpartpartNo
supportedpart partly, or with limits not supportedn/p not published by the vendor

Read a part as "some products in this category, or all of them with limits". Read an n/p as "the vendors we checked have not published this", which is a fact about documentation and not a fault.

Our column was checked against the application code

Every AxleGuard cell was re-audited on August 29, 2026. A partial mark now covers six specific boundaries: relaxed route restrictions, physical telemetry, permit conditions, bypass-provider connection, ELD registration and per-load cost presentation.

How to read it

The rows are grouped, and the groups matter more than the ticks.

A tick in the wrong group is worth nothing. A fleet that already routes well and still gets cited has a problem in rows three to seven, not in rows one and two.

Rows 1 to 2 — the road

Whether the tool understands that a road has a height, a weight rating and a turn radius, and refuses to send a 13-foot-6 trailer under a 13-foot bridge.

Rows 3 to 7 — the axles

Whether the tool solves what each axle group carries from where the freight sits, applies every statutory test to it, and says which rule bound.

Rows 8 to 14 — the run

Whether the answer survives contact with a real trip: legs, drops, fuel burn, hours, and a verdict that changes because the truck moved.

Rows 15 to 18 — the rules

Whether jurisdiction is a property of the load rather than a global setting, and what happens when no legal position exists.

Rows 19 to 24 — the operation

The office functions, the hardware, the money and the audit trail. This is where our own column has the honest gaps in it.

Our own boundaries, on purpose

Orders, settlements and invoicing remain a plain no. HOS record mechanics exist, but the workspace is not FMCSA registered. Recorded registration status gates transfer today; the other readiness checks are visible evidence, not yet enforcement gates. Physical signals stay partial until a real gateway passes commissioning.

Rows marked supported, out of 24

rows
  • AxleGuard16 rows

    Plus six part, and two plain no

  • Routing and navigation2 rows

    Plus three part

  • Dispatch and TMS2 rows

    Plus ten part

  • Telematics and ELD3 rows

    Plus five part

  • Onboard scales2 rows

    Plus four part

  • Bypass and permits2 rows

    Plus four part

Counted from the table above. This is not a scoreboard. The twenty-four rows follow one load from planning through operation, and every category here is being asked about work it may never have set out to do.

Why the count is the least useful thing here

A dispatch system carrying two ticks and ten parts is not a weak product. It is a strong product being asked about axle physics. Read down the rows that bind your own operation instead, and ignore the totals.

Five of these six columns hold products a fleet already owns. The question was never which one to replace.

The nearest neighbours

Axle calculators deserve their own table.

Putting a dedicated axle weight calculator in the same column as a dispatch system would flatter us and mislead you. This is the closer comparison, and the one worth arguing about.

Showing all 12 capabilities.

Capability matrix comparing AxleGuard with dedicated axle weight calculators, load and container packing software, and an in-house spreadsheet
CapabilityAxleGuardAxle weight calculatorsLoad and container packersSpreadsheet built in-house
Axle weights from payload positionYesYespartpart
Bridge formula on every consecutive groupYespartNoNo
Tire and axle-rating limits layered on statuteYesn/pNoNo
Corrective move given in holes and inchesYesNoNoNo
Jurisdiction rule set attached to the loadYespartNoNo
Container and pallet packing in three dimensionsYesNoYesNo
Centre of gravity and stability outputpartYesYesNo
Finished-vehicle build record and sign-off workflowpartYesNoNo
Re-solved per leg as freight comes offYesNoNoNo
Routed on a road the vehicle can legally takeYesNoNoNo
Derived replay now; physical axle signal after commissioningpartNoNoNo
Audit trail of who changed a limitYesn/pn/pNo
supportedpart partly, or with limits not supportedn/p not published by the vendor

Two engineering boundaries

AxleGuard now exposes a planning-grade centre-of-gravity and rollover margin, plus an accepted finished-vehicle build record. Neither is a certified stability calculation or a dealer/bodybuilder pre-build specification. A firm speccing a tanker body should still buy the engineering tool built for that work.

Methodology

Where these rows came from.

Every row is drawn from publicly published product documentation, specification sheets and vendor support material, read as of August 2026. Where a vendor does not publish a capability, the cell reads not published. That is a statement about what has been written down, not a claim that the product cannot do it.

There are no pricing figures, customer counts, market share numbers or benchmark timings anywhere in this table, because we have not run those tests and the vendors have not published figures that could be compared fairly.

Product names and trademarks belong to their owners and are used for identification and comparison only. None of the vendors named on this site has reviewed or endorsed any of it. These are active products that ship changes continuously, so confirm anything that matters directly with the vendor before it decides a purchase.

The reasoning behind each row, category by category, is on themethodology section of the compare hub.

One table is not a decision

A matrix is good at showing you what to ask about and bad at telling you what to buy. Take the four or five rows that actually bind your operation, and put those questions to every vendor on your list, including us.

Where a row disagrees with a vendor

If a vendor publishes something that contradicts a cell here, the vendor is right and we will change it. Point it out and we would rather correct the page than argue with the documentation.

Our own column, counted

The 24 rows, as our own column answers them

rows
67%
25%
8%
  • Supported16 rows
  • Partly, or with limits6 rows
  • A plain no2 rows

Six rows carry visible limits: relaxed route restrictions, physical signals, permit conditions, bypass, HOS transfer and per-load cost presentation. Orders and invoicing remain outside the product.

Next step

Test the rows that matter to you.

Pick the four rows your operation actually lives on, bring a real load, and see whether our column holds up on your freight rather than on our page.