The Sovereign Restaurant — Blog Series - Post 2: The Cloud Trap

Sometime in the next twelve months, your inbox will receive an announcement.

A platform you already pay for — your POS provider, your workforce management tool, your ERP — will launch an AI analytics product. The email will be well-designed. The language will be confident. The headline will say something about unlocking the power of your data.

The price will be included in your existing contract, or close enough to feel like a no-brainer.

And if you sign up without reading the data terms carefully, you will have made the same mistake the industry made twenty years ago with delivery.

Cast your mind back to 2004. The choice operators faced then was whether to build delivery infrastructure — own the fleet, manage the logistics, control the channel — or outsource it to an aggregator that would handle the complexity in exchange for a percentage of every order.

Almost nobody built the fleet. The aggregator fee seemed manageable. The operational simplicity was compelling. And one contract at a time, the industry permanently transferred a revenue layer to platforms that now have structural pricing power over the operators who created their customer base.

The data sovereignty question is that decision, one layer up — and the downside is materially worse.

Here is what happens when you hand your operational data to a platform to train its models. The insight that data produces belongs to the platform, not to you. They will benchmark your performance against the anonymised aggregate of every other operator on their system. They will productize those benchmarks. They will sell the resulting intelligence to your competitors, your suppliers, and eventually to the investors evaluating your business.

You will receive a dashboard. It will be good. You will not own anything.

But here is the version of this argument that tends to land hardest in a boardroom: the platform that owns your best-selling item data, your peak trading windows, your highest-margin menu combinations, and your customer frequency patterns has a complete operational brief. It has everything it needs to design a ghost kitchen that competes directly with you — using your own historical data as the product development document.

That is not a paranoid scenario. It is the logical commercial endpoint of a platform whose relationship with operators is already deteriorating over margin, and whose cost base is structurally lower than yours.

The sovereign position — owning the inference layer, keeping the thinking inside your own architecture — is not a technology prescription. It is a contractual and commercial decision. It means ensuring, in writing, that the data your operation produces is yours: that it cannot be used to train models you don't control, benchmark you against competitors, or productize insights you generated.

Whether that means a private cloud with explicit data sovereignty clauses, an edge computing architecture, or something else will depend on your scale and your IT capability.

The principle does not depend on either.

Own the model. Or be owned by the platform.

Part two of the Sovereign Restaurant series. Full white paper available [here].