AXYS

Every commercial carrier in Ontario operates against a CVOR — a Commercial Vehicle Operator's Registration record maintained by the Ministry of Transportation. The CVOR is the province's running tally of a carrier's roadside inspections, collisions and convictions, and it is the thing that decides whether a carrier keeps operating.

The evidence behind that record tends to live nowhere in particular. A safety manager keeps driver abstracts in one spreadsheet, inspection reports in a filing cabinet, and convictions in an inbox. When an audit arrives, assembling the picture is archaeology. Worse, the carrier is usually the last to know its own standing: the first signal that a threshold has been crossed is a letter from the MTO.

AXYS holds a carrier's drivers, vehicles, roadside inspections, collisions, tickets and convictions, and driver qualification files in one place. That alone replaces the spreadsheets, but the part that matters more is what it does with them.

It reconciles the carrier's own data against their official MTO record, so discrepancies surface as discrepancies rather than as surprises. Then it rolls everything up into a fleet risk score measured against actual CVOR thresholds — the point being to tell a safety manager where they stand before the regulator does.

One deployment serves many carriers, with each carrier's data sealed off from the others. In a compliance product this is not so much a feature as the licence to exist: a leak across tenants would be a leak of regulatory records between competitors.

Every change is permanently logged with who made it and why. Compliance software gets read adversarially — in an audit, or in litigation after a collision — so “who changed this driver's file, when, and on what basis” has to be answerable years later. That requirement shapes a surprising amount of the schema.

React on the front end, Python and FastAPI on the API, PostgreSQL for storage, hosted on Azure.