<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Control Plane on Sovereign Shift</title>
    <link>https://sovereignshift.eu/tags/control-plane/</link>
    <description>Recent content in Control Plane on Sovereign Shift</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Wed, 10 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://sovereignshift.eu/tags/control-plane/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The Hidden Control-Plane Problem: SSO, Email, DNS, and File Storage</title>
      <link>https://sovereignshift.eu/blog/hidden-control-plane-problem/</link>
      <pubDate>Wed, 10 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://sovereignshift.eu/blog/hidden-control-plane-problem/</guid>
      <description>&lt;p&gt;When organisations list their cloud dependencies, they typically produce a tool inventory: we use Slack for chat, Salesforce for CRM, Jira for project management. Each tool gets its own line item, its own risk rating, its own migration plan.&lt;/p&gt;&#xA;&lt;p&gt;This approach misses the point. The tools are the visible layer. Underneath them sits a control plane: a small set of services that every tool depends on and that determines who can access what, where data flows, how systems find each other, and where files live. The control plane is the real dependency. And in most European organisations, the entire control plane is operated by one or two US companies.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
