Mount it. Choose the truck.
Set up the driver’s phone or tablet in landscape while parked. The driving view keeps speed, direction and the map together.
Nexus Fleet
On the road. In the shop.
Two screens. One truck. A running Austin demo.
Your drivers, your trucks
No cameras here. No AI rating your driving. And no decision about your truck comes out of a box you can't inspect.
We respect privacy. No AI runs in this app. There is no camera, no driver score and no behaviour analysis, and nothing you enter is sent to a model, because there is no model. Every number on the screen is arithmetic you can check by hand, and it shows where it came from.
- No cameras
- No driver scores
- No AI
The record behind the resultAsk why.
Ask why.
Get the evidence.
Know which part was measured, who supplied the service policy, and what the numbers actually support. Try the sample below. Change the evidence and watch the result change.
Each part has an identityEach limit has a sourceUnknown stays unknown
NEXUS 01 · SAMPLE F-150
Front left tire
DEMO-TIRE-01At or below sample limit
3/32 inSample tread measurement
The sample measurement is below a fictional 4/32 in shop limit. A person must inspect the vehicle and decide the work.
Historical evidence · obtain a new reading
SHOW THE MATH
3/32 − 4/32 = −1/32 in margin
Put the record to the test.
Try a different reading, remove the policy, or use an old observation.
- Observation
- 3/32 in20 minutes old · sample timeline
- Source
- Manual measurement · sample
- Policy
- 4/32 in tread limitDemo shop instruction T-01 · sample only
- Baseline
A decision should travel with its evidence. Download this sample with its part ID, observation time, policy and calculation. Nothing is saved to your fleet.
What you can use todayThe workspace supports manual inspections, part histories and source-based service calculations. The demo uses fictional shop rules, never recommended service limits.
What is still being builtTracker firmware, the OBD feed and live map setup. No prediction of failure, safety certification, camera or driver score is added by this example.
In everyday use
01 · Before the drive
02 · At the shop
03 · After the work
One vehicle record. Two ways to use it.
A second phone for the mechanic.
The mechanic opens the same truck’s record on their own phone: inspections, parts, meter readings and repair history. Opening a part does not change the driver’s screen.
Measure once. Keep the history.
Record the measurement or repair with its date, meter and source. A rotation keeps the part’s history; a replacement starts a new part record.
Available today: the workspace supports manual records. The connected setup: a tracker would send position and vehicle readings to the shared record; the mechanic would see each report’s age. Tracker firmware, the OBD feed and live map setup are still in development. The two screens above demonstrate that experience with sample data.
Fleet maintenance · Austin
Every part on every vehicle, with the receipt.
Track each physical component — this tire, in this position, since this odometer reading. Open the measurement, service policy and history behind its status. When the record cannot support a result, the screen tells you what is missing.
How it thinks
01
02
03
Three rules it will not break.
These are not features. They are the reasons a number on this screen is worth believing, and each one cost something to learn.
No invented limits
There is no default oil interval and no default tread minimum anywhere in the system. A part with no policy reads NO INFO, never "100%". Every limit somebody enters names the source it came from.
Two counters are never subtracted
A number written on a clipboard and a number reported by a vehicle computer are different counters. The system refuses to do arithmetic across them and says in plain words why it cannot compare, rather than quietly producing a figure.
A part keeps its identity
Rotating a tire moves its position and keeps its life. Replacing it closes that record and opens a new one with a fresh baseline. You can always answer how long the part actually on the truck has been there.
Two people, two screens
Driving
In the shop
A driver and a mechanic do not want the same thing.
So they do not get the same screen. The driving view follows the rules published for in-vehicle displays: readable in one glance, targets sized for a moving truck, nothing on screen that is not a driving task.
The road comes first
- A large, clear map. Compact GPS speed with its source and age.
- A small overhead truck inside a smooth compass ring.
- One quiet vehicle-status row; urgent vehicle alerts appear without a tap. Routine service stays with the mechanic.
- If the heading is not known, no bearing is drawn at all. It never quietly points north.
- Parts and history stay locked until somebody confirms the vehicle is parked.
What is due, and what it rests on
- Every part: one status word, one line of evidence — the reading, its source, its age.
- Tires and brakes by real axle, side and inner or outer position, on a drawing of the vehicle.
- Log a reading, measure a groove, close out a repair. Typed once, in under a minute.
- Items coming due appear before they are due, so one visit covers them.
- Inspections from a template, with the odometer and the inspector attached.
Hardware
01 · Tracker
02 · OBD adapter
03 · Phone or tablet
Three pieces, and none of them are required.
Everything except the live map works with no hardware at all. A tracker automates the meter and the position. It does not unlock the product.
Two wires, no vehicle computer
A battery-powered unit on our own firmware. Position, vehicle voltage and estimated running hours — recorded as estimates, labelled as estimates, kept apart from anything measured.
Only what the vehicle really reports
An optional adapter on the diagnostic port. The system records which readings a given vehicle has genuinely produced, separately from what an adapter claims to support. Unsupported readings stay unavailable.
The screen in the cab
A mounted phone or tablet running the driving view, with a second phone for the mechanic’s records. Both open in the browser; the workspace can be added to the home screen.
Where it stands
What is real today.
Written down so nobody has to guess, including us.
Live
Vehicles, component life, meter readings, inspections, VIN decoding, device registration, and the ingest endpoint trackers report into.
Live
The mechanic's workspace and the landscape driving cockpit, on any phone or tablet.
Live
The desktop version for the office: the vehicle list and the open record side by side, keyboard shortcuts, and an Install button in Chrome or Edge that gives it its own window on Windows, Mac or Chromebook.
Live
Our own map of Austin: where every truck last reported, where each job sends it, route planning, and turn-by-turn directions with an optional voice. Built from OpenStreetMap and served from this site, so no outside map service sees your trucks.
Pending
Tracker firmware, the OBD ingest path and the phone app from an app store. The hardware is chosen; none of it is built.