Every serious infrastructure investment goes into redundant hardware, distributed systems, and multi-region failover. Almost none goes into the one dependency that sits above all of it — the small number of engineers whose departure, unavailability, or burnout makes the environment unrecoverable.
The infrastructure bus factor is the organizational single point of failure that no architecture review catches. It doesn't appear in the system diagram. It doesn't show up on a monitoring dashboard. It lives in a person. In most organizations, the real infrastructure control plane is not Terraform, not Kubernetes, not vCenter. It is the senior engineer carrying operational context in their head — the undocumented governance layer that fills every gap the formal systems leave.
That is not a staffing problem. It is an architectural one.
The Bus Factor No One Models
The infrastructure bus factor is the number of engineers who would need to be simultaneously unavailable before the environment becomes unrecoverable. The question isn't how many people are on the team. It's how many of them carry operational authority artifacts that exist nowhere else.
