Fleetwright Cloud

FleetWright SaaS - Fleet maintenance management platform

Fleetwright Cloud

What It Is

Fleetwright Cloud is a SaaS platform for fleet maintenance management. The idea is simple: if you’re running a fleet of vehicles, whether that’s a small business with a handful of vans or something larger, keeping track of maintenance schedules, service history, and repair work is a real problem. Spreadsheets fall apart fast. Fleetwright Cloud is built to replace that mess.

It’s a SaaS web-based platform. You log in, you manage your fleet, you stop losing track of which truck is due for an oil change.

Why I Built It

Most fleet management software is either way too expensive for small operators or buried in features nobody needs. I wanted something that covers the core maintenance workflow without requiring a six-month onboarding contract or an enterprise sales call. Building it as a SaaS means it can serve multiple tenants from one deployment, which keeps the operational overhead low.

How It Works

The backend is PHP, which is a deliberate choice for a project like this. It’s portable, well-understood, and pairs cleanly with traditional web hosting environments. The frontend is HTML, CSS, and JavaScript. No heavy framework. The goal was to keep the stack approachable and easy to maintain long-term.

Deployment is handled through Docker. The Dockerfile makes it straightforward for me to spin up a consistent environment without wrestling with server configuration by hand.

What It Covers

Based on what a fleet maintenance platform needs to do, here’s what the project is built around:

  • Tracking vehicles and their service records
  • Scheduling and logging maintenance tasks
  • Multi-tenant support so one instance can serve multiple accounts
  • A web interface that works without installing anything on the client side
  • Integration with GeoTab Telemetric
  • One click work order generation for Preventative Maintenance, DTC Fault Codes and Recall Notices.

FleetWright also:

Decodes the VIN to make/model/year (so we can call the recalls endpoint).

Returns 17 spec fields we surface on the equipment detail page (GVWR class, drive type, brake system, fuel, engine, transmission, plant location)

Automatically checks each VIN against the NHTSA federal recalls database (the same data source the official nhtsa.gov/recalls site uses) and decodes the full vehicle specification: GVWR, drivetrain, brake system, engine, transmission, directly from the manufacturer’s vPIC submission.

Current Status

The project is actively developed. It’s not a finished product sitting in a drawer. I’m adding to it, fixing things, and refining the feature set as real-world use cases come up.

Tech Stack

  • PHP — backend logic and server-side rendering
  • HTML / CSS / JavaScript — frontend, kept intentionally simple
  • Docker — containerized deployment

Source Code

The source code repository on my self-hosted Forgejo instance is private.

Marketing site: Fleetwright – Everything You Need to Manage Fleet Maintenance