IBM and Red Hat: Six Years of Growth, Tensions and a New Open Source Era

The relationship between IBM and Red Hat is entering a new phase. The company that acquired Red Hat for around $34 billion in 2019 is integrating some of its corporate functions while, for now, keeping technical areas such as engineering separate. The move comes after six years in which Red Hat has become an important part of IBM’s software business, with OpenShift, Ansible and its artificial intelligence technologies increasingly integrated into IBM’s hybrid cloud strategy.

The key facts about IBM and Red Hat in 30 seconds

• IBM completed its acquisition of Red Hat in July 2019 for $34 billion.
• Red Hat grew from roughly $3.4 billion in revenue in 2019 to around $6.5 billion five years later.
• OpenShift grew from about $100 million in annual recurring revenue to $1.3 billion, according to IBM.
• From 2026, functions such as HR, finance, accounting and legal are being integrated into IBM.
• CentOS, access to RHEL source code and middleware integration have become important points of tension around the relationship.

The story has two sides that are worth keeping separate. From a business perspective, IBM has turned Red Hat into one of the most important components of its software and hybrid cloud strategy. From the perspective of parts of the open source community and some customers, several decisions following the acquisition have raised questions about how much autonomy Red Hat retains and how its open source model may evolve.

The financial figures help explain why Red Hat matters so much to IBM. In the third quarter of 2024, IBM said Red Hat had reached approximately $6.5 billion in revenue, almost twice the level at the time of the acquisition. During the same period, OpenShift had grown from roughly $100 million in annual recurring revenue to $1.3 billion.

From a $34 billion acquisition to the center of IBM’s hybrid cloud strategy

IBM announced the acquisition in October 2018 at an enterprise value of approximately $34 billion and completed it on July 9, 2019. The promise was specific: IBM said it would preserve Red Hat as a distinct unit, maintaining its brand, headquarters, practices and open development model.

The deal had a clear strategic rationale for IBM. The company wanted to strengthen its position in hybrid and multicloud environments at a time when businesses were increasingly combining their own data centers with multiple public cloud providers.

Red Hat brought exactly the technologies IBM needed: Red Hat Enterprise Linux (RHEL), OpenShift, container technologies and an established position in enterprise open source software. IBM argued that the combination would allow customers to run applications across their own data centers, private clouds and services from providers such as AWS, Microsoft Azure, Google Cloud and IBM Cloud.

Soon after the acquisition closed, IBM transformed more than 100 products in its portfolio so they could run on OpenShift and launched IBM Cloud Paks, aiming to bring enterprise applications to different cloud environments through a common platform.

That was one of the first signs of how IBM intended to use Red Hat. The acquisition was not simply about buying a Linux distribution. OpenShift was expected to become a layer through which IBM could sell software, services, automation and data tools.

OpenShift, Ansible and the rise of artificial intelligence

The results show that this strategy has had a commercial impact.

IBM said in 2024 that Red Hat had reached approximately $6.5 billion in revenue and that OpenShift had increased its annual recurring revenue more than tenfold since the acquisition. The company also highlighted the growth of Ansible and the arrival of RHEL AI and OpenShift AI.

The evolution is particularly relevant now that IBM is expanding its artificial intelligence strategy around infrastructure based on Red Hat technologies.

OpenShift AI has become one of the platforms used to develop, train and deploy artificial intelligence and machine learning applications across hybrid environments. IBM has also integrated the technology with products such as watsonx and Ansible Lightspeed.

In 2025, Red Hat expanded this direction further. OpenShift AI received new capabilities for AI models, while Red Hat Summit introduced the open source llm-d community, focused on distributed inference for generative AI models. Its founding collaborators include IBM Research, NVIDIA, Google Cloud and CoreWeave.

Ansible is also moving further into artificial intelligence. Ansible Automation Platform 2.6 includes Ansible Lightspeed with generative AI assistants and allows organizations to use different model providers through a BYOM, or Bring Your Own Model, approach. Red Hat lists compatibility with Red Hat AI models, OpenAI and Azure OpenAI, as well as 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 capabilities with IBM-managed infrastructure for artificial intelligence and virtualization workloads.

The direction is significant: Red Hat is no longer positioned only as a provider of Linux and container technologies. Its products are increasingly 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 was not the first move bringing the two companies’ structures closer together.

In February 2025, Red Hat announced that its middleware product and engineering teams would be integrated with IBM’s organization focused on data security, identity management and runtimes. The company presented the change as a way to unify its strategy for Java applications and integration technologies.

Months later came the broader announcement covering corporate functions. From early 2026, most employees in Red Hat’s general and administrative areas, including human resources, finance, accounting and legal, would move into IBM. Reporting on the change said that engineering and other technical areas would remain within Red Hat, although some employees expressed concerns about the consolidation of duplicate positions.

This matters because IBM’s original 2019 promise was very specific: the company said it would preserve Red Hat’s independence and neutrality.

The reorganization does not prove that Red Hat’s technical independence has disappeared. It does show that the original separation model has not remained completely unchanged six years after the acquisition.

CentOS opened the first major wound

The CentOS decision is probably the precedent that weighs most heavily on perceptions of the IBM-Red Hat relationship.

In December 2020, the project announced that development would shift from CentOS Linux toward CentOS Stream. CentOS Linux 8 reached end of life on December 31, 2021, while CentOS Linux 7 reached end of life on June 30, 2024. CentOS Stream took on the role of a public development branch positioned ahead of RHEL.

The distinction is important. CentOS Linux was a rebuild of RHEL positioned after the commercial distribution in the release cycle. CentOS Stream functions as a public development branch for RHEL.

For companies using CentOS Linux as a stable, free operating system, the change meant making migration decisions. The CentOS Project recommended moving to CentOS Stream, converting systems to RHEL or using another Enterprise Linux distribution.

The second major conflict came in 2023 over RHEL source code. Red Hat changed how the source code associated with RHEL was distributed. The company decided that CentOS Stream would serve as the public repository for source code related to RHEL, while customers and partners would continue to access RHEL sources through Red Hat’s portals according to their subscription agreements.

Red Hat argued that the source code remained available and that CentOS Stream enabled more direct collaboration with development. But the change affected how projects rebuilding RHEL obtained source material. AlmaLinux, Rocky Linux and other distributions had to adapt their processes.

Red Hat did not present the move as an abandonment of open source. The company explicitly said that CentOS Stream source code would remain publicly available.

The risk for enterprise users, therefore, is not that RHEL has stopped being open source. The issue is different: dependence on a single vendor’s decisions over release schedules, source access, commercial terms and the evolution of products that may support thousands of corporate systems.

What risks should IT departments watch?

The IBM reorganization does not automatically mean that companies should leave RHEL, OpenShift or other Red Hat technologies. The decision depends on existing contracts, required support levels, certifications, deployed applications and the cost of migration.

For infrastructure based on RHEL, moving to AlmaLinux or Rocky Linux is not simply a matter of changing the distribution name. An enterprise migration requires checking applications, drivers, management tools, vendor support and update processes.

Debian represents another model, with a community independent of a major enterprise software vendor. SUSE offers a commercial alternative for organizations that need professional support and enterprise tools.

The first risk is concentration. A company might use RHEL, OpenShift, Ansible, OpenShift AI, IBM Cloud services and IBM data tools. Each product may make sense independently, but together they increase dependence on a single commercial relationship.

The second is product lifecycle risk. CentOS demonstrated that a decision affecting a free platform can force thousands of organizations to migrate. Companies running systems for five, seven or ten years need visibility into how each component will evolve.

The third concerns source availability and the ability to build alternatives. The 2023 change did not eliminate access to CentOS Stream source code, but it changed the mechanism used to access RHEL sources. For some organizations, that difference can affect reconstruction, support and diversification strategies.

The fourth is organizational. The integration of corporate functions and specific product areas shows that IBM is willing to share structures with Red Hat when it sees a business reason to do so.

That does not mean Red Hat will disappear as a brand or that OpenShift will stop being a distinct product. Nor does it allow a conclusion that IBM will eventually integrate Red Hat’s engineering organization. Those decisions have not been announced.

The other side of the story is equally clear. IBM has invested in Red Hat, expanded OpenShift commercially and is using its technology as part 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 in revenue and grew 12% compared with 2023 under the company’s updated reporting structure.

Six years after the acquisition, Red Hat is not an asset that IBM has left on the sidelines. Quite the opposite: it has become increasingly connected to IBM’s software business and AI strategy.

The open question is how much further that integration can go without changing the characteristics that made Red Hat valuable in the first place: its community, its position in open source, its neutrality across different clouds and vendors, and its ability to provide an enterprise platform that is not tied to a single infrastructure provider.

Frequently asked questions

How much did IBM pay for Red Hat?

IBM announced the deal at an enterprise value of approximately $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 had reached approximately $6.5 billion in revenue, compared with around $3.4 billion in fiscal 2019.

What happened to CentOS?

CentOS Linux was progressively replaced by CentOS Stream as the public development platform for RHEL. CentOS Linux 7 reached end of life on June 30, 2024.

Is IBM completely absorbing Red Hat?

No. The 2026 reorganization primarily affects administrative functions such as human resources, finance, accounting and legal. Engineering and other technical areas remain within Red Hat, although specific product organizations have already been integrated with IBM.