Multi tenant
Every record is tenant-scoped from the schema up.
Not a point of sale
Hospitality OS models the whole restaurant — floor, service, production, inventory, purchasing, guests, devices — as independent domains that communicate through business events. This build is the platform foundation: architecture first, features next.
Every record is tenant-scoped from the schema up.
Writes are queued and replayable; service never stops.
Domains publish facts instead of touching each other's data.
No restaurant-specific logic is ever compiled in.
Thirteen domains, one platform
Floor to pass
Seating, ordering, firing and running modelled as one service cycle.
Production aware
Kitchen and bar are first-class domains, not printer targets.
Stock to supplier
Inventory and purchasing stay separate, connected by events.