Why this exists
The story in two paragraphs.
Every fleet shop we've walked into runs on a stack of tools that don't quite fit. A whiteboard of open repairs. An Excel sheet of meter readings nobody trusts. Sticky notes on the rolling toolbox. A telematics dashboard that's great for the office but ignored by the mechanic. Three or four years ago we figured: someone should build a maintenance + work-order + tool tracking app that crews actually use every day, prices fairly, and ships with the open API that integrations-heavy fleets need on day one.
DirtFleet is that. The product is opinionated about what it is (maintenance, work orders, tool tracking, project P&L, OSHA prep, certified payroll) and what it deliberately isn't (FMCSA-certified ELD, full GL, estimating, inspection-first DVIR). It lives in the same stack as your Samsara / Geotab / John Deere Operations Center, not on top of them.
Operating principles
Five filters.
Every product decision passes through these. When they conflict, the customer wins.
Three taps beats three screens
Mechanics + drivers + foremen aren't going to learn your software. The app exists to log a meter reading in 3 taps, not to be admired in marketing demos.
Honest scope wins long
The temptation to claim every feature is real. We say no to features that don't fit — even profitable ones — because the customers who stay are the ones who weren't oversold.
Pricing aligned with the customer
Per-asset, not per-seat. A 25-truck fleet with 5 drivers, 2 mechanics, and 1 manager is billed for 25 items, not 33 users. The math should reward you for adding the crew the truck needs.
Integration-first product
Every feature ships with a public REST endpoint + webhook event before the in-app UI is final. We treat the API as the spine of the product, not an afterthought.
Documented decisions, public roadmap
Engineering choices are written down (docs/* in the repo) so the next person can change them with context. The customer-facing roadmap is public so buyers can plan around what we ship.
Timeline
Where we've been.
- Early 2026
First version of the hours-logging app + photo-of-meter shipped to a single construction shop. Mechanic uptake was instant; manager uptake came after we added the auto-flag system.
- Spring 2026
Beta cohort onboarded — five fleets across construction, ag, and equipment-rental. Quick Log + auto-PM + offline outbox shipped.
- Today
Public API + tool tracking + work orders + projects + incident module + 5 industry deep-dives + the integrations directory. Punch list from launch is meaningfully complete; next phase is paying-customer growth.
Curious?
Try with your fleet.
30-day free trial. Same team that wrote this page is who answers your support email.