Back to Projects
P
Engineering

PodTrust

Full-Stack Developer

NestJSPrismaPostgreSQLReact NativeExpoSupabase

About the Project

PodTrust is an escrow product — money is held until both sides of a transaction are satisfied, which matters in markets where buyer and seller have no prior trust relationship. The product is split across independent codebases: an admin web application with its own REST API for operating the escrow product, a NestJS platform API, and an Expo/React Native mobile app for the end users who actually open and settle escrow agreements.

What It's Made Of

Mobile app

Expo · React Native · Supabase · turbo

Where end users open, fund, track and settle escrow agreements, and raise a dispute when a deal goes wrong. Built in an npm + turbo workspace on a Supabase backend, with the typed client and validation schemas generated from the API spec rather than hand-written, so the app and the API cannot quietly disagree about an agreement's shape.

Admin operations console

pnpm workspaces · web app + REST API

The operator surface for running the escrow product: reviewing agreements, moving them through their lifecycle, adjudicating disputes, and releasing or refunding funds at settlement. It ships with its own REST API in the same workspace, which is why this directory is a workspace of its own rather than a page in the platform app.

Platform API

NestJS · Prisma · PostgreSQL · Docker

The escrow state machine and the system of record: agreements, parties, funding, milestones, releases and disputes, with every transition explicit and auditable. Passport JWT with argon2 hashing, documented through Swagger, and exported as an OpenAPI spec that drives client generation for the other two surfaces. Containerised with health checks and structured logging.

Key Highlights

  • Built the admin operations console for managing escrow agreements, disputes, and settlement
  • Shipped the mobile app in Expo/React Native on a Supabase backend, in a turbo-managed workspace
  • Set up an OpenAPI codegen pipeline that generates a typed React client and Zod schemas from the API spec
  • Secured the API with Passport JWT and argon2 password hashing, documented through Swagger
  • Added operational plumbing the product needed to run: health checks, structured logging, and a containerized API

Technical Challenges

Escrow is unforgiving about state — an agreement in the wrong status means someone's money is stuck. The hardest part was modelling the state machine so that every transition was explicit and auditable, and making sure the mobile app and the admin console could never disagree about what state an agreement was in. Generating the client types directly from the API spec removed a whole class of drift bugs between the three codebases.