Straight answers.
No. Manual vehicle records, web and mobile inventory, and provider-neutral VIN decoding do not require hardware. Optional OBD2 adapter wiring exists but still needs physical adapter and real-vehicle acceptance. Spreadsheet import and photo-assisted odometer capture remain launch work; Geotab and Samsara are later integrations.
Offline-first sync is a protected launch requirement with a real foundation in validation: a PowerSync-backed local store, scoped lifecycle, conflict handling, and credential rotation. Design partners will test queued writes, reconnect behavior, and the airplane-mode soak gate before public launch.
The current design-partner target is trades businesses with roughly 5 to 50 vehicles. Final packaging and per-vehicle pricing are being validated with those partners.
The current build has executable foundations for vehicle lifecycle controls including archive/restore and status-filtered lists, web and mobile inventory, VIN decode, guided walkarounds, attributed maintenance recommendations with web and mobile read/refresh surfaces, maintenance status and online work orders, OBD2 scan history, inspection template building, password signup, OAuth plumbing, workspace invitations, member lifecycle controls, tenant audit history, tenant isolation, durable outbox/event delivery, and repository security and behavior checks. Offline field completion, odometer capture, imports and exports, production media upload, licensed maintenance data, password-reset email delivery, and production invitation delivery are not complete yet.
The product is designed around portable CSV or JSON exports, including custom fields. The final retention and deletion process will be documented in the customer agreement before paid service begins.
Design partners receive founder-assisted setup, early product access, and a direct role in roadmap decisions in exchange for regular feedback. Pricing is still being validated and will be confirmed in writing before any paid commitment.