Technological monoculture

A technological monoculture is a condition in which a large fraction of a critical system depends on a single technology, vendor, or implementation, creating correlated failure risk that is invisible during normal operations. The concept originates in agricultural ecology, where monoculture crops are vulnerable to pathogens that can destroy entire harvests, and it applies with equal force to technological systems.

In computing, technological monocultures arise when dominant market positions, network effects, or regulatory requirements cause diverse organizations to converge on identical software stacks, hardware architectures, or service providers. The 2024 CrowdStrike outage is a canonical example: millions of organizations depended on the same kernel-level security software, and a single faulty update propagated across all of them simultaneously. The organizations were independent in their operations but perfectly correlated in their failure mode.

Technological monocultures are not merely a market structure problem. They are a systemic risk problem. They convert the failure of a single component into the failure of an entire ecosystem. And they are structurally incentivized by economies of scale, vendor consolidation, and the efficiency gains of standardization — the same forces that produce the efficiency–resilience tradeoff in other domains.

The defense against technological monoculture is not nostalgia for diversity but structural diversity: the deliberate preservation of independent implementations, the regulatory encouragement of interoperability standards over proprietary lock-in, and the recognition that efficiency in procurement can be fragility in operation.