Dispatch platform · Web + mobile · 2026

JobsiteX: on-demand trucking for job sites, with live dispatch

Customers book a truck for a pickup and drop-off; nearby drivers get the job over WebSocket and the first to accept wins. Stripe Connect pays the drivers.

Client code is private. This describes the engineering
JobsiteX, Dispatch platform · Web + mobile
Client
JobsiteX
Industry
Logistics
My role
Backend lead; mobile contributor
Year
2026

Overview

A two-sided hauling platform: a NestJS + Prisma API that handles fare estimation, job broadcast to nearby drivers, live driver location, a booked-to-delivered status timeline, Stripe payments with Connect payouts and withdrawals, and an admin console for driver verification. React Native apps for customers and drivers, a React admin dashboard.

The problem

Dispatch has to feel instant on both sides. A customer posts a job and needs a truck within minutes; drivers on a site with bad signal need the offer to reach them once and only once. Money moves in two directions (customer payment in, driver payout out) and drivers must be verified before they see a single job.

What I built

  • Job broadcast over Socket.IO to drivers in range; first to accept gets it, everyone else is told it is gone. Direct booking of a known driver checks availability and distance first.
  • Fare estimation per truck type, then a booked, arrived, loaded, in transit, delivered timeline with live driver location streamed to the customer.
  • Driver onboarding: CDL, insurance and DOT uploads to S3 with OCR extraction, admin review and approval before the driver can go online.
  • Stripe payment intents and webhooks for customers; Stripe Connect onboarding for drivers, earnings, and withdrawals with admin approval.
  • Google and Apple sign-in, OTP verification, FCM push, CMS pages for policy and help; BullMQ + Redis for notifications and queues; Docker + GitHub Actions deploys.

Outcome

Real-time

Job broadcast and live location over Socket.IO

Stripe Connect

Driver payouts and withdrawals

4

Surfaces: customer app, driver app, admin, API

Engineering decisions

  • First-accept dispatch over WebSocket rooms
  • Two-directional money: intents in, Connect payouts out
  • Document OCR feeding an admin approval queue