We built the software before the first vehicle.
The operating system underneath the service, five role-based consoles, one ledger, and document tracking that counts down to expiry instead of remembering after it.
See the consoles ↗Order of operations
Why we built it first.
A transport operation without software is a WhatsApp group and a spreadsheet that breaks past a few thousand trips a month. We built the system first so that from the first vehicle, every trip was already metered, every document already tracked, every change already logged.
That order, software before wheels, is why the service can report on itself rather than reconstruct itself at month-end.
The consoles
Five role-based consoles.
Each role sees the view it needs and nothing it doesn’t. Click a role to change the console below.
The morning view. Today’s routes, which vehicles are assigned, live pickup status against the geofence, and the change-request queue for this site.
The operational rollup across sites: utilisation, variance, exceptions to clear, and the buffer-fleet position for the branch.
Billing, reconciled. Each invoice against its trip ledger, the active billing model, excess-kilometre computation and the dispute window, no rate or margin surfaced in demo data.
Every document, tracked to expiry. Driver verification, vehicle papers, permits and facility certificates in a renewal queue that counts down rather than lapses.
The whole operation on one screen: trips run, compliance health, billing status and the emissions position, the view that says whether the promise held this month.
Screens shown use demo data and a fictional client. No real rates, no margin columns, no real identities.
Onboarding
A vehicle joins through the system, not around it.
A vehicle joins the fleet through the system, not around it: papers loaded, checks recorded, livery confirmed, and the vehicle mapped to the routes it can serve before it carries a single passenger.
Rate cards
Five billing models on one ledger.
A switch of model is configuration, not migration.
Fixed, per-trip, package, slab and back-to-back all live as rate-card logic against one ledger, so a switch of model is a configuration, not a migration.
Change requests
Every change is a request with a trail.
Once a route locks, every change is a request with an approver and a timestamp. The trail means a disputed change has an answer, who asked, who approved, when, instead of a memory.
Compliance
Document renewal with expiry countdowns.
The failure mode is a lapsed permit at a gate.
The failure mode in this industry is a lapsed permit discovered at a gate. The compliance console tracks each document to its expiry and surfaces it while there is still time to act, not after.
Month-end
Monthly billing review.
At month-end the system assembles the pack: ledger, reconciled invoice, variance report and, where wanted, the emissions statement, the same pack your admin receives, produced from the same data everyone else worked from all month.
Integrations
Integrations, with honest status.
| Integration | Status |
|---|---|
| HRMS / roster import | Available — CSV or API, mapped per client during onboarding. |
| Emissions feed to reporting | Live — built from the same trip data, into the monthly statement. |
| Finance / ERP export | Available — reconciled invoice and ledger exported as CSV. |
| Single sign-on (SSO) | On roadmap — stated as planned, not listed as live. |
Roadmap honesty
What is not in it yet.
We write it as roadmap rather than list it as a feature.
There is no self-service client portal today. It is on the roadmap, and we write it as roadmap rather than list it as a feature, because publishing a capability you do not have is exactly what fails a vendor due-diligence review.
We also do not run a 24/7 support desk or hold a SOC 2 report, and the platform is maintained by a small team. If you are buying transport, none of that is in your way. If you are considering licensing the software, those are the honest constraints to weigh. Licensing and custom builds →
Questions people ask
Questions people ask.
Is Thoyz OS a product I can buy on its own?
Primarily it is the system that runs our transport service. We can license parts of it or build against it. That’s a separate, smaller conversation on the custom-builds page.
Is there a client portal?
Not yet. It’s on the roadmap. We state it as planned rather than list it as live.
Can it import our roster from our HRMS?
Roster import is part of the platform; the specific integration status is listed above and confirmed per engagement.
Does it track compliance documents automatically?
Yes, every document is tracked to its expiry with a countdown, so renewals surface before they lapse.
Want to see the console behind the service?
The same system that meters every trip, tracks every document to expiry and reconciles every invoice against its ledger. We’ll walk you through the consoles on a call.
Talk to us ↗