SaaS · Restaurant · 2026In development
AOS
A multi-tenant QR menu and ordering platform for restaurants.
Launching soon
MASA 12
Visuals and metrics are placeholders.
4
Safety layers
RLS
Tenant isolation
Faz 4
Build phase
Problem
Ordering in restaurants is slow and error-prone because of paper menus, waiter traffic and manual relaying. Duplicate orders, wrong tables and price tampering are real risks.
Solution
Guests scan the QR code at the table, browse the menu and order; staff run kitchen and service flow inside the same tenant. All business logic lives in one API, and security decisions stay server-side.
Technical highlights
- →Duplicate-order protection via idempotency key, Redis lock and a DB unique constraint
- →Server-side price snapshots (integer cents) against client price tampering
- →Tenant data isolation with PostgreSQL RLS
- →HMAC table-session tokens (8h) so table and dining period can't be overridden by the client
Stack
- Next.js
- Express
- TypeScript
- PostgreSQL
- Prisma
- Redis