The UK government is encouraging organisations like the NHS and Ministry of Defence to prioritise British technology, with a particular focus on AI and emerging platforms.
It’s a serious move, and it reflects wider issues around security. Geopolitical pressure, economic uncertainty, and increasing reliance on a small number of global technology providers are forcing organisations to think more carefully about resilience.
But there’s a more immediate question that sits underneath all of this.
Do you know where your infrastructure actually resides, how it behaves, and what it depends on?
Because for many organisations, that picture isn’t as clear as it should be.
Visibility, not just ownership
In many NHS environments, the issue isn’t a lack of capability or investment. It’s a lack of clear visibility across the estate.
Over time, systems are introduced to solve specific problems. They’re integrated, extended, and adapted. New layers are added, often under time pressure.
The result isn’t “messy.” It’s something more complex:
- dependencies that aren’t fully documented
- infrastructure spread across multiple environments
- workloads that have evolved beyond their original design
- monitoring that highlights symptoms rather than root causes
Everything functions, but understanding how it all fits together takes time. And when something goes wrong, that lack of clarity becomes a risk.
Where Linux fits into this conversation
This is where the conversation around open technologies becomes more relevant.
Linux underpins a significant proportion of NHS infrastructure already, particularly in clinical systems, research environments, and high-performance workloads. It’s not new, and it’s not niche.
What’s often overlooked is what Linux represents in this context:
- transparency in how systems operate
- flexibility in how they are deployed and managed
- the ability to build infrastructure that isn’t tied to a single vendor’s roadmap
In the context of sovereignty, there’s sometimes hesitation because commercial distributions like Red Hat are US-based. That’s true at the company level.
But the technology itself is global, open, and not owned in the same way as proprietary platforms. And importantly, it can be supported, managed, and developed by UK-based providers.
The real risk: unknown dependencies
When we work with organisations, the biggest risks rarely come from a lack of tools.
They come from unclear dependencies.
- a service relies on something no one realised was critical
- an update introduces unexpected behaviour
- a change in one area impacts something entirely different
These aren’t edge cases. They’re a natural byproduct of environments that have evolved over time without a consistent view across the whole estate.
And they’re difficult to manage if:
- you don’t have full visibility
- you can’t easily trace how systems interact
- or you’re reliant on multiple third parties to interpret what’s happening
That’s where resilience starts to break down.
Reframing “buy British”
The current policy direction focuses on where new technology is sourced. That matters. But it’s only part of the picture.
A more useful starting point for most organisations is:
- Where does our current infrastructure actually sit?
- What are we dependent on?
- How quickly can we respond when something changes?
Because once those questions are answered, decisions about suppliers, platforms, and partners become far more informed.
Repatriation and resilience
There’s also a growing conversation around repatriating workloads. Not everything needs to move. But in certain cases, organisations are actively looking to:
- bring critical systems closer to home
- reduce reliance on global hyperscalers for sensitive workloads
- ensure they have stronger oversight of how services are delivered
That doesn’t mean abandoning cloud or existing platforms. It means being more deliberate about where things run, and why.
And in that context, open technologies like Linux provide a practical foundation for building infrastructure that is:
- portable
- observable
- and not constrained by a single vendor ecosystem
A practical next step
For most organisations, this isn’t about wholesale transformation.
It’s about getting a clearer view of what’s already there.
- mapping dependencies
- identifying areas of risk
- understanding where visibility is limited
- and deciding where greater control and resilience are needed
From there, you can make informed decisions about whether to:
- optimise what you have
- introduce more open technologies
- or repatriate specific workloads
At Tiger Computing we can help you leverage Linux and open-source tools to ensure your stack remains portable, vendor-agnostic, and – most importantly – under your control. It’s about building a foundation that doesn’t lock you in, but does give you the visibility you’ve been missing.
Book a brief call with our Linux specialists to explore how this could fit into your current infrastructure goals.
