Case study
logiparty
Logiparty is a multi-tenant web app for third-party logistics companies that run warehouse, fleet, and crew for live events, deliveries, and corporate jobs. Each company gets its own workspace on its own subdomain and a white-label portal where clients request jobs and see only their inventory. The product treats the job as the unit of work: trucks, crew, and client-owned gear stay tied to that job until load-out releases them.
What it is
How a job moves
When a job is upcoming or ready, the inventory and vehicles assigned to it are reserved. Staff see what is spoken for before they promise the same gear elsewhere.
Under the hood
Next.js on Vercel, Neon Postgres with row-level security, wildcard DNS for per-company subdomains, auth with role-based access, Cloudflare R2 for private documents with signed URLs, and branded transactional email. The architecture is built for isolation first, then features on top.
How this shipped
I shaped the product direction and system design, wrote implementation briefs for coding agents, reviewed diffs and production behavior, and kept ownership of what ships. The case study focuses on the product; the process is simply how this codebase stayed coherent while moving fast.
logiparty.com (opens in a new tab)Source on GitHub (opens in a new tab)