The relationship between IBM and Red Hat is entering a new phase. The company that bought Red Hat for about $34 billion in 2019 is integrating part of its corporate functions while keeping technical areas such as engineering separate for now. The move comes after six years in which Red Hat has become an important piece of IBM’s software business, with OpenShift, Ansible, and its artificial intelligence technologies increasingly woven into IBM’s hybrid cloud strategy.
IBM and Red Hat in 30 seconds
- IBM closed the Red Hat acquisition in July 2019 for $34 billion.
- Red Hat’s revenue went from about $3.4 billion in 2019 to roughly $6.5 billion five years later.
- OpenShift’s annual recurring revenue grew from about $100 million to $1.3 billion, according to IBM.
- Starting in 2026, functions such as HR, finance, accounting, and legal are being folded into IBM.
- CentOS, access to RHEL’s source code, and the integration of middleware show where the friction in this relationship lies.
There are two sides to this story worth keeping separate. From a business standpoint, IBM has managed to turn Red Hat into one of the most important pieces of its software and hybrid cloud strategy. From the standpoint of the community and some customers, several decisions since the acquisition have raised questions about how much autonomy Red Hat still has and how its open source model can evolve from here.
The financial numbers help explain why Red Hat matters so much to IBM. In the third quarter of 2024, IBM said Red Hat’s revenue had reached roughly $6.5 billion, almost double what it was when the acquisition was announced. Over the same period, OpenShift’s annual recurring revenue had grown from about $100 million to $1.3 billion.
From a $34 billion purchase to the centerpiece of hybrid cloud
IBM announced the acquisition in October 2018 for an enterprise value of roughly $34 billion and completed it on July 9, 2019. The promise was to keep Red Hat as a distinct unit, preserving its brand, headquarters, practices, and open development model.
The deal made clear strategic sense for IBM. The company was looking to strengthen its position in hybrid cloud and multicloud at a time when businesses were starting to combine their own data centers with different public cloud providers.
Red Hat brought exactly the pieces IBM needed: Red Hat Enterprise Linux (RHEL), OpenShift, container technologies, and an established position in enterprise open source software. IBM argued at the time that the combination would let customers run applications across their own data centers, private clouds, and providers such as AWS, Microsoft Azure, Google Cloud, or IBM Cloud.
Shortly after the deal closed, IBM reworked more than 100 products in its catalog to run on OpenShift and launched IBM Cloud Paks, aimed at bringing enterprise applications to different cloud environments on a common foundation.
That move was one of the first signs of how IBM intended to use Red Hat. The deal was never framed as simply buying a Linux distribution. OpenShift was meant to become the layer on which IBM could sell software, services, automation, and data tools.
OpenShift, Ansible, and the arrival of artificial intelligence
The results show that strategy has paid off commercially.
IBM reported in 2024 that Red Hat had reached roughly $6.5 billion in revenue and that OpenShift’s annual recurring revenue had grown more than tenfold since the acquisition. The company also highlighted Ansible’s growth and the arrival of RHEL AI and OpenShift AI.
That progress matters even more now that IBM is shifting part of its artificial intelligence strategy toward enterprise infrastructure built on Red Hat.
OpenShift AI has become one of the pieces used to develop, train, and deploy artificial intelligence and machine learning applications across hybrid environments. IBM has also integrated it with products such as watsonx and Ansible Lightspeed.
In 2025, Red Hat pushed even further in this direction. OpenShift AI gained new AI model capabilities, and Red Hat Summit saw the launch of the llm-d open source community, focused on distributed inference for generative models. Its founding contributors include IBM Research, NVIDIA, Google Cloud, and CoreWeave.
Ansible is also evolving toward artificial intelligence. Version 2.6 adds Ansible Lightspeed with generative assistants and supports a Bring Your Own Model (BYOM) approach across different model providers. Red Hat says it supports models from Red Hat AI, OpenAI, and Azure OpenAI, with planned integrations with IBM watsonx.ai and Google Gemini.
In May 2026, IBM took another step by offering Red Hat AI Inference and Red Hat OpenShift Virtualization as managed services on IBM Cloud. The stated goal is to combine Red Hat’s capabilities with infrastructure managed by IBM for AI and virtualization workloads.
The direction is telling: Red Hat is no longer just a Linux and container vendor. Its technologies are part of the layer IBM uses to build an enterprise offering around AI, automation, virtualization, and hybrid cloud.
The first major structural change came before the 2026 reorganization
The administrative integration announced in September 2025 wasn’t the first move to bring the two companies’ structures closer together.
In February 2025, Red Hat announced that its middleware product and engineering teams would be folded into IBM’s organization for data security, identity management, and runtimes. The company presented the change as a way to unify its strategy for Java applications and integration solutions.
Months later came the broader announcement about corporate functions. Starting in early 2026, most workers in Red Hat’s general and administrative areas, including human resources, finance, accounting, and legal, would move to IBM. According to The Register, engineering and other technical areas would remain at Red Hat, though the reporting also noted that some employees were concerned about the consolidation of duplicate roles.
This point matters because the original 2019 promise was very specific: IBM said it would preserve Red Hat’s independence and neutrality.
The reorganization doesn’t prove that technical independence has disappeared. It does show that the original separation model hasn’t remained intact six years on.
CentOS opened the first big wound
The CentOS episode is probably the precedent that weighs most heavily on the community’s perception.
In December 2020, the project announced the shift from CentOS Linux to CentOS Stream. CentOS Linux 8 reached end of life on December 31, 2021, and CentOS Linux 7 reached end of life on June 30, 2024. CentOS Stream took over as the public development branch sitting ahead of RHEL in the release cycle.
The difference matters. CentOS Linux was a rebuild of RHEL positioned downstream of it in the release cycle. CentOS Stream works as RHEL’s public upstream development branch.
For businesses using CentOS Linux as a stable, free platform, the change meant having to make migration decisions. The CentOS project itself recommended at the time moving to CentOS Stream, converting systems to RHEL, or switching to another distribution in the Enterprise Linux ecosystem.
The second conflict came in 2023 over RHEL’s source code. Red Hat decided that CentOS Stream would be the public repository for RHEL-related source code, and that customers and partners would continue accessing RHEL sources through their portals, under their subscription agreements.
Red Hat argued that the code remained available and that CentOS Stream enabled more direct collaboration with development. But the change affected how projects that rebuilt RHEL obtained the sources. AlmaLinux, Rocky Linux, and other distributions had to adapt their processes.
Red Hat didn’t present that move as abandoning open source. In fact, the company explicitly said CentOS Stream’s code would remain publicly available.
The threat to enterprise users, then, isn’t that RHEL has stopped being open source. The risk lies elsewhere: dependence on a single vendor’s decisions about timelines, source access, commercial terms, and the evolution of products that may underpin thousands of corporate systems.
What risks IT departments should watch
None of this means companies need to abandon Red Hat, but it does change how an infrastructure built on its technologies should be evaluated.
The first risk is concentration. A company might use RHEL, OpenShift, Ansible, OpenShift AI, IBM Cloud services, and IBM’s data and AI tools. Each product can make sense on its own, but together they increase dependence on a single commercial relationship.
The second is product-cycle change. CentOS showed that a decision about a free platform can force thousands of organizations to migrate. Companies running systems for five, seven, or ten years need advance visibility into how each component will evolve.
The third relates to code availability and the ability to build alternatives. The 2023 change didn’t eliminate access to CentOS Stream’s code, but it did change the mechanism used to access RHEL’s sources. For some organizations, that difference can affect their rebuild, support, and diversification strategies.
And the fourth is organizational. The integration of administrative functions and some product areas shows that IBM is willing to share structures with Red Hat when it sees a business reason to do so.
That doesn’t mean Red Hat will disappear as a brand, or that OpenShift will stop being an independent product. Nor does it mean IBM will merge their engineering teams in the future. But it does justify infrastructure leaders keeping a close eye on organizational and product changes.
The other side of the story is just as clear. IBM has invested in Red Hat, multiplied OpenShift’s commercial reach, and is using its technology as one of the foundations of its hybrid cloud and artificial intelligence strategy. In 2024, IBM’s Hybrid Cloud business, which includes RHEL, OpenShift, Ansible, and Red Hat AI, generated $6.5 billion and grew 12% versus 2023 under the company’s new reporting structure.
Six years after the purchase, Red Hat doesn’t look like an acquisition IBM has left on the sidelines. The opposite is true: it has become an increasingly connected part of IBM’s software business and AI strategy.
The open question is how much of that integration can happen without changing the traits that made Red Hat valuable in the first place: its community, its standing within open source, its neutrality across different clouds and vendors, and its ability to offer an enterprise platform independent of any single manufacturer.
Frequently asked questions
How much did IBM pay for Red Hat?
IBM announced the deal at an enterprise value of roughly $34 billion and completed the acquisition on July 9, 2019.
How much has Red Hat grown since the acquisition?
IBM said in 2024 that Red Hat’s revenue had reached roughly $6.5 billion, up from about $3.4 billion in fiscal year 2019.
What happened to CentOS?
CentOS Linux was progressively replaced by CentOS Stream as RHEL’s public development platform. CentOS Linux 7 reached end of life on June 30, 2024.
Is IBM fully absorbing Red Hat?
No. The reorganization announced for 2026 mainly affects administrative functions such as human resources, finance, accounting, and legal. Published reporting indicates engineering and other technical areas remain at Red Hat, although some concrete integrations have already happened, such as part of middleware joining an IBM organization in 2025.
