CompanyGraph
Cisco Systems, Inc.
CSCO · United States
Runs one operating system — IOS — across campus switches, service-provider routers, and data-center networks worldwide.
Cisco builds and sells the networking hardware — campus switches, service-provider routers, and data-center switches — that carries traffic across enterprise and carrier networks, and every piece of that hardware runs a single operating system called IOS. Because IOS uses the same command syntax and policy logic across all three product tiers, a network administrator learns one system rather than three, and a configuration rule written once applies everywhere. That shared language is also what makes leaving expensive: IOS syntax cannot be copied to a competitor's platform, so replacing even one tier means rewriting every configuration file from scratch and putting administrators through months of retraining on a different vendor's commands, which is why customers tend to renew multi-year support contracts long past the point where buying new hardware would otherwise make financial sense. The same unified codebase that creates that stickiness is also the company's main vulnerability — because Catalyst switches, ASR routers, and Nexus fabric all share code paths, a single security flaw discovered anywhere in IOS reaches the entire installed base at once, across campus, core, and data center simultaneously.
How does this company make money?
The company earns money when it sells Catalyst, ASR, or Nexus hardware, and that hardware sale comes bundled with a software license. It then collects annual subscription fees tied to each device's serial number for ongoing software support, meaning revenue continues for as long as the hardware stays in use. It also charges for professional services when customers need help designing or building out their networks.
What makes this company hard to replace?
Network administrators trained on IOS commands must go through months of retraining to use a different vendor's system, because each vendor's command language is different. Every configuration file written in IOS syntax has to be rewritten from scratch on a new platform — it cannot simply be copied over. On top of that, multi-year enterprise support contracts tied to specific hardware serial numbers lock customers into a financial commitment that makes switching expensive even before the technical work begins.
What limits this company?
The networking chips inside Catalyst, ASR, and Nexus hardware are custom-designed, and each design takes 18 to 24 months to go from concept to a finished chip. Engineers must guess which protocol standards — like BGP extensions or 400G and 800G switching — will be finalized by IEEE or IETF before the chip is locked in. If they guess wrong, the mistake cannot be fixed until the next chip generation, which means there is always a fixed gap between what customers need and what can actually ship.
What does this company depend on?
The company cannot operate without TSMC and Broadcom to manufacture its custom networking chips, or Marvell for switching chips. It also depends on IEEE 802.11 and other standards bodies to set the wireless and networking protocols that IOS must support. Enterprise IT procurement cycles and carrier-grade reliability certification processes determine when and whether large customers can buy at all.
Who depends on this company?
Enterprise IT departments running Catalyst switch infrastructure would face network segmentation failures if the company stopped, requiring complete hardware replacement. Service providers using ASR routers for MPLS networks would lose traffic routing capabilities and be forced into expensive carrier-grade equipment swaps. Hyperscalers like Amazon and Microsoft would experience data-center fabric disruptions that would require full architectural redesigns.
How does this company scale?
Software licenses and annual support contracts can be extended to more customers at almost no additional cost, because the same IOS code already exists. What does not scale easily is the custom ASIC development at the heart of every hardware product — spreading that work across multiple silicon teams would break the tight timing and architectural consistency that makes the chips work correctly together.
What external forces can significantly affect this company?
U.S.-China technology export restrictions are splitting the global networking equipment market in two, forcing duplicate research and development spending for separate product lines. The rapid growth of AI workloads is pushing hyperscalers to demand 400G and 800G switching capacity much faster than normal enterprise hardware refresh cycles would deliver it. Federal cybersecurity rules are requiring hardware-level security features in any networking equipment sold to government customers.
Where is this company structurally vulnerable?
Because Catalyst, ASR, and Nexus all share the same IOS code, a single security flaw or protocol bug found anywhere in that code hits campus switches, service-provider routers, and data-center fabric all at once. The same architectural unity that makes it painful for customers to leave also makes it impossible to contain a serious software problem to just one product line.