A Free Rebuild Is Not a Closed Red Hat File

A Free Rebuild Is Not a Closed Red Hat File

You opened a Red Hat alternatives URL. Keep it. This page is the map of paid and free exits from Red Hat Enterprise Linux: AlmaLinux, Rocky Linux, Oracle Linux, SUSE Linux Enterprise Server, SUSE Multi-Linux Support, and CentOS Stream. How Red Hat counts a socket-pair stays at Understanding Red Hat’s licensing model. How you confirm a RHEL host is registered versus whether the account is covered stays at How to check if your Red Hat server is licensed.

That’s the problem.

A distro ISO is not a closed Red Hat file. CentOS Linux is gone. Stream is not the clone that died with it. AlmaLinux and Rocky do not make the same compatibility claim. Oracle Linux is free to download and still sells support. SUSE will support the OS you already run, or sell you SLES. Debian and Ubuntu are a different family. None of those sentences is “the subscription went away, so SAM risk went away.”

Do not invent a list price. Your number is the quote, the Oracle or SUSE support paper, or the Red Hat inventory you still hold.

CentOS Linux ended. Stream is not the replacement clone.

Red Hat (updated 1 July 2024): CentOS Linux 7 reached end of life on 30 June 2024. Updates and releases of CentOS Linux were discontinued between 2021 and 2024. The CentOS Project blog (8 December 2020): CentOS Linux 8, as a rebuild of RHEL 8, ended at the end of 2021. CentOS Linux 7 was produced through the remainder of the RHEL 7 life cycle.

The Red Hat blog (17 July 2024): “CentOS Linux no longer exists.” Any CentOS Linux support still sold in the market is a fork, wholly separate from the CentOS Project, CentOS Stream, and Red Hat.

CentOS.org: CentOS Stream is a “continuously delivered distro that tracks just ahead of Red Hat Enterprise Linux (RHEL).” The 2020 project post: Stream is the upstream (development) branch of RHEL. If you were using CentOS Linux 8 in production and were concerned Stream would not meet your needs, the project pointed you at Red Hat.

Red Hat’s Stream explainer (updated 6 February 2025): Fedora is further upstream. Stream sits in the middle. RHEL is the production-grade OS. Stream “provides a continuous stream of content, making CentOS Stream a preview of future Red Hat Enterprise Linux releases.” For important business applications and workloads, Red Hat’s recommended option is RHEL, not Stream. The same page: Stream is well-suited for development and proof-of-concept tasks that will ultimately run on RHEL.

Do not brief Stream as a drop-in production RHEL clone. Official wording does not say that.

If you stay on RHEL, Convert2RHEL and Red Hat’s Third Party Linux Migration offering are stay paths. They are not this URL. No-cost RHEL developer SKUs live on Understanding Red Hat’s licensing model.

AlmaLinux: binary compatible, not a 1:1 rebuild

AlmaLinux: “AlmaLinux OS is binary compatible with RHEL®.” It is community owned, forever-free, and positioned as filling the gap left by the CentOS Linux stable release.

That sentence is not “1:1 clone.” The 13 July 2023 board post: after Red Hat stopped providing the means for downstream clones to remain 1:1 binary copies, the AlmaLinux OS Foundation dropped the aim to be 1:1 with RHEL. The goal became binary/ABI compatibility: applications built to run on RHEL should run on AlmaLinux. The foundation was no longer held to bug-for-bug compatibility or to shipping an exact copy of RHEL source. The same post: AlmaLinux may accept fixes outside Red Hat’s cycle, which means some AlmaLinux bugs will not match RHEL, and some AlmaLinux fixes will land before RHEL.

The current homepage FAQ repeats that July 2023 shift. Do not paste a 2021 “1:1 binary clone” sentence onto a 2026 estate.

AlmaLinux FAQ: each minor ends when the next minor ships. Stable updates for AlmaLinux OS 8.x until 2029, and 9.x until 2032. The homepage, at fetch, lists 9.8 and 10.2 as current stables.

The bits are free. Commercial support exists as a separate buy through foundation sponsors named on the homepage (TuxCare, Cybertrust Japan). Do not invent those prices.

Rocky Linux: bug-for-bug, as Rocky currently states it

Rocky Linux: “an open-source enterprise operating system designed to be 100% bug-for-bug compatible with Red Hat Enterprise Linux®.” It “rebuilds sources directly from RHEL®” and advertises a 10-year support lifecycle at no cost for the distribution.

That is Rocky’s current wording. Quote it as a project claim, not as a Red Hat certification. The about page is the origin story (Gregory Kurtzer, after the December 2020 CentOS Stream shift). It does not rewrite the compatibility sentence on the homepage.

Trademarks still apply. Commercial support, if you buy it, is a partner contract. It is not “Rocky is free, so there is no paper.” Do not invent those prices.

Homepage releases at fetch: 10.2, 9.8, 8.10.

Oracle Linux: free to download, two kernels, paid support

Oracle: “Oracle Linux is free to download and distribute.” The datasheet: it has been completely free to download and use since 2006, and “Oracle Linux is 100% application binary compatible with Red Hat Enterprise Linux (RHEL).” User-space docs: that userspace compatibility is independent of which kernel is running. Existing userspace applications continue unmodified. Oracle’s words. Not a Red Hat mark.

Two kernels, from Oracle Linux 9 kernel docs and the datasheet:

  • Unbreakable Enterprise Kernel (UEK): default and enabled on x86_64. Based on a stable mainline branch, used on Oracle Engineered Systems and OCI. Some packages exist only on UEK (the docs name btrfs-tools, rds, and rdma related packages).
  • Red Hat Compatible Kernel (RHCK): “fully compatible with the Linux kernel that’s distributed in a corresponding Red Hat Enterprise Linux (RHEL) release.” Use RHCK when you need that kernel match.

UEK is not RHCK. Do not brief “Oracle Linux is RHEL” without saying which kernel the box boots.

Support is optional and paid. Oracle Linux Support: Basic, Premier, and Premier Plus, available for ten years from a major release, then Extended, then Sustaining. Premier adds Ksplice (zero-downtime patching). Premier Plus adds Oracle virtualization. The datasheet: you choose which systems are covered and at which level. Uncovered boxes are still Oracle Linux. They are not “no SAM object.”

Oracle’s ULN switch page (updated 5 January 2024): switching a RHEL server onto the Unbreakable Linux Network is documented as a simple switch. That page also says to hold a valid Oracle Linux Services Agreement before you register to ULN. Free yum updates and paid ULN support are not the same gate. Do not paste store prices. Do not invent SKUs.

Oracle, CIQ, and SUSE founded OpenELA to publish Enterprise Linux sources. That is a source project. It is not a license holiday.

SUSE: keep the OS, or change it

Two different SUSE products. Do not flatten them.

SUSE Multi-Linux Support (formerly SUSE Liberty Linux). Product page: “The no migration alternative for CentOS and RHEL enterprise support.” Keep the operating system. Get the patches from SUSE. FAQ: Liberty was the former name for support of a 100% binary-compatible version of RHEL, including API and ABI compatibility. It is now integrated into Multi-Linux Support. You do not have to migrate to SLES. Transition is: remove Red Hat patch repositories, point at SUSE channels.

SUSE Multi-Linux Support 9 docs (publication date 6 August 2026): with a subscription you update RHEL from SUSE repositories, with no requirement to migrate the OS. CentOS Stream is not supported. Lite and Basic only support CentOS Linux, so they are not the RHEL 9 row. Professional covers CentOS Linux and RHEL. Enterprise adds SLES. Some components still say “Liberty” during the name transition. Do not paste the dollar figures on the product page.

SUSE Linux Enterprise Server (SLES). SLES: a paid enterprise Linux of SUSE’s own. SLES 16 is current on that page. It is not a RHEL rebuild. Treat it as a different distribution with a commercial subscription, certifications, and add-ons. A SLES migration is an OS change, not a repo flip.

Debian and Ubuntu are not this family

The live page listed Debian and Ubuntu as free RHEL alternatives. They are enterprise Linux. They are not RHEL-compatible rebuilds. Different userspace, different package format, different certifications. If the requirement is “software certified for RHEL runs unmodified,” Debian and Ubuntu are the wrong row. Canonical sells commercial Ubuntu support. That is a different catalog. Do not steal it here.

Compatibility claims are not interchangeable

Distro or serviceWhat the vendor currently saysFree bits?Paid support?Drop-in production RHEL clone?
AlmaLinuxBinary/ABI compatible. Not 1:1 since July 2023.YesThird-party, named on the project siteNo. Compatible, with a documented shift off bug-for-bug.
Rocky Linux100% bug-for-bug compatible. Rebuilds RHEL sources.YesPartners exist. Distro is no-cost.Rocky’s claim. Not a Red Hat mark.
Oracle Linux100% application binary compatible. UEK or RHCK.Yes to download and distributeBasic, Premier, Premier PlusCompatible userspace. Kernel depends. ULN expects a support agreement.
SUSE Multi-Linux Support100% binary-compatible Liberty bits, or support the RHEL/CentOS you already runNo. It is a support service.Yes, by tierService on the existing OS, or Liberty bits. Stream is not supported.
SLESSUSE’s own enterprise LinuxTrial existsSubscriptionNo. Different distro.
CentOS StreamMidstream, tracks just ahead of RHEL. Preview of the next minor.YesNot a Red Hat production subscriptionNo. Official: not the production-grade RHEL recommendation.
CentOS LinuxEnded 30 June 2024N/AMarketplace forks only, separate from the projectDead.

Switching does not erase SAM risk

Do not brief “no Red Hat subscription, so no SAM risk.”

  1. Hosts you still run as RHEL still consume Red Hat units. Socket-pair versus VDC is the metric hub. Registration versus account coverage is the check. A Rocky guest next to a RHEL guest does not close the RHEL row.
  2. Trademarks. Red Hat’s trademark guidelines: you may distribute rebuilt code. You must remove Red Hat Marks, give the product its own name, and not mislead anyone into thinking they are getting Red Hat’s software, support, or QA. Rebuilders do that. Your procurement slides still cannot call the fleet “RHEL” if it is not.
  3. Support contracts you buy instead. Oracle Linux Support is a coverage decision on the systems you put on ULN. SUSE Multi-Linux Support is a per-system, per-tier service. Alma and Rocky third-party support is a contract. Those are SAM objects. Count them.
  4. ISV certifications follow the OS the vendor certified, not a hallway claim of compatibility. Oracle documents userspace compatibility independent of UEK versus RHCK. AlmaLinux documents that it is no longer an exact RHEL copy. Test the paper the ISV signed.
  5. OpenELA publishes sources. It is not a substitute for a support contract or a Red Hat entitlement.

Cost optimization and audit defense both still need the distro on the box, the leftover RHEL, and the support paper on the rebuilds. Software rationalization is the sprawl file if you now run four “RHEL-like” operating systems to do one job.

What to have this week

Do this before the next Red Hat renewal, Oracle Linux support quote, or “we already moved to Alma” briefing.

  1. Every Linux instance, by actual distro. RHEL, AlmaLinux, Rocky, Oracle Linux (UEK or RHCK), SLES, Stream, leftover CentOS Linux. Infrastructure Mapper is the topology file.
  2. What is still RHEL. Those hosts still need a Red Hat position. Point the metric at Understanding Red Hat’s licensing model and the host check at How to check if your Red Hat server is licensed. Do not mix rebuilds into the RHEL true-up as if they canceled it.
  3. What support paper sits on the rebuilds. Oracle Basic / Premier / Plus, SUSE Multi-Linux Support tier, Alma or Rocky third-party, or none. LCM is the renewal file. Renewal optimization is the date file.
  4. What you told ISVs and auditors the OS is. Compatible is not certified. Certified is the letter.
  5. A cost-optimal cover for the RHEL remainder, and a list of unmanaged distributions. Red Hat Deployment Manager maps RHEL deployments to SKUs and surfaces unmanaged distributions.

Can a non-specialist brief the CIO in fifteen minutes from the pack you have today? If the answer is “we installed Rocky so we are off Red Hat” while Hybrid Cloud Console still shows registered RHEL, or “Oracle Linux is free so there is no support decision,” you do not have a position.

Picture your procurement director, sixty days out. Finance has this URL bookmarked. A free ISO is not a closed file. The number is how many hosts are still RHEL, which rebuild they actually run, and which support contract, if any, covers the rest.

The decision layer, not another distro bake-off

You already have Satellite, a CMDB, and a spreadsheet that says “moved to Alma.” The gap is not another comparison table. The gap is turning the estate into a file: distro on the box, kernel if it is Oracle, remaining RHEL metric, support paper on the rebuilds. LICENSEWARE sits on the inventory and ITSM tools you already run. It is not a rip-and-replace SAM suite. It is a decision layer: what matters, why it matters now, what should happen next. RDM is the RHEL file.

If you are heading into a Red Hat renewal or an alternatives steering group and your current tools still need three weeks to separate leftover RHEL from Alma, Rocky, Oracle Linux, and Stream, book an Audit Readiness Review. You can also start on the free plan and run the analysis on your own data.

Do not let a vendor frame this as “download the clone and the subscription problem ends.” Do not let your own side frame Stream as the CentOS you used to run. The right question is: which distro is on the host, is any of it still RHEL, and which support contract covers the rest. That is a data question, not a sales question.

The vendor will walk in with a number. The only question is whether you have yours first: current, defensible, and tied to the contract in front of you.

Sources

Posted in ,

Alex Cojocaru

Alex has been active in the software world since he started his career as an Analyst in 2011. He had various roles in software asset management, data analytics, and software development. He walked in the shoes of an analyst, auditor, advisor, and software engineer, being involved in building SAM tools, amongst other data-focused projects. In 2020, Alex co-founded LICENSEWARE and is currently leading the company as CEO.