Plaet
Our own restaurant-management SaaS, grown from a single-location tool into a multi-tenant platform: one system now runs the floor, the kitchen and the register for several restaurants at once, each one walled off from the others.
More views
At a glance
- Backend Modules15 modules, 109 endpoints
- Access Control21 permissions, 5 roles
- Database Models22 (Prisma)
Problem
The original tool only ever ran one restaurant's floor. Turning it into something worth selling meant the data model, the auth system and every query in the app had to become tenant-aware — without any one restaurant ever seeing another's orders, menu or staff.
Solution
Rebuilt the core around a tenant id carried automatically through every request via AsyncLocalStorage, rather than a parameter every developer has to remember to pass, plus a granular role-permission system covering five staff roles — from cashier to super-admin — and a kitchen board staff actually use during service, not just for demos.
Results & Impact
- One codebase now runs any number of restaurants, each fully isolated at the query level
- A real-time kitchen Kanban replaced the paper ticket rail, with drag-and-drop and swipe support for tablets
- A prepaid "ticket book" system — common in Colombian workplace cafeterias — built in as a first-class payment method, not bolted on