A TMS that can show its work.
Dispatch, compliance and settlement for asset-based carriers — where every driver payment traces back to the tariff, the trip and the load that produced it. No spreadsheet in the middle, no number you cannot explain.
Already a customer? Sign in
ELD-agnostic
Bring the ELD you already run. Per truck, not per fleet.
Multi-authority
One back office, several MC numbers, one address book.
History comes with you
Migration is a feature of the schema, not a script.
Every field audited
Old value and new, append-only, enforced by the database.
Switching
Changing TMS should not cost you your history.
Most carriers stay on software they have outgrown because the last five years of their business live inside it. We treated that as a schema problem rather than a services engagement — every row we create for you remembers the row it came from.
Extract
We pull your records out of the system you are on today and land them as-is, keeping the original payload beside every row we create.
Dry run
A full rehearsal that writes nothing. You get the same per-record verdicts an apply would produce — created, updated, skipped, failed and why — before anything is committed.
Apply
The same run, for real, re-runnable and resumable. Every imported row keeps a permanent pointer back to where it came from.
What comes across
- Drivers and contractors, de-duplicated into one person per human
- Trucks, trailers and assignment history — with the odometer at each handover
- Compliance documents, their expiry rules and their recurrence
- Customers, loads, trips and stops, with appointment times corrected to the facility's timezone
- Pay tariffs, the driver ledger and past settlements
And what might not
Some systems store their change history as rendered text with no record of the previous value. Where that is true, the history cannot be imported as an audit trail — and we tell you that before the migration, not after it.
Platform
Built around the truck and the driver, not a broker's margin.
An asset-based carrier lives or dies on per-unit utilisation. Every table below exists because that is the business being run, and the model refuses the shortcuts that make a number unexplainable six months later.
Dispatch
Loads, stops and trips modelled as separate things, because they are.
- A load that changes driver mid-route is still one load
- Appointment, window and first-come stops, each with its own rules
- Stop times local to the facility, not to your office
Fleet and equipment
The truck is the unit of the business, so it is the unit of the model.
- Available, home, shop, in transit or yard — with how long it has been there
- Trailers as first-class records, not a string on a form
- Assignment history with the odometer at both ends
People and compliance
A person, their business and their employment are three different records.
- Licence class, endorsements and restrictions as data you can query
- Document requirements with real expiry modes, including recurrence
- Who needs action today, sorted by how urgent it is
Settlement and driver pay
Named pay tariffs that are reused, versioned and never overwritten.
- Mileage bands, a guaranteed weekly floor and per-stop accessorials
- A pay change never rewrites last week's settlement
- Posting to the books and sending to the driver are two separate acts
The driver sub-ledger
A driver does not have a balance. They have a position per account.
- Every charge classified as an asset or a liability, so the sign is never in doubt
- Advances drawn down across several settlements, not all-or-nothing
- Balances derived from the movements, so the two cannot disagree
Access control
Roles you compose from permissions, rather than five names we chose.
- Deny by default, with no administrator bypass
- Posting a settlement and viewing driver pay are separate rights
- Who may read an identity number is a permission, not a convention
Settlement
Numbers a driver can walk backwards.
A settlement is not a figure you publish and then defend. It is three layers that each reconcile against the next — so when a driver asks why this week is lighter, the answer is a load, a line and a rate, not a promise to look into it.
Rate
The tariff
A named scheme with bands and a floor, shared across drivers and dated so it never rewrites history.
Line
The trip
One expense line per load, each carrying its own calculation — linehaul, detention, stop pay, a deduction.
Total
The settlement
One payee, one period, adding up the lines. Frozen the moment it is posted.
One load, derived
Illustrative- Load gross
- $2,400.00
- Tariff — 27% of gross
- $648.00
- Stop pay — 2 extra stops
- $60.00
- Fuel advance — instalment 2 of 4
- −$125.00
- Net for this load
- $583.00
Change the tariff tomorrow and this settlement does not move. Rates are dated, so last week is paid at last week's terms — a pay change is never a silent rewrite of history.
Unit economics
Know which truck to keep.
The decision that actually moves an asset-based carrier's margin is which units to run and which to let go. Answering it means revenue, driver pay, fuel, tolls, maintenance and financing all have to be attributable to one truck — which is a property of the data model, not a report you can bolt on later.
So the odometer is captured at both ends of every assignment, a repair is billed to the unit that needed it, and a fuel transaction lands against the truck that burned it.
Revenue
per loaded mile, per unit
Driver cost
from the settlement, not an estimate
Fuel and tolls
attributed by transaction
Maintenance
work orders costed to the unit
Financing
loan and insurance per truck
Cost of ownership
the number the others add up to
Standards
The parts nobody demos, written down anyway.
These are the decisions that are cheap on the first day and impossible to retrofit on the thousandth. We are stating them publicly so you can hold us to them.
Identity numbers are encrypted, under a key per person
A licence or tax number is stored encrypted with a searchable fingerprint beside it. A lawful deletion request is honoured by destroying that person's key — not by hoping every copy was found.
Credentials are hashed and never returned
No endpoint, at any permission level, hands back a password. Not to an administrator, not to support, not to us.
The audit log is data, and the database enforces it
Every change records the old value and the new one, keyed by record and field. Rows cannot be updated, deleted or truncated — that is a trigger, not a policy.
Tenant isolation is proven by tests that fail when it breaks
Every query for your data passes one chokepoint, and the isolation tests are validated by removing the filter and watching them go red. A test that still passes without the filter is not a test.
Money is an integer count of minor units
Never a float, never a string parsed at the edge, with a currency on every row that holds an amount.
A date is not an instant
A pickup appointment belongs to the facility's timezone. A hire date has no timezone at all. Conflating the two is how appointments land hours off, so we don't.
Integrations
Keep the ELD you already run.
The ELD is an integration, never a dependency. The provider is bound to each truck rather than to the fleet, which means you can run the old one and the new one side by side through a changeover instead of switching every unit on one night.
Every connection reports its own health — last sync, last error, current status — because a feed that quietly stopped four hours ago should not look like a quiet afternoon.
ELD
Position, odometer, engine hours and HOS
Factoring
Invoice submission and funding status
Fuel
Card transactions into the driver ledger
Toll
Transponder charges attributed to a trip
Accounting
Settlement and invoice export
Load boards
Inbound rate confirmations
Pricing
How we price.
Fleet size is the only thing that scales with what the software costs us to run, so it is the only thing we price on.
Priced per truck
Not per seat and not per load. Your dispatcher, your safety manager and your accountant all need the same records; charging for the third one to log in is a tax on doing the job properly.
Every module included
Compliance, settlement, the ledger and the audit trail are the product, not tiers of it. You should not have to buy the ability to prove what you paid someone.
Migration is not a line item
Bringing your history across is part of becoming a customer, not a professional-services invoice that arrives afterwards.
Rates are set per operating authority once we know the fleet size.
Questions
Before you ask.
Do I have to change ELD provider to use this?
No. The ELD is an integration, never a dependency — the product is built to run for a carrier who uses none of our other software. The provider is bound per truck rather than per fleet, which also means you can run your old ELD and a new one side by side while you change over, instead of switching everything on one night.
Can I bring my data from the system I use today?
That is the part we designed first. Import runs are re-runnable, always rehearsable as a dry run that writes nothing, and every row we create keeps a permanent pointer back to the record it came from. Where something genuinely cannot be migrated, you hear it before the migration rather than discovering it after.
We run several authorities. Is that an extra account?
No. One back office can hold several operating authorities, each with its own MC, DOT and FEIN, sharing one address book and one user list. Settlements, compliance records and numbering stay per authority, because that is how the regulator and the payroll both see it.
Who can see a driver's identity numbers and pay?
Exactly the people you grant it to. Roles are composed from individual permissions rather than picked from a fixed list, reading an identity number is its own permission, and every read of the audit log is itself governed. Deny by default, with no administrator bypass.
Is there an API?
Yes — the data layer sits behind a service layer that both the application and the public API call into, so the API is not a later rewrite of the product. Integration credentials are encrypted and are never returned to a client.
What state is the product in?
Early access, under active development. The foundation — tenancy, audit, numbering, money and time handling — plus people, equipment, documents and compliance are built. Dispatch, settlement and the ledger are designed and in progress. We would rather say that plainly than imply otherwise.
Bring the fleet. Bring the history.
Start with the records you already have and see them come across in a dry run that writes nothing.