Packages
Trial, Basic, Professional and Enterprise. Every one carries the same evidence guarantees; what changes is capacity, reporting and how much of the platform you can wire into everything else.
Why there are no figures on this page
The packages are settled and set out in full below. The figures are not published yet, and publishing a number we might change would be worse than publishing none. A written quote against your job volume, branches and retention requirement takes one conversation.
Mobile tyre and roadside operations
Not by which features you are allowed to have. The core is the same in all four.
Thirty days on your own workflow. No card.
Best for
Operators who want to see it carry real jobs before anyone signs anything.
Thirty days, no card, no notice period.
One fourteen-day extension where there is a named blocker rather than a quiet drift.
Book a trial callOne operation, one or two depots.
Best for
Independent operators running their own work, with commercial accounts and light contract reporting.
Monthly or annual.
Annual: pay for eleven months, get twelve.
Book a demoSeveral depots, doing contracted fleet work.
Best for
Regional operators whose customers audit them, and who feel it in reporting, branch consistency or process control.
Annual preferred. Monthly available.
Annual: pay for ten months, get twelve.
Book a demoNational coverage, frameworks and integrations.
Best for
Fleet service providers and multi-region networks carrying framework agreements and procurement review.
Annual, on a scoped order form.
Priced against your scope: integrations, data residency, security review and the service levels you need.
Talk to salesThese packages describe what a tier contains, not what is finished.
AxleGrid is in development and pre-pilot. The product page states what is built, what is in progress and what is designed but not started, surface by surface. We would rather you check that before a conversation than after one.
The first thing to understand
AxleGrid is priced as a package for your operation, not as a per-seat licence. That is deliberate, and it changes what happens as you grow.
Per-user pricing punishes exactly the behaviour that makes this kind of system work. A tyre operation needs the fitter in it, the dispatcher in it, the depot manager in it, the owner in it and — increasingly — the fleet customer able to see their own jobs. Charge per head and every one of those becomes a decision about whether the licence is worth it, which is how operations end up with three people sharing a login and an audit trail that means nothing.
It also fits the trade badly. Headcount in mobile fitting moves with the season, with subcontract cover and with the shape of the contracts you are running. A price that recalculates every time someone joins for the winter is a price you cannot budget against.
In every package
The core is not unbundled. Whatever size you are, the list above is included — the trial as well.
Side by side
For the point where you have narrowed it to two and want to check the edges.
| Package | Trial | Basic | Professional | Enterprise |
|---|---|---|---|---|
| Modules | ||||
| Avior DispatchIntake, assignment, status and operational visibility. | Included | Included | Included | Included |
| AxleGrid MobileThe fitter app: accept, navigate, capture, close. | Included | Included | Included | Included |
| Avior LocateCustomer location links, consent and typed-location fallback. | Included | Included | Included | Included |
| Avior AxleProofCompletion evidence, hash-chained and checkable. | Included | Included | Included | Included |
| Audit ledgerYour own history, readable without a charge for reading it. | Included | Included | Included | Included |
| Reporting | ||||
| Avior Insights | Limited | Limited | Standard reports | Advanced and custom |
| Operational reports | Not included | Not included | Included | Included |
| Capacity | ||||
| Users | 8 | 15 | 75 | 500 |
| Jobs a month | 250 | 750 | 5,000 | 50,000 |
| Branches | 1 | 2 | 15 | 250 |
| Evidence storage | 5 GB | 25 GB | 250 GB | 2 TB |
| Evidence retentionHow far back a claim can reach and still find the record. | 30 days | 90 days | 365 days | 7 years |
| Platform | ||||
| Integration API, SSO, custom domainNot part of Professional by default. Scoped where the operation needs it. | Not included | Not included | Not by default | When scoped |
| Dedicated database | Not included | Not included | Not included | When scoped |
| Contract | 30 days | Monthly or annual | Annual or monthly | Annual, scoped |
Retention is the row worth pausing on. How long you must keep evidence is a contract question, not a technical one — so it is a stated package dimension rather than a default you discover when a claim reaches back further than your data does.
Getting on it
Configuration is work, and work is quoted. What that work consists of should not be a surprise, so here it is.
Onboarding is quoted alongside the subscription, not discovered afterwards. See services for what migration, custom reports and integrations actually involve.
Said explicitly
The hash chain, the completeness check and the audit ledger are in every package, including the trial. A system whose integrity guarantees depend on what you paid is not offering integrity, and the moment you most need the evidence is not the moment to discover it was an upgrade.
Reading your own history is not a chargeable event.
Giving a fleet customer visibility of their own jobs should make you easier to work with, not more expensive to run.
What moves you up a package
Packages are separated by capacity, not by which features you are allowed to have.
The closest thing to a measure of how much work the platform is actually doing for you.
Operational complexity, not headcount. Two depots is a different system to one.
Banded, not per seat. Adding a fitter should never be a purchasing decision.
How much you keep, and for how long. A seven-year retention obligation is a real cost and is priced as one.
Quoted separately
Pretending otherwise produces a low headline price and an unpleasant conversation later.
Thirty days, no card, a setup call, a midpoint review and a conversion review. It is judged on whether real dispatchers and real fitters used it, not on whether anyone logged in — a trial that only produces logins has told neither of us anything. It works best if you come with a named dispatcher, at least one fitter who will actually run jobs on it, and a real workflow. There is no open sign-up button, and that is on purpose.
If you exceed a package limit there is a grace band before anything is charged, and the overage rate is published in your order form rather than discovered on an invoice. If your usage sits above your package for more than a couple of months, the right answer is a bigger package, and we would rather tell you that than bill you for the difference indefinitely.
The four packages above are for the operators doing the work: mobile tyre and roadside teams, and the depots behind them. A separate set of packages for fleet operations — the customer side of the same contracts — is being prepared and is not ready to publish. We are not going to put a date on it here.
If that is the side you sit on, the fleet contract reporting page covers what exists today, and telling us what you need now is the most direct way to influence what those packages contain.
Written quote
Tell us your job volume, your branches and how long your contracts make you keep evidence. You get a quote you can put in front of a board, with the package limits and the overage rates next to the price.