WIGTN CREW

wigex travel expense tracker

With a travel expense tracker as the excuse, this project experiments with the team's standard structure for running backend and mobile in one repository.

Role: Backend · Mobile · Infrastructure
Period: In progress
Stack: NestJSPrismaSupabaseExpoGCP Cloud Run

MONOREPO

Expo appTravel ledger UI

NestJS + PrismaDomain API

CLOUD

GCP Cloud RunContainer deploys

SupabasePostgres and auth

App / clientNativeServerWorkerStorageExternal

Backend and mobile travel in one repository; the server ships to Cloud Run, data lives in Supabase.Hover a block to highlight its flows. Drag to pan.

01What it is

A travel expense tracker where a NestJS and Prisma backend and an Expo-based mobile app are managed together in a single repository. The server is deployed to GCP Cloud Run and the data lives in Supabase. More than the features themselves, the real goal is refining a monorepo structure and deployment path the team can pick up directly whenever a new project starts.

02Right now

This project is ongoing. The backend domain design, the mobile screens, and the Cloud Run deployment pipeline are in place, and I am sorting out which parts to carry over into the team's standard template.