Record drives and turn them into clear, privacy-aware session cards designed for keeping or sharing.
Product directionDriver / A Vex product
Your car deserves more than a trip log.
Driver connects every drive, modification, issue, and confirmed fix to one living vehicle history.
Early accessVehicle recordDriveBuildContextIn development
Three layers. One vehicle record.
Driver is designed so each layer strengthens the others without making social activity or future intelligence a requirement.
Connect parts, modifications, service, issues, milestones, and owner-confirmed details to one vehicle record.
Product directionUse that structured history later to explain relationships, evidence, limits, uncertainty, and when inspection is required.
Later roadmapA collectible view of a real history.
The card is a live product visualization. It is not a final application screenshot.
DriverIn development
Vehicle profileOne history, connected.
Product visualization
DriveSession card
A drive becomes a composed record with privacy controls kept visible.
- Route privacy
- Start and end hidden
- Share state
- Private by default
- Session context
- Connected to this vehicle
Privacy is part of the route.
Recording should keep route-start, route-end, visibility, and sharing choices explicit. The product direction treats privacy as core behavior, not a hidden setting.
Better context, without false certainty.
Mechanical intelligence is a later roadmap layer. The goal is to use a vehicle's confirmed history to explain evidence, relationships, limitations, and the point where inspection is required.
It will not replace a qualified mechanic or physical inspection.Starts withOwner-confirmed vehicle history
Should showEvidence and relevant relationships
Must exposeLimits and uncertainty
Escalates toProfessional inspection when required
Follow Driver as it develops.
Driver is an active Vex product in development. Early-access routing will use the confirmed company contact destination.
