News
The supermarket cloud vs. the artisan chef: Why you need a recipe before you shop
Why the absence of a cloud strategy at board level is quietly costing you your digital sovereignty.
We all know the feeling. You're tired, it's been a long day, and you walk into the supermarket hungry with no list and no plan. You head straight for the ready meals and grab a lasagne. You slide it in the microwave, and five minutes later dinner is on the table. No effort, instant reward.
But anyone who eats this way regularly knows the downsides. You pay a premium for packaging and marketing. The ingredients list is full of additives you'd never choose yourself. And it's not exactly nourishing. It silences the immediate hunger, but it doesn't feed you. Over time, a diet of ready meals is unsustainable.
We see this same decision play out repeatedly in how organisations build their IT infrastructure. Time pressure on a project, a market demanding fast innovation, the temptation to walk into a public cloud hungry and grab the first thing off the shelf is real. The big tech companies make it easy. Generous onboarding credits, polished marketing promises, a catalogue full of ready-to-use services. Click, deploy, done.
A quick operational fix for a strategic foundation
But read the ingredients list on the back of the packaging, and things look different. Hidden costs. Geopolitical dependencies. Vendor lock-in that nobody thought about in the rush.
To be clear: the public cloud offers real advantages in speed and innovation, and organisations that go this route are not automatically making a mistake. But what we see consistently is that the choice of cloud provider is made as an operational decision rather than a strategic one. Driven by the urgency of the moment, a temporary promotion, or the preference of whoever happened to be in the room first.
Meanwhile, your cloud infrastructure has become the foundation of your entire organisation. It is not a commodity like a mobile contract. It should be a boardroom-level strategic decision one with the same weight as choosing where to locate your headquarters. The comfort of the early days can quietly turn into an unhealthy dependency you cannot easily escape.
The ingredients list of the market today
This risk is more urgent now than it has ever been. We live in a world where geopolitical relationships are shifting and the power of American Big Tech is under increasing scrutiny. European legislation - including DORA (Digital Operational Resilience Act) and NIS2 - is not coincidentally pushing organisations to take a hard look at their operational resilience and contingency scenarios.
This is not a theoretical discussion. The evidence from recent months is concrete:
- The AI export block. The US government recently blocked the export of specific advanced AI models from Anthropic outside the United States. If your innovation strategy relies on American AI licences, you can be grounded overnight.
- The sanctions list trap. Members of the International Criminal Court in The Hague were suddenly and completely locked out of their Microsoft environment after appearing on a US sanctions list. Email gone. Documents gone. Teams gone.
- The cloud-enforcement collapse. Amsterdam Trade Bank went bankrupt within two weeks after their Azure environment was shut down as a result of international sanctions. Not an IT incident, a corporate death sentence.
- The legal threat to data transfers. Recent developments in US corporate law have once again destabilised the legal foundation for EU-US data transfers. American tech giants can be compelled by their own government to hand over data, regardless of European privacy legislation.
When an American provider decides to change its terms unilaterally, or when geopolitical trade restrictions and court rulings directly affect your data flows, you can no longer look away. If your data and platform are deeply entangled with the proprietary systems of a single hyperscaler, you may have an exit strategy on paper. In practice, you are grounded
Recipe first, then go shopping
When an organisation decides to define the recipe before it shops, to make architecture decisions before choosing a provider, something fundamental changes. At the drawing board, we design for a cloud-native architecture based on open standards. We build the platform so that it does not depend on the proprietary, closed tools of any single vendor.
By building on open standards, it stops mattering to your applications where the compute comes from. AWS, Azure, a local European data centre, your code and your data stay portable. The standards belong to you, not to your vendor. That is the blueprint that makes your platform future-proof, regardless of what sits underneath it
Returning control to where it belongs
Everyone in this market has a commercial interest, including us. Let's be transparent about that. But an honest conversation with an organisation that leans heavily on hyperscaler ready meals has to start with the same transparency about the long term.
When an organisation no longer understands or manages its fundamental infrastructure in-house, control quietly shifts outward. You become dependent on the decisions others make, about pricing, features, and terms. The control over your digital future does not belong in the boardroom of a foreign tech giant.
So before your next infrastructure decision: are you still reaching for the ready-made lasagne?
At TrueFullstaq, we help organisations take back control and build it into their own teams. Not by telling them to leave the supermarket, the public cloud has genuine value. But by anchoring the foundational knowledge of cloud-native infrastructure and open standards within their own organisation. Because the best recipe is the one you own yoursel
