IBM, antitrust, and closed platforms
What mid-century computing dominance still illustrates about lock-in
For much of the mid-20th century IBM was not merely a large computer company; it was the default computing vendor for many businesses and governments. Punch cards, mainframes, and bundled services created a deep dependency that later antitrust scrutiny tried to unwind. The episode is still a useful reference when talking about platform lock-in.
How dominance looked
IBM's position rested on more than individual products:
- Continuous technical lead in systems that became industry reference points
- Hardware, software, and services sold as a tightly coupled stack
- Switching costs that made leaving the ecosystem expensive
That combination looks familiar in later platform businesses, even when the product categories differ.
The antitrust case
In 1969 the U.S. government filed a major antitrust suit against IBM. Allegations included monopolization of the computer market and practices that limited competition. The case produced a large documentary record. It was withdrawn in 1982 as "without merit," but the years of scrutiny coincided with a more open field for competitors such as Microsoft and Apple.
Historians caution against treating IBM as a single monolith. James W. Cortada has described it as a set of internal factions rather than one uniform institution — which makes the monopoly story more complicated than a simple villain narrative.
Why the history still matters
Modern large platforms also compete through ecosystems: proprietary standards, bundled services, and network effects that raise the cost of exit. IBM's case does not map one-to-one onto any current company, but it shows how technical leadership plus integration can become structural power.
Open source and open standards are one recurring counterweight: development that is inspectable, portable across vendors, and harder for a single firm to fully enclose. They are not a complete answer to every market-power problem, but they change the default assumptions about who can read, fix, and redistribute the stack.