Skip to content
AxleGuard
Demo

About

One load, carried through every decision.

AxleGuard started with the late axle answer. It became a wider freight operating platform because preventing that failure requires the load, equipment, rules, route and live run to stay connected.

Where it started

The gap between what the paperwork knows and what the scale knows.

A bill of lading holds one number for weight. A scale house reads five. The shipper, broker, dispatcher and driver all make their decision from that one number. Enforcement is done on the five.

That gap does not close with more care. It closes with arithmetic that nobody has time to do by hand. Every consecutive axle group faces four competing limits. A second jurisdiction and four hundred miles of fuel burn can move the answer while the truck is running.

So the tool had to do three unglamorous things at once. Solve the physics from where the freight actually sits. Say what to move, not just that something is wrong. And keep saying it as the load changes on the road.

The problem in full

Five decisions that shaped it.

Solve the position, not just report the weight

Plenty of things can tell you what a load weighs. Very little will tell you what to do about where it sits, which is the part that costs money on a Tuesday.

Make jurisdiction a property of the load

Not a setting on the account. A truck crosses a state line in the middle of a run, and a system that holds one global rule set has already decided to be wrong on half the freight.

Refuse rather than warn

An over-limit load cannot be dispatched, and there is no override. A warning that can be dismissed is a warning that is dismissed at the end of a bad shift.

Keep the record, not just the current state

Every change is written down with what it looked like before. A compliance position you cannot reconstruct two years later is not really a compliance position.

Sell it with a conversation

Nothing here is self-serve. An axle limit is a legal position, and nobody should be configuring one from a card form at two in the morning without hearing what this is and is not.

The gap, counted

One number is written down. Sixteen can be cited.

This is the whole reason the product exists, expressed as arithmetic rather than as an argument.

Weight checks on one five-axle truck

How many weight numbers each part of the chain sees

checks
  • On the bill of lading1 checks

    The gross weight, which is the one number that does not move when the load is built badly

  • What a careful planner checks by hand3 checks

    Gross, the drive tandem and the trailer tandem

  • What the rules actually apply to the truck16 checks

    Five single axles, ten consecutive axle groups, and the gross

A five-axle tractor-semitrailer has five single axles, ten consecutive groups of two or more that the bridge formula applies to, and one gross limit. That is sixteen separate ways to be over, and exactly one of them is written on the paperwork everybody in the chain reads. Counted, not estimated.

A bill of lading holds one number for weight. A scale house reads five, and the arithmetic behind them runs to sixteen.

How we work

Four rules we hold ourselves to, including on this website.

They are worth stating because they are the ones most easily abandoned when a page needs to be more persuasive than the product is ready to support.

Keep one answer through the whole run

A load should not be rebuilt as paperwork, a route, a scale reading and a telemetry event in four different systems. The equipment, freight, rules and verdict stay connected from planning through arrival.

A verdict without an instruction is half a product

Telling somebody a load is illegal leaves them exactly where they were, only more worried. Every failing verdict here comes with the move that fixes it, in the units the yard already uses.

Say exactly what is supported

Equipment, jurisdictions and integrations are named in the rollout scope. If a combination needs custom modelling, that is settled before configuration starts.

Write for the person on the dock

Not for a buyer, not for a conference. If a sentence on this site would not survive being read out to a dispatcher at six in the morning, it does not belong here.

Who built it

Built bySpace-O Technologies.

The same people wrote the arithmetic, built the screens and run the demonstration calls. That is the only structural fact about us that should matter to you on a call.

What that means in practice

  • Ask how a number is computed and get the answer on the call, not in a follow-up
  • Ask what is not built and get a straight list rather than a roadmap
  • The person who takes a bug report is the person who fixes it
  • Nothing on this site was written by someone who has not used the product

What you will not find here

No customer logos, no testimonials, no headcount, no funding announcement and no statistics we did not measure. Not as modesty — we simply have not earned any of them yet, and inventing them is how a compliance tool loses the only thing it is selling.

Straight answers

Five questions about us, rather than about the product.

No customer logos, no testimonials, and no statistics we did not measure. We have not earned any of them yet.
01Who is behind this?
The same product team that wrote the arithmetic runs the demonstration calls. You can ask how a number is computed and get the actual answer rather than a follow-up email.
02Are you a routing company or a compliance company?
AxleGuard is freight planning and execution software. Per-axle compliance is the differentiator, but the answer also needs cargo placement, equipment geometry, truck-safe routing, permits, trip timing and live telemetry. Those pieces stay together because the load moves through all of them.
03Who is a rollout designed for?
Carriers, brokers, shippers and heavy-haul teams that can bring one real lane, the equipment that runs it and a clear definition of a legal result. The rollout starts there before expanding to the board.
04Why is there no team page with photographs?
The useful information is how to reach the people responsible for the product, how rollout decisions are made and who owns support. Those details are on this page and the contact page rather than hidden behind a directory of portraits.
05How do we get hold of you?
By email, at sales@spaceotechnologies.com, or through the demonstration form. There is one inbox, a person reads it, and you get a reply within one business day even if the reply is that we are the wrong fit.

Next step

Talk to the people who built the arithmetic.

Bring the hardest question on your current process. You will get a direct answer from the team responsible for the solver, the rules and the rollout.