SUMMARY: Control plane concentration occurs when one interface, identity, provider, or approval path can change many systems that appear independent at the service layer.
A system can look distributed while its authority remains centralized. Files may live in several repositories. Applications may run across regions. Teams may use different vendors, channels, and databases. Yet the same administrator account, identity provider, billing relationship, domain registrar, or management console can still suspend, redirect, revoke, or reconfigure all of them.
The visible infrastructure is the service plane: the places where work happens. The control plane is the layer that decides who may change that infrastructure and which instructions the system will obey. Concentration at this layer creates a shared failure mode that ordinary asset inventories often miss.
Four Forms of Concentration
Identity concentration: one email account, single sign-on provider, device, or recovery channel unlocks several administrative surfaces. Separate passwords do not create independence if every reset returns to the same inbox.
Interface concentration: one dashboard governs domains, deployments, storage, access, and billing. Convenience compresses many decisions into one session and expands the consequence of a mistaken or compromised action.
Provider concentration: services use different product names but share the same corporate account, cloud region, support desk, policy engine, or payment relationship. A single provider decision can therefore cross boundaries that the architecture diagram treats as separate.
Authority concentration: only one person or role can approve emergency changes. The system may have technical alternatives, but those alternatives remain inert when the authorized operator is unavailable.
Why Backups Do Not Solve It
A backup preserves state. It does not automatically preserve the authority needed to restore that state somewhere else. Recovery may still depend on the same registrar, identity provider, encryption key, billing account, or approval queue that failed. This is why a dependency register should record control relationships as well as technical components.
Use a route substitution matrix to test whether an alternate route can be activated without borrowing the primary route’s control plane. If both paths require the same credential or decision maker, they are alternatives in appearance only.
The Practical Test
Choose one administrative surface and ask three questions: what else can this identity change, where does its recovery path terminate, and who can act if the normal authority disappears? Repeat the exercise for domains, hosting, publishing, communications, payments, and archives. The repeated names reveal the actual concentration map.
Field assessment: infrastructure is not meaningfully distributed when every important change still passes through the same hand, account, or gate.
Continue the discussion in the Clandestinia forum.