IBM bought Red Hat's route into the hybrid cloud
The $34 billion acquisition placed enterprise support, Kubernetes and cloud neutrality at the centre of IBM's cloud strategy. For software founders, the value lay in the operating work around open source.
IBM completed its acquisition of Red Hat on 9 July 2019, paying $190 per share in cash for an approximate equity value of $34 billion. The transaction joined a large enterprise technology supplier with a business built around making open source software usable in demanding production environments. Linux and Kubernetes were central to the pitch, alongside something less visible: customers' willingness to pay for reliable operations around software they could otherwise obtain through open source projects.
The agreement had been announced the previous October. Closing made the strategic commitment concrete, but did not establish that the integration would succeed. IBM promised to preserve Red Hat's independence and neutrality while extending its reach. Those promises mattered because Red Hat sold across competing clouds. The asset IBM wanted to expand depended partly on customers believing that it would continue to serve environments outside IBM's own infrastructure.
The customer was already running several environments
The closing announcement described a platform for deploying, running and managing applications on premises, in private clouds and across multiple public clouds. That is a concrete purchasing situation: an established company may need to modernise an application without moving its database, or support a public cloud service alongside systems that remain inside its own facilities. A common software foundation can make these choices easier to manage without making the environments identical.
For an application startup, this expands the possible customer base and the support obligation together. A product that works inside the founder's preferred cloud may need different identity connections, storage assumptions and installation procedures for a bank's infrastructure. The commercial question becomes whether a reusable deployment approach can serve those accounts profitably. Large enterprise demand has little value if every contract requires a separate branch of the product and a permanent team of specialists.
OpenShift showed where the operating work sat
Red Hat's introduction of OpenShift 4 in May helps explain what IBM was buying. The announcement emphasised automated software updates, lifecycle management, installation and Kubernetes Operators. Operators encode procedures for running an application, including maintenance, scaling and failover. These were attempts to turn recurring operational knowledge into software, making a production platform more than a collection of downloadable components.
Scroll to view all columns
| Comparison | Platform capability | Application vendor's responsibility |
|---|---|---|
| Deployment | A Kubernetes foundation and installation automation | Package the application and validate its dependencies in each supported environment |
| Lifecycle | Operators and platform update mechanisms | Define safe upgrades, data migrations, backup and recovery for the application |
| Enterprise support | A supported infrastructure platform and partner ecosystem | Own the customer outcome and resolve failures across product boundaries |
Capabilities described in Red Hat's OpenShift 4 announcement. Application vendors still needed to manage deployment, lifecycle and support for their own products.
Source2
The announcement also distinguished capabilities from their release schedules. OpenShift 4 was expected to become available within the next month; support across additional environments was described as arriving in coming months, and several features remained in preview or development. Those distinctions matter to buyers building a deployment timetable. An acquisition thesis may encompass a broad platform, while an application vendor must still verify the versions, providers and features that its next customer can actually use.
Neutrality was part of the commercial product
At closing, IBM said Red Hat would remain a distinct unit, retain its headquarters, brands and practices, and continue partnerships with Amazon Web Services, Microsoft Azure, Google Cloud and Alibaba. These were commitments by the acquirer, rather than guarantees of every future commercial decision. Their prominence showed how much the deal depended on preserving relationships with companies that also competed with IBM.
For a young infrastructure supplier, neutrality can be a reason to buy. Customers may value a security, data or management product because it works across several providers. An investor should therefore examine which relationships produce that value: access to interfaces, support agreements, certification and the ability to diagnose problems across environments. A future acquisition can strengthen distribution while changing how partners view the supplier. The company needs a business that remains useful through that change.
The ecosystem offered distribution and competition
OpenShift 4's Certified Operators programme created a route for partner applications to sit inside the platform's operating model. A database or integration company could make installation and maintenance easier for an existing OpenShift customer. This gives a small vendor a more precise proposition than merely saying that it supports containers: the customer can assess how the application behaves when it is installed, expanded, upgraded or recovered.
The same platform can absorb capabilities that once supported a standalone company. Founders must distinguish a useful integration from dependence on a feature gap that the platform is likely to close. Specialist operational knowledge, a differentiated data service or a difficult customer workflow may provide a stronger position than a thin administrative interface. Certification and a marketplace listing can open access to buyers. Whether partner salespeople generate profitable contracts still needs to be demonstrated.
A large exit did not set a universal valuation
Red Hat's scale and strategic position made this a poor template for valuing every open source startup. The closing release reported fiscal 2019 revenue of $3.4 billion and pointed to a broad subscription business. IBM also brought its own distribution and strategic objectives to the price. Applying the headline transaction value to a young project's downloads or developer attention would skip the essential step of identifying what customers actually paid to receive.
Commercial value depended on taking responsibility for customers' use of the software. Who maintains the supported version, handles an urgent failure and makes upgrades safe for an enterprise customer? How much of that work can be repeated through software rather than delivered afresh by consultants? IBM's acquisition placed a substantial value on an established answer to those questions. For founders, building that answer remained a product and operating challenge, even with open source distribution.
Investment implications
- Enterprise open source earns a budget when distribution, maintenance and accountability solve expensive operational problems.
- A platform partnership can broaden a startup's reach while placing more of its product boundary under a larger supplier's control.
Sources
- IBM Closes Landmark Acquisition of Red Hat for $34 Billion; Defines Open, Hybrid Cloud Future (opens in a new tab)
IBM and Red Hat
- Red Hat Redefines Enterprise Kubernetes Through Full Stack Automation with Red Hat OpenShift 4 (opens in a new tab)
Red Hat
- IBM to Acquire Red Hat, Completely Changing the Cloud Landscape and Becoming World's #1 Hybrid Cloud Provider (opens in a new tab)
IBM and Red Hat
Published
