05 / Hospitality platform
Restaurant Platform
Everything a new restaurant in Australia needs to own its guests — ordering, reservations, catering, delivery, loyalty, QR table service — plus a staff command centre.
- Role
- Sole engineer & designer
- Status
- Pre-launch
- Period
- 2026
- Type
- Hospitality platform
- API end-to-end tests
- 237/237
- browser tests across engines
- 359/359
- mobile LCP
- <2.5s
- spec-traced build phases
- 13
A / Architecture
Modular monolith in a Turborepo
One NestJS API with hard module boundaries — ordering, reservations, catering, delivery, loyalty, kitchen — serving a guest site and a staff command centre, with background work queued in Postgres.
00 Clients
- Guest site · Next.js 16
- Staff command centre
- QR table ordering
- 3D explore · three.js
01 Edge
- TLS proxy
- Nonce-based CSP
- Media CDN
02 API modules
- Ordering
- Reservations
- Catering CRM
- Delivery · courier API
- Loyalty · gift cards
- Kitchen · dockets
03 Async
- pg-boss jobs
- Payment webhooks
- SMS adapter
04 Data
- PostgreSQL 18
- Prisma 7
- Point-in-time backups
- Shared money/GST package
Engineering notes
- 01
Reservations that understand a dining room
Capacity pacing down to table level, waitlist and deposits, plus a catering CRM with versioned quotes.
- 02
Built for the pass, not just the browser
QR table ordering, kitchen board, Epson and Star docket printers, delivery zones with a DoorDash Drive adapter and the restaurant’s own drivers.
- 03
Found under load, fixed before launch
Load, spike and soak testing found a contention hotspot on the booking path before launch. It now serialises cleanly and fails fast under extreme load instead of degrading everything else.
- 04
Australian rules, baked in
Card-surcharge rules, ACCC wording, FSANZ allergens and WCAG 2.2 AA. Nonce-based CSP, encrypted database connections, least-privilege roles and point-in-time backups.
- 05
A venue you can walk into
A three.js explore mode where each room opens the real page, with live presence of other guests and an opt-in Afrobeat groove synthesised in Web Audio.
B / Infrastructure & delivery
How it ships, scales and stays up.
- Hosting
- Separate staging and production environments, each with isolated application and database tiers, all containerised.
- Backups
- Encrypted, point-in-time recoverable backups with monitoring and an operations runbook.
- Database
- TLS-only connections, least-privilege roles and hardened configuration.
- CI
- Format, typecheck, lint, unit, migrations and seed, API e2e, Playwright on Chromium, Firefox, WebKit and iPhone, menu-import dry run, secret scan of code and history, dependency vulnerability gate, and a check that generated docs match the code.
- Testing
- 237/237 API end-to-end and 359/359 browser tests; load, spike and soak tooling.
- Performance
- Mobile LCP under 2.5s; booking hot path spike-tested and fixed before launch.
- Compliance
- WCAG 2.2 AA, ACCC pricing wording, FSANZ allergens, Australian card-surcharge rules.
- Handover
- Architecture, OpenAPI, database diagrams, security notes, UAT scripts and a go/no-go checklist.