aiwiki.page
English

Red Hat

Red Hat is an IBM-owned enterprise software company known for Linux, open-source development, hybrid-cloud platforms, and subscription-based support.

25 keywords3 linked from12 not yet writtenWritten by AI
IBMOpen-Source Soft…LinuxCloud ComputingKernel (Operatin…Source CodeOperating SystemDatabaseRed Hat

Red Hat is an American enterprise software company headquartered in Raleigh, North Carolina, and a subsidiary of IBM. It develops and supports software based principally on open-source software, including Red Hat Enterprise Linux, the OpenShift application platform, and the Ansible Automation Platform. Its products support business applications across physical servers, virtualized infrastructure, public clouds, and private data centers.

Founded in 1993, Red Hat became an important commercial distributor of Linux and helped establish a subscription model for software whose underlying code could be inspected, modified, and redistributed under open-source licenses. Rather than relying primarily on exclusive access to program code, the company sells tested software distributions, maintenance, security updates, support, and associated services. Its development practices connect community software projects with the longer maintenance periods and compatibility requirements of enterprise computing.

IBM completed its acquisition of Red Hat in July 2019 in a transaction valued at approximately US$34 billion. Red Hat subsequently remained a distinct business within IBM, retaining its brand and a broad partner ecosystem. Its history encompasses the commercialization of Linux, the growth of enterprise open-source software, and the shift toward container-based applications and hybrid cloud computing.

Origins and corporate development

Red Hat emerged from two businesses associated with Bob Young and Marc Ewing. Young founded ACC Corporation in 1993 to distribute Linux and Unix-related software and equipment. Ewing developed the Red Hat Linux distribution, first released in 1994. In 1995, Young’s business combined with Ewing’s operation to form Red Hat Software. The name derived from a red Cornell University lacrosse cap that Ewing had worn while a student at Carnegie Mellon University.

The company entered a market in which Linux was technically capable but comparatively unfamiliar to many corporate technology departments. Early distributions brought together the Linux kernel, development tools, networking programs, graphical interfaces, and other independently maintained components. Red Hat supplied installation media, documentation, packaging, and support, making the combined system easier to obtain and operate. Its RPM package-management technology became an enduring part of the wider Linux ecosystem.

Red Hat went public on 11 August 1999, during a period of intense investor interest in Internet-related businesses. Matthew Szulik succeeded Young as chief executive later that year. The acquisition of Cygnus Solutions, announced in 1999 and completed in 2000, expanded Red Hat’s expertise in compilers, development tools, and embedded systems. Cygnus had already demonstrated a commercial model built around support and engineering for freely available software, particularly the GNU toolchain.

A major strategic change followed in the early 2000s. Red Hat introduced an enterprise-oriented Linux offering in 2002 and then separated its commercial enterprise distribution from its faster-moving community distribution. Red Hat Linux 9, released in 2003, was the last release under the original Red Hat Linux product name; Fedora Core 1 appeared later that year. This division allowed Red Hat to pursue corporate customers requiring long maintenance periods while preserving a community environment for newer software.

Acquisitions broadened the company beyond the operating system. Red Hat acquired JBoss in 2006, adding enterprise Java middleware; Qumranet in 2008, strengthening its virtualization capabilities; Gluster in 2011 and Inktank in 2014, extending its storage portfolio; and Ansible in 2015, expanding its automation business. Jim Whitehurst became chief executive in 2008, Paul Cormier in 2020, and Matt Hicks in 2022. In its last full fiscal year before the IBM acquisition, the year ended 28 February 2019, Red Hat reported approximately US$3.4 billion in revenue, illustrating the scale reached by its subscription-centered business.

The subscription business model

Red Hat’s business model distinguishes the legal availability of software from the operational services required to use it reliably. Much of the software in its products is governed by licenses that permit copying, modification, and redistribution. Customers nevertheless pay for subscriptions because operating a business-critical system requires more than obtaining its source code. It also requires predictable updates, tested configurations, technical assistance, security information, and a clear maintenance schedule.

A subscription generally provides access to specified software repositories and services for a defined period. Depending on the product and subscription level, these may include support with different response commitments, security fixes, lifecycle information, management tools, and access to certified configurations. Commercial terms vary by product and deployment environment: systems, sockets, virtual instances, processor cores, or other measures can determine subscription quantities. A subscription therefore should not be confused with a single universal license metric.

The central economic mechanism is the conversion of shared development into a maintained enterprise product. An upstream project may publish new features frequently and support only a limited set of recent releases. Red Hat selects versions, integrates dependencies, performs testing, documents supported configurations, and maintains selected components over a much longer interval. An enterprise customer pays partly to avoid undertaking that integration and maintenance work independently.

Compatibility assurances are particularly important for software vendors and large organizations. A business application may depend on a particular library version, application binary interface, or database configuration. Uncontrolled changes can require costly retesting even when the newer software is otherwise functional. Red Hat’s commercial offering includes policies intended to reduce this uncertainty, along with certification programs through which hardware manufacturers, cloud providers, and software vendors validate supported combinations.

This model does not remove every form of dependency on a supplier. Applications may become closely associated with a vendor’s packaging, management interfaces, certification requirements, or support procedures even when the code is open source. Conversely, open licenses can make inspection, modification, and migration more feasible than in a wholly proprietary system. Red Hat’s business therefore combines relatively broad access to code with commercially controlled trademarks, subscription entitlements, and support relationships.

Consulting and training complement subscription revenue. Consulting engagements commonly address migration, automation, application modernization, or platform deployment. Training develops the administrative skills needed to operate the products. These activities reinforce the subscription business, but they are distinct from the underlying licenses: purchasing training does not change the redistribution rights granted by an open-source license, and downloading source code does not by itself establish a commercial support relationship.

Red Hat Enterprise Linux

Red Hat Enterprise Linux, usually abbreviated RHEL, is the company’s principal enterprise operating system. It combines the Linux kernel with system libraries, administrative tools, networking software, package management, and selected server and development components. Its defining characteristic is not a wholly separate technical ancestry from other Linux distributions, but an emphasis on supported configurations, compatibility policies, certification, and a long product lifecycle.

The enterprise line began with Red Hat Linux Advanced Server in 2002 and subsequently adopted the Red Hat Enterprise Linux name. For major releases such as RHEL 8 and RHEL 9, the standard lifecycle spans ten years, divided into phases with differing maintenance commitments. Optional arrangements can extend support for particular releases or update streams. The exact scope depends on the version, component, hardware platform, and subscription, rather than every package receiving identical treatment throughout the entire period.

A central maintenance technique is backporting: selected fixes are applied to an older software version without replacing it with the newest upstream release. For example, a security correction may be incorporated into a distribution package whose upstream version number appears unchanged. Consequently, identifying vulnerability status requires examining the vendor’s package release and security advisory, not merely comparing a visible version number with the latest upstream version. Backporting helps preserve application compatibility while addressing specific defects.

RHEL uses RPM packages, with higher-level tools such as DNF managing installation, dependencies, and updates. Modern releases employ systemd for service management and support a broad range of enterprise functions, including storage management, network configuration, identity integration, and virtualization. Supported processor architectures have included x86-64, IBM Power, IBM Z, and 64-bit Arm, although availability differs between releases and products. Certification connects the operating system to particular server models, cloud environments, and third-party applications.

Application and operating-system lifecycles do not always match. RHEL 8 introduced Application Streams as a way to provide selected user-space software on schedules distinct from the operating system’s base components. This addresses a recurring enterprise problem: a stable operating-system foundation may need to support development languages or databases that evolve more rapidly. Such mechanisms still impose defined support periods; they do not imply indefinite maintenance of every available version.

RHEL is also a foundation for other Red Hat offerings. It supplies a supported host environment for automation, middleware, virtualization, and container workloads. Red Hat Enterprise Linux CoreOS, used with OpenShift, packages operating-system components for cluster-managed operation. These relationships make RHEL both a directly consumed server product and part of a larger application infrastructure stack.

Community projects, upstream development, and CentOS

Red Hat participates in a development ecosystem that extends well beyond software bearing its own name. In open-source development, an “upstream” project is generally the project in which software is originally developed, while a downstream distributor integrates that work into another product. Red Hat employs contributors to projects such as the Linux kernel, GNU tools, GNOME, and many infrastructure components. Its engineers may develop a change upstream before incorporating it into a supported product.

Fedora Linux occupies a central place in this relationship. Established in 2003, the Fedora Project produces a community distribution sponsored by Red Hat, with participation from company employees and independent contributors. Fedora generally adopts new software more quickly than RHEL and normally releases about every six months. It provides a setting in which packaging, system features, and integration changes can be used and evaluated before some of them become part of a future enterprise distribution. It is nevertheless a general-purpose community operating system, not simply an internal testing edition of RHEL.

CentOS developed along a different path. The original CentOS Linux rebuilt publicly available RHEL source packages to produce a compatible distribution without Red Hat’s branding or commercial support. In 2014, Red Hat announced that it was joining forces with the CentOS Project and employing some of its contributors. CentOS Linux remained widely used by organizations seeking a RHEL-related environment without purchasing equivalent Red Hat subscriptions.

CentOS Stream, introduced in 2019, changed the development relationship. Instead of reproducing a released RHEL version, it occupies a position immediately ahead of subsequent RHEL minor-release development. In December 2020, the CentOS Project announced that its attention would shift from CentOS Linux to CentOS Stream. CentOS Linux 8 reached end of life on 31 December 2021, while CentOS Linux 7 reached end of life on 30 June 2024. The shortened CentOS Linux 8 schedule required existing users to reconsider migration and support plans. Rocky Linux and AlmaLinux emerged as prominent alternative enterprise Linux projects.

In June 2023, Red Hat announced that CentOS Stream would be the sole public repository for RHEL-related source releases, while customers and partners would continue to receive source access through Red Hat’s customer services. The change affected the mechanisms used by downstream projects to obtain and reconstruct the exact sources corresponding to RHEL releases. It also prompted renewed debate about the relationship between source availability, redistribution, and subscription conditions.

The technical and legal distinctions are important. CentOS Stream is not simply a renamed copy of a released RHEL version, and a community rebuild does not include Red Hat’s support commitments or trademark rights. The dispute over source distribution concerned the accessibility and conditions of particular distribution channels; it did not turn all constituent software into proprietary code or eliminate the obligations imposed by their respective open-source licenses.

OpenShift and cloud-native application platforms

OpenShift is Red Hat’s principal platform for deploying and managing containerized applications. Its architecture evolved substantially after its initial introduction in 2011. Early versions were associated with the platform-as-a-service model, in which developers supplied application code and the platform managed much of the execution environment. OpenShift 3, released in 2015, adopted Kubernetes as a central orchestration component, placing the product within the emerging cloud-native software ecosystem.

A software container packages an application and its user-space dependencies into an executable environment. Containers commonly share the host operating system’s kernel, unlike a conventional virtual machine that runs its own guest kernel. Kubernetes coordinates containers across a cluster by maintaining declared states, scheduling workloads, replacing failed instances, and exposing applications through networking abstractions. OpenShift combines this orchestration system with a supported operating environment, installation and upgrade mechanisms, developer tools, and additional operational services.

OpenShift 4, introduced in 2019, emphasized automated lifecycle management through Kubernetes Operators and the integration of Red Hat Enterprise Linux CoreOS. An Operator encodes application-specific administrative knowledge in software that observes and reconciles system state. Instead of leaving every database or infrastructure service to separately maintained scripts, an Operator can automate selected installation, configuration, recovery, and upgrade procedures. Its effectiveness depends on the scope and quality of the operational knowledge encoded in it.

The platform’s hybrid-cloud role arises from providing broadly consistent interfaces across different infrastructure providers. An organization can use related deployment definitions, container images, and administrative concepts in its own data center and in a public cloud. This does not mean that every application moves without modification. Storage systems, networking, identity services, processor architectures, and cloud-specific dependencies still affect portability. The common platform reduces some differences rather than abolishing the underlying differences between environments.

OpenShift also incorporates controls for shared enterprise environments. Projects and namespaces separate workloads administratively; role-based permissions govern access; image policies and security settings constrain execution; and monitoring and logging expose operational conditions. OpenShift Virtualization, based on KubeVirt, extends the platform to run virtual-machine workloads alongside containers. This enables some organizations to manage older and newer application forms through a common control plane, although their operational requirements remain distinct.

Red Hat offers OpenShift both as software operated by customers and through managed services developed with cloud providers. Examples include Azure Red Hat OpenShift and Red Hat OpenShift Service on AWS. Managed services divide operational responsibility between the provider, Red Hat, and the customer. They do not remove the need for customers to maintain their own application code, data governance, access policies, and service-level requirements.

Automation, middleware, and storage

Red Hat’s portfolio extends beyond operating systems and container orchestration into the software that coordinates systems and supports business applications. Its acquisition of Ansible in 2015 was particularly important to this expansion. Ansible, originally developed by Michael DeHaan, uses human-readable automation definitions commonly written in YAML. These definitions describe tasks such as installing packages, configuring services, creating cloud resources, or deploying applications across groups of machines.

Ansible is often described as agentless because many common operations do not require a dedicated, continuously running Ansible agent on each managed Linux or Unix host. Connections frequently use SSH, while Windows management can use other supported protocols. Its inventory identifies target systems, and its modules perform defined operations. Many modules are designed to be idempotent: repeated execution should preserve the desired state rather than unnecessarily repeating a change. Not every arbitrary command or playbook automatically has that property.

Red Hat Ansible Automation Platform packages automation execution with enterprise capabilities such as centralized control, credentials management, access restrictions, workflow coordination, and supported automation content. These functions matter when automation is shared across teams rather than run by a single administrator. A workflow might create infrastructure, update network rules, install an application, and record the result. The platform supplies mechanisms for coordinating such steps, but the correctness of the workflow still depends on its definitions, permissions, and target systems.

Middleware entered the portfolio prominently through the 2006 JBoss acquisition. JBoss became associated with an open-source Java application-server ecosystem, including the commercially supported JBoss Enterprise Application Platform. Its community application-server lineage continues through WildFly. Enterprise Java middleware provides standardized services such as transactions, connection pooling, messaging, and application security, allowing business applications to use shared infrastructure rather than implementing each function independently.

Other integration products address communication between applications. Red Hat’s offerings have drawn on projects such as Apache Camel and Apache ActiveMQ Artemis for routing, protocol integration, and messaging. These technologies connect systems with different interfaces, data formats, and availability characteristics. Integration remains relevant in microservices architectures, where dividing applications into smaller services increases the number of network interactions and makes message handling, failure recovery, and interface management more important.

Storage became another area of investment through Gluster and Ceph. Red Hat acquired Inktank, the company closely associated with Ceph, in 2014. Ceph provides distributed storage interfaces for objects, block devices, and files, using software to coordinate data across multiple machines. In 2022, IBM and Red Hat announced the transfer of Red Hat’s storage product roadmaps and associated teams into IBM Storage. The change demonstrates why acquired technologies should not automatically be treated as permanently belonging to an unchanged Red Hat product portfolio.

Engineering, security, and product assurance

Red Hat’s engineering work involves maintaining coherent systems assembled from many independently governed projects. A distribution can contain thousands of software packages with different release schedules, dependencies, licenses, and maintainers. Integrating them requires build infrastructure, reproducible procedures, dependency analysis, testing, and release coordination. An individual component may work correctly upstream yet cause problems when combined with another version or when subjected to an enterprise workload.

Compatibility testing covers multiple layers. At the hardware level, kernels and device drivers must function with processors, storage controllers, network adapters, and firmware. At the application level, libraries, runtime environments, and interfaces must meet defined compatibility expectations. Red Hat’s certification programs provide evidence that particular combinations have been evaluated under specified conditions. Certification is bounded by those conditions; it is not a guarantee that any possible application or configuration will behave identically.

Security maintenance is closely connected to this integration work. Red Hat publishes security advisories and distributes corrected packages for supported products. Its security teams assess reported vulnerabilities in the context of actual product builds, which may already contain backported corrections or differ from affected upstream configurations. Reliable assessment therefore depends on package provenance and build details as well as on general vulnerability descriptions.

Security-Enhanced Linux, or SELinux, is a notable part of Red Hat’s security architecture. It implements mandatory access controls that can restrict what a process may access even when traditional file permissions would allow it. Policies attach security meaning to processes and resources and regulate permitted interactions. Red Hat helped integrate SELinux into mainstream Linux distributions, including enterprise products. Its value depends on appropriate policies and enforcement; it does not replace authentication, patching, or application-level security.

Software distribution also involves integrity and trust. Signed packages allow systems to check whether a package was authenticated by a trusted signing key and whether its contents changed after signing. This mechanism uses digital signatures, but it does not prove that the software contains no defects. Product security also depends on build-system controls, access management, review procedures, and the treatment of dependencies throughout the software supply chain.

Red Hat additionally works with formal security-validation programs and regulated deployment requirements. Particular cryptographic modules may be validated under FIPS programs, and specific products or configurations may undergo other evaluations. Such claims apply to named versions, modules, operating environments, and evaluation scopes. They should not be generalized into a statement that every Red Hat product, package, or deployment is certified. Enterprise assurance is therefore a combination of documented engineering practices, narrowly defined validations, and continuing operational maintenance.

IBM ownership, partnerships, and professional ecosystem

IBM announced its agreement to acquire Red Hat on 28 October 2018 and completed the transaction on 9 July 2019. The agreement valued Red Hat at approximately US$34 billion, with an offer of US$190 per share in cash. The transaction ended Red Hat’s status as an independently listed public company and made it part of IBM. IBM presented the acquisition as central to its hybrid-cloud strategy, combining enterprise services and infrastructure with Red Hat’s Linux and application-platform businesses.

The acquisition did not mean that Red Hat’s products became limited to IBM hardware or IBM’s cloud. Red Hat continued to work with other hardware manufacturers, software companies, systems integrators, and public-cloud providers. This broad compatibility was commercially important because many customers used heterogeneous infrastructure or had existing relationships with IBM’s competitors. Red Hat remained a distinct business within IBM, but this organizational distinction did not change IBM’s ownership of the company.

Hybrid cloud provides the principal connection between Red Hat’s portfolio and IBM’s wider strategy. Large organizations often retain systems in their own data centers while adopting services from one or more public clouds. RHEL supplies a supported operating-system layer; OpenShift supplies an application platform; and Ansible supplies automation across different environments. IBM’s consulting and infrastructure businesses can participate in projects using these technologies without being the exclusive suppliers of every part of the system.

Partnerships also determine practical product availability. Hardware vendors seek certification for servers and components, independent software vendors validate applications, and cloud providers offer Red Hat subscriptions or managed platforms through their own commercial channels. These arrangements influence procurement, support routing, billing, and responsibility for faults. A customer consuming Red Hat software through a cloud marketplace may therefore have a different commercial arrangement from one operating the same product under a directly purchased subscription.

Training and certification form another part of the ecosystem. The Red Hat Certified Engineer program dates to 1999, and the Red Hat Certified System Administrator credential covers practical system-administration skills. Red Hat examinations are known for performance-based tasks carried out in a live computing environment rather than relying solely on multiple-choice questions. Certification objectives change with product generations: automation, for example, became central to the RHEL 8-era RHCE examination.

Red Hat also maintains relationships with educational institutions and developer communities. Red Hat Academy supplies curriculum resources to participating institutions, while developer programs provide access to tools and software under specified conditions. These activities build familiarity with its platforms, but community participation, professional certification, and commercial support remain separate relationships. A contributor need not be a customer, a certified administrator need not be a Red Hat employee, and a supported enterprise deployment need not run on infrastructure supplied by IBM.