WEBVTT

1
00:00:00.000 --> 00:00:03.280
This video adaptation was generated with Notebook LM.

2
00:00:03.280 --> 00:00:04.520
Welcome to this explainer.

3
00:00:04.520 --> 00:00:07.920
Today, we're diving into European cloud sovereignty proposals and

4
00:00:07.920 --> 00:00:13.320
the very real contract management challenges businesses are facing as of September 2026.

5
00:00:13.320 --> 00:00:16.200
We're gonna cut through the noise and look closely at access,

6
00:00:16.200 --> 00:00:20.600
critical dependencies, and what it actually takes to leave a cloud service.

7
00:00:20.600 --> 00:00:25.800
And as you can see on screen, this video adaptation was generated with Notebook LM.

8
00:00:25.800 --> 00:00:27.720
Okay, here's our roadmap for today.

9
00:00:27.720 --> 00:00:30.000
First, the tech sovereignty proposal.

10
00:00:30.000 --> 00:00:32.640
Second, four proposed sovereignty levels.

11
00:00:32.640 --> 00:00:37.160
Third, managing digital contracts, and finally, testing a cloud exit.

12
00:00:37.160 --> 00:00:38.520
Let's jump in.

13
00:00:38.520 --> 00:00:40.800
The tech sovereignty proposal.

14
00:00:40.800 --> 00:00:42.080
So let's set the scene.

15
00:00:42.080 --> 00:00:44.880
It's September 28, 2026.

16
00:00:44.880 --> 00:00:48.760
You see these headlines everywhere about digital autonomy, right?

17
00:00:48.760 --> 00:00:51.440
But what does that actually mean on the ground?

18
00:00:51.440 --> 00:00:56.440
Imagine your business buys a cloud service and it's heavily marketed as European.

19
00:00:56.440 --> 00:00:58.360
Your data is hosted right here in the union.

20
00:00:58.360 --> 00:01:02.200
So your management team thinks, great, we've got total control.

21
00:01:02.200 --> 00:01:06.440
But then, renewal time rolls around and reality hits hard.

22
00:01:06.440 --> 00:01:08.680
You realize data exports are incomplete.

23
00:01:08.680 --> 00:01:11.920
There are hidden third party dependencies you didn't even know about.

24
00:01:11.920 --> 00:01:16.080
And migration, it's gonna take way longer than expected.

25
00:01:16.080 --> 00:01:18.720
The location of the servers answered one question, sure.

26
00:01:18.720 --> 00:01:22.120
But the contract left literally everything else wide open.

27
00:01:22.120 --> 00:01:26.720
To understand where this disconnect comes from, we have to look at the regulatory level.

28
00:01:26.720 --> 00:01:32.040
On June 3, 2026, the European Commission presented a technology sovereignty package.

29
00:01:32.040 --> 00:01:37.240
This included an open source strategy and the highly discussed Cloud and AI Development Act,

30
00:01:37.240 --> 00:01:38.920
or CADA for short.

31
00:01:38.920 --> 00:01:43.760
The main goal here, strengthening absolute control over digital infrastructure.

32
00:01:43.760 --> 00:01:49.080
But, and this is absolutely crucial, we have to remember what these documents actually are.

33
00:01:49.080 --> 00:01:50.800
These drafts remain proposals.

34
00:01:50.800 --> 00:01:52.920
They express a policy direction.

35
00:01:52.920 --> 00:01:55.160
Just because the commission puts out a presentation,

36
00:01:55.160 --> 00:01:59.280
doesn't magically impose a new general legal obligation on your business.

37
00:01:59.280 --> 00:02:02.320
They show us where the regulatory wins are blowing, for sure.

38
00:02:02.320 --> 00:02:04.520
But they aren't universal legal duties,

39
00:02:04.520 --> 00:02:07.280
applying to every single company just yet.

40
00:02:07.280 --> 00:02:09.960
Four proposed sovereignty levels.

41
00:02:09.960 --> 00:02:15.680
Now, what's really fascinating here is how this sort of proposal describes a framework for public sector bodies.

42
00:02:15.680 --> 00:02:18.200
And it's entirely based on risk assessment.

43
00:02:18.200 --> 00:02:21.920
Look at how it distinguishes sovereignty into four proposed levels.

44
00:02:21.920 --> 00:02:25.920
Level one, that's just an EU location, basically the bare minimum.

45
00:02:25.920 --> 00:02:29.840
Level two, steps it up, demanding independence and transparency.

46
00:02:29.840 --> 00:02:35.440
Level three goes even further, requiring EU ownership and control alongside additional criteria.

47
00:02:35.440 --> 00:02:37.200
And then, there's the gold standard.

48
00:02:37.200 --> 00:02:43.360
Level four, full transparency and control, completely free from any third country interference.

49
00:02:43.360 --> 00:02:45.000
The big takeaway here for you?

50
00:02:45.000 --> 00:02:51.440
You literally cannot describe a complex technical architecture with a single marketing adjective like European.

51
00:02:51.440 --> 00:02:55.920
As this quote nails it, a European data center location answers one question,

52
00:02:55.920 --> 00:02:59.560
but it definitely does not answer every question about control.

53
00:02:59.560 --> 00:03:03.240
Real sovereignty requires you to scrutinize every single layer.

54
00:03:03.240 --> 00:03:05.520
Managing digital contracts.

55
00:03:05.520 --> 00:03:12.160
Okay, so how do we take these macro level EU proposals and turn them into practical steps for your next purchase?

56
00:03:12.160 --> 00:03:15.680
Well, to turn a marketing term into something you can actually test,

57
00:03:15.680 --> 00:03:21.120
our first management recommendation is simply to ask, where exactly does this service operate?

58
00:03:21.120 --> 00:03:24.000
This ties right back to that level one sovereignty question.

59
00:03:24.000 --> 00:03:28.160
You need to know the physical jurisdiction of the servers running your apps.

60
00:03:28.160 --> 00:03:31.440
Next up, ask, who can actually act on it?

61
00:03:31.440 --> 00:03:34.560
Like, who really holds the administrative keys?

62
00:03:34.560 --> 00:03:37.520
Because, well, you might be buying from a European company,

63
00:03:37.520 --> 00:03:42.000
but if their core features secretly rely on a non-European third party dependency,

64
00:03:42.000 --> 00:03:44.640
your control is instantly diluted.

65
00:03:44.640 --> 00:03:48.360
Finally, ask yourself, how could the business replace it?

66
00:03:48.360 --> 00:03:51.280
Honestly, your departure deserves your utmost attention.

67
00:03:51.280 --> 00:03:54.760
Think about it, a promised data export is completely useless

68
00:03:54.760 --> 00:03:57.680
if you don't also get the metadata, the file histories,

69
00:03:57.680 --> 00:04:02.000
or the technical documentation you need to actually set it up somewhere else.

70
00:04:02.000 --> 00:04:07.440
Your control over a service absolutely depends on your documented ability to replace it.

71
00:04:07.440 --> 00:04:13.360
And keep in mind, a slick sales pitch is way too general to establish what you're actually owed.

72
00:04:13.360 --> 00:04:15.600
You've got to take the answers to those three questions

73
00:04:15.600 --> 00:04:19.360
and compare them directly against your written contractual documents.

74
00:04:19.360 --> 00:04:24.320
Finding out your precise responsibilities requires you to look hard at the contract itself.

75
00:04:24.320 --> 00:04:26.480
Testing a cloud exit.

76
00:04:26.480 --> 00:04:31.760
So, because a dependency doesn't necessarily mean you need to make a panicky overnight change,

77
00:04:31.760 --> 00:04:35.920
you should definitely conduct a trial export before you renew a contract.

78
00:04:35.920 --> 00:04:38.560
You want to know the real costs and timing, right?

79
00:04:38.560 --> 00:04:42.560
Here are four practical management recommendations to evaluate your readiness.

80
00:04:42.560 --> 00:04:46.560
One, request a trial export using suitable test data.

81
00:04:46.560 --> 00:04:49.600
Two, check it for completeness and reusability.

82
00:04:49.600 --> 00:04:53.200
Three, write down every single manual operation required.

83
00:04:53.200 --> 00:04:54.880
This is where you find the real friction.

84
00:04:54.880 --> 00:04:59.200
And four, compare that real-world experience with your written commitments.

85
00:04:59.200 --> 00:05:02.400
Now remember, these are strictly management recommendations.

86
00:05:02.400 --> 00:05:06.960
You should note what the test could not establish, rather than pretending an incomplete exercise

87
00:05:06.960 --> 00:05:09.200
as a full-blown migration assessment.

88
00:05:09.200 --> 00:05:11.200
And this is absolutely vital.

89
00:05:11.200 --> 00:05:14.080
A migration test evaluates your management readiness,

90
00:05:14.080 --> 00:05:16.720
but it does not certify legal compliance.

91
00:05:16.720 --> 00:05:20.800
This is just practical advice to aid your discussions, not a universal legal duty.

92
00:05:21.600 --> 00:05:23.440
As you start putting this into practice,

93
00:05:23.440 --> 00:05:26.320
make sure you assign responsibility to someone on your team

94
00:05:26.320 --> 00:05:28.880
to actually monitor these critical dependencies.

95
00:05:28.880 --> 00:05:30.640
And keep our timeline in mind.

96
00:05:30.640 --> 00:05:34.560
This specific research closed on September 28, 2026.

97
00:05:34.560 --> 00:05:36.320
Because CADA is still a draft,

98
00:05:36.320 --> 00:05:39.280
you've got to continuously monitor further legislative developments

99
00:05:39.280 --> 00:05:40.800
before you make any final decisions.

100
00:05:41.600 --> 00:05:46.480
Ultimately, a replacement option only becomes truly useful when it has three things.

101
00:05:46.480 --> 00:05:48.720
An owner, an estimate, and a timetable.

102
00:05:49.280 --> 00:05:51.680
Despite all the fancy marketing adjectives,

103
00:05:51.680 --> 00:05:53.840
you have to ask yourself the hard question.

104
00:05:53.840 --> 00:05:55.600
If you had to flip the switch tomorrow,

105
00:05:55.600 --> 00:05:58.160
would your business actually survive the exit?

106
00:05:58.160 --> 00:06:01.760
Or are you locked into a European cloud that you can never really leave?

107
00:06:02.640 --> 00:06:04.400
Thanks for joining me for this explainer.

108
00:06:04.400 --> 00:06:06.240
Now, go check your contracts.
