Repair Ticket Tracking Portal

A separate public app, deployed on its own, that reads from the shop's Supabase project through one SECURITY DEFINER Postgres function. It needs an exact ticket number or phone match and returns only customer-safe fields.

• React
• TypeScript
• Vite
• Tailwind CSS
• Supabase

Customers want to check their repair without calling, but opening the shop database to the public would expose every customer's data.

• ▹Giving customers useful status without leaking anyone else's data

• ▹Look up a repair by ticket number or phone number
• ▹Returns no internal notes, no other customers' details and no financial breakdown
• ▹Separate repository and deployment from the staff app, so staff code never ships to public traffic
• ▹Static build that can sit on any host or subdomain

• ▹Expose one database function instead of granting the public role SELECT on the table, because row-level security applies per role, not per query
• ▹To add a field, extend the function rather than widening table access
• ▹Keep the public app in its own repository and deployment

Content needed: measured results with period and method. Never estimated.

Evidence

• ▹Design rationale and setup are documented in a private repository README

Content needed: what you would do differently

• AI Engineering · Full-Stack

  StockIQ

• AI Engineering · Full-Stack · Geospatial

  NAIMOS Intelligence

• AI Engineering · Applied ML

  Ghana Image Captioning