07/10/2026

Sovereign by Design

Imagine it is 07:00 on Monday morning and your CIO calls. A major technology vendor has suspended service in your region. What breaks?

Most organisations can tell you what they spend with that vendor, which licences they own and roughly where the software is deployed. Far fewer can name every critical service, application and business process that depends on it straight away.

That is why digital sovereignty belongs in the ITAM conversation. It covers more than where your data is hosted or whether your suppliers are European. The practical question is whether your organisation can keep making its own decisions about its IT estate when circumstances change.

Sovereignty is about options

Geopolitics, regulation, sanctions, acquisitions, subscription models and growing SaaS and AI dependency all change technology risk. A supplier can change its licensing model, a service can become unavailable, and an acquisition can alter commercial terms. Jurisdiction can also affect how technology or data may be accessed.

For ITAM, that gives us five dimensions to track: data location, jurisdiction, vendor dependency, licensing control and operational continuity.

What you are after is optionality: understanding your dependencies and keeping credible choices when circumstances change.

You need to see your dependencies

SAM already gives us much of the foundation. Discovery, inventory, entitlements, contracts and usage data say a lot about the estate. Sovereignty needs one more layer, and these questions are where the gaps usually are. Where is the data hosted? Which jurisdiction applies? Which subprocessors and infrastructure does the service rely on? What happens if the vendor is acquired? Can we move our data? Is there a viable alternative?

Answering them turns an asset inventory into a dependency map. The dependency nobody knew existed is often the biggest risk.

Licensing is a sovereignty issue too

Say your largest infrastructure vendor is acquired. Perpetual licences disappear, subscription bundles become mandatory and your renewal quote multiplies. What leverage do you have?

Accurate usage data lets you right-size. Contract knowledge shows which protections you have. Knowing the alternatives tells you what leaving would really cost. Without these, negotiating is hard because the supplier knows switching could take years. Your strongest leverage is a credible option to leave.

You do not have to keep changing suppliers for this to work. Staying with a strategic vendor by choice is very different from having no realistic way to leave.

From blind to sovereign by design

Organisations can approach sovereignty in stages. A blind organisation has little visibility into jurisdiction, dependencies or exit options. An aware organisation understands its major vendors and systems. A managed organisation records these risks, maps dependencies, plans renewals and documents exit strategies.

A sovereign-by-design organisation takes it further and builds sovereignty into sourcing, contracting, architecture and governance. Its critical dependencies have tested alternatives, protective contract clauses are standard, and continuity plans are rehearsed rather than only documented.

The goal is deliberate dependency instead of accidental dependency.

Start with the next 90 days

You do not need a multi-year programme to begin. Take your ten most critical technology vendors. In the first 30 days, map their key attributes and dependencies. In the next 30, enrich your SAM and CMDB data and review upcoming renewals, exit rights, portability and change-of-control clauses. In the final 30, run a tabletop exercise and produce a one-page sovereignty heatmap for the CIO.

That changes what ITAM gets asked. Instead of only “What software do we have and what does it cost?”, ITAM can also answer: What do we depend on? Where are we exposed? What options do we have if something changes?

Nobody can predict the next acquisition, regulatory intervention, geopolitical event or licensing change, but you can understand the impact before it happens.

So start with one practical objective: build a sovereignty map for your ten most critical technology vendors before your next major renewal. Then, when the CIO calls at 07:00 and asks, “What breaks?”, you can answer: “Here’s the list.”

Recent posts

Join our events!

We host various events from time to time. Register now and be up to date!
Do not miss out!