Platform dependency is quietly becoming infrastructure
Organizations increasingly treat third-party platforms with the permanence once reserved for utilities — without the regulatory scaffolding that follows.
Over the last decade, the operational dependence on a small set of platforms has shifted from a procurement decision into something closer to structural infrastructure. The shift has been gradual enough that few organizations have a moment in which they decided it.
What is notable is not the dependence itself, but the absence of the institutional scaffolding that historically accompanies infrastructure: service guarantees with meaningful recourse, regulatory oversight, shared standards, interoperability mandates. The dependency has matured faster than its governance.
This produces a familiar drift pattern: the cost of switching grows quietly, the assumption of continuity hardens, and the operational imagination narrows. Eventually the platform is not a vendor but a constraint on what is thinkable.
The remedy is not dramatic. It is the ordinary discipline of documenting dependencies, maintaining exit paths, and preserving in-house literacy in the systems that have been delegated outward.