# Red Hat introduces 'forever' support for RHEL Lifetime support for RHEL versions now available with annual contracts. - **Source:** [Latest news](https://brifing.si/source/77d15218-219f-472d-bf40-31b5646d2942) - **Published:** 2026-07-10 - **Topic:** [Product Management](https://brifing.si/c/product) - **Original article:** - **On Brifing:** https://brifing.si/s/bdac11eb-6858-4510-a030-27f6adcd605b ## Revolution in Support Duration Red Hat's RHEL Long-Life Add-On marks a new era for Linux distributions. Designed for sectors like finance and healthcare, this model allows indefinite use of specific RHEL versions. The only requirement: maintaining annual subscription payments. ## The Need for Eternal Support Companies' reluctance to frequently update server infrastructure drove this solution. It provides critical security patches for organizations using outdated systems like CentOS, offering flexibility in digital transformation timelines. ## Technical Specifications Requiring Premium subscription, RHEL Forever includes critical security patches and 24/7 support. Backported fixes maintain API/ABI compatibility, preventing large-scale migrations triggered by lifecycle deadlines. ## New Competitive Landscape Canonical and SUSE's 15-19 year support offerings highlight industry trends. Red Hat's move will likely pressure other Linux distributors to develop similar long-term support models. ## Pricing Uncertainty No standard pricing exists as costs are negotiated per customer. However, this add-on to Premium subscriptions is expected to require significant investment, especially for large enterprises. ## Industry Impact This shift transforms infrastructure management paradigms. Companies can now align product lifecycles with business strategies rather than vendor schedules. Particularly crucial for regulated industries needing operational flexibility. ## Sources covering this story - https://www.zdnet.com/article/red-hat-enterprise-linux-forever-support/ — --- _Summary written by Brifing from the original reporting. Copyright in the original article belongs to its publisher; read the full piece at the link above._