Ghost_Kitchen/docs/adr/0001-one-server-per-kitchen.md

One server and database per Kitchen

Even though this codebase is built as a reusable template deployed to many ghost-kitchen operators, each Kitchen runs its own independent server and database with exactly one Brand — there is no central multi-tenant backend or cross-kitchen data layer. We chose this over a shared multi-tenant SaaS backend because each Kitchen's server talks directly to that Kitchen's own microcontrollers/machines, and keeping deployments fully independent avoids coupling physical hardware control to a shared cloud service. The trade-off: no built-in cross-kitchen reporting or central admin — any future need for that requires a separate aggregation layer, not a schema change to this one.