GearGuard Maintenance
Maintenance tracking for equipment, work requests, teams, and work centers.
The problem
Maintenance runs on spreadsheets, chat threads, and whoever happens to remember. Requests go missing, nobody is certain who owns a job, and a work center can't tell you what's overdue without asking three people.
What we built
GearGuard puts all of it in one system: track equipment assets, raise and route maintenance requests, organize teams and work centers, and keep status visible from the request to the close. The React and TypeScript frontend runs on Vite with Redux Toolkit and Material-UI, talking to a typed Express API with Prisma, Neon PostgreSQL, JWT auth, and Zod validation. Requirements documents sit in the repository next to the code.
- Equipment registry and maintenance-request tracking in one place
- Teams and work centers for routing and clear ownership
- React TypeScript SPA with Redux Toolkit, React Router, and Material-UI
- Node and Express API with Prisma, Neon PostgreSQL, JWT auth, and Zod validation
- Documented frontend and backend specs in a structured monorepo
My contribution
What I owned on the team
Worked across the GearGuard stack: equipment and maintenance-request flows, team and work-center organization, and the React TypeScript frontend against the Prisma and Express API on Neon PostgreSQL.
How it turned out
Delivered as a team, with the requirements written down alongside the code. The repository stays private, so this page is the summary.