RHEL 10: What’s New for Linux Servers

Red Hat Enterprise Linux sets the pace for the whole enterprise Linux world. Free rebuilds such as AlmaLinux and Rocky Linux inherit its code, cloud providers ship it as ready-made templates, and thousands of commercial applications certify against it. When a new major version lands, the effects ripple far beyond the companies that actually pay for a subscription.

RHEL 10 arrived on May 20, 2025 under the codename Coughlan. It runs Linux kernel 6.12 and carries support commitments that stretch to 2035. By the summer of 2026 the platform has already collected two minor updates, 10.1 and 10.2, so the release can be judged on its track record instead of launch-day promises.

This guide walks through the headline features, the additions delivered by the minor releases, the free ways to get hands-on with the system, and the mistakes that most often derail migrations. No deep Linux background is required: every technical concept comes with a plain-language explanation.

Why RHEL 10 matters beyond Red Hat customers

Red Hat Enterprise Linux belongs to the enterprise distribution category, and predictability is its core promise. Kernel and library versions are frozen at launch, after which the system receives a decade of security patches and carefully selected improvements. New capabilities reach the old kernel through backports, so software that once started on a server keeps running for years without surprises.

The lifecycle follows a familiar shape: full support with fresh features lasts until roughly May 2030, then a maintenance phase with critical fixes continues until May 2035. Extended programs can keep individual minor releases alive even longer. For infrastructure teams this translates into a planning horizon measured in decades rather than quarters.

The release rhythm is equally steady. Since the eighth version Red Hat has shipped a major release every three years: RHEL 8 in 2019, RHEL 9 in 2022, RHEL 10 in 2025, with minor updates landing every six months. Migrations can be scheduled years ahead, calmly and without fire drills.

The impact reaches well past paying customers. RHEL sources flow through CentOS Stream into community rebuilds. AlmaLinux 10 shipped on May 27, 2025, a single week after the original, and Rocky Linux 10 followed in mid-June. Both are binary compatible with RHEL 10 and mirror its package set, while independent Phoronix benchmarks measured identical performance across all three systems on the same hardware.

Red Hat frames the tenth version around three priorities: hardened security, container and cloud focus, and automation powered by artificial intelligence. The next sections show what each of those means in practice.

The four changes that define RHEL 10

The release notes list dozens of modifications. Four of them shape day-to-day server work more than everything else combined.

Lightspeed brings AI assistance into the terminal

Lightspeed is the most talked-about addition. The assistant lives directly in the shell: an administrator describes a problem in ordinary words, something like “why does the SSH service refuse to start”, and receives step-by-step guidance. The answers draw on the knowledge base that Red Hat support engineers have accumulated over decades of tickets.

Version 10.1 taught the assistant to operate in fully disconnected, air-gapped environments, which matters for banks, defense contractors and industrial sites, and raised the context limit from 2 KB to 32 KB, enough to feed it lengthy logs. One caveat applies: the feature is tied to a Red Hat subscription and its backend services, so the free rebuilds ship without it.

Post-quantum cryptography lands ahead of the threat

RHEL 10 became the first enterprise distribution with FIPS-compliant support for post-quantum encryption. The idea is simpler than the name suggests. A technique known as “harvest now, decrypt later” lets an attacker capture encrypted traffic today and store it until quantum computers grow strong enough to break classical algorithms. Records with a long shelf life, whether medical histories, financial archives or government files, could be exposed a decade from now.

Post-quantum algorithms are designed to survive that scenario. They debuted in 10.0 as a technology preview, then 10.1 switched them on across the system-wide cryptographic policies by default, and OpenSSL 3.5 added the NIST-standardized ML-KEM and ML-DSA algorithms.

Image mode treats the operating system as a container

The bootc technology rethinks how servers are managed. A classic OS gets installed once and then tweaked for years, which is why two formally identical machines slowly drift apart in configuration. Image mode proposes building the system as a container image instead: describe the contents once, roll it out to the entire fleet, ship updates by swapping the image, and roll back by returning to the previous one.

A household analogy helps: rather than renovating every apartment separately, the developer delivers buildings with identical factory finishing. The concept keeps evolving. Version 10.1 introduced soft reboots that refresh the user space without restarting the kernel, and 10.2 learned to pre-stage updates across a fleet so they can be applied during a convenient maintenance window.

The x86-64-v3 requirement retires older hardware

This is the change that hurts. RHEL 10 demands a processor with the x86-64-v3 instruction set, which for Intel means Haswell-generation chips and newer, roughly everything manufactured from 2013 onward. On an older server the system simply refuses to boot. The decision unlocks better performance on current silicon, yet owners of aging racks now face a choice between replacing hardware and finding a workaround. One workaround exists: AlmaLinux, alone among the rebuilds, publishes a separate build of version 10 for x86-64-v2 that runs on processors from around 2008.

Smaller but notable shifts round out the picture: the installer moved from X.Org to Wayland, RDP replaced VNC for graphical remote access, PipeWire took over audio duties from PulseAudio, and network interfaces now carry predictable names such as ens3, with the legacy net.ifnames=0 parameter removed for good.

What the 10.1 and 10.2 updates delivered

RHEL follows a strict schedule: minor versions appear every six months and bring genuine functionality along with the fixes.

Version 10.1 went live on November 12, 2025, and its central theme was hardware acceleration for AI workloads. The NVIDIA open kernel driver moved into the official extensions repository, joined by the CUDA user-space components and the AMD ROCm stack. GPU driver installation used to be a project of its own; now it comes down to standard package manager commands. The release also introduced reproducible container builds, where images produced from identical inputs match down to the metadata, and made ACME-based automatic TLS certificate management generally available, taking the error-prone manual renewal of certificates off the operations checklist. Updated tooling included GCC 15, Go 1.24, Node.js 24 and .NET 10.

Version 10.2, dated May 20, 2026, kept the momentum. The extensions repository gained goose, an optional console assistant with streaming answers and groundwork for the MCP protocol, through which AI agents will be able to interact with the system. Image mode received pre-staged updates without an immediate reboot plus cryptographically sealed images as a technology preview. The runtimes took a noticeable jump: Python 3.14 with experimental free-threaded builds that drop the global interpreter lock, PostgreSQL 18, OpenJDK 25, PHP 8.4, Go 1.26 and Rust 1.92.

Upgrade paths deserve a separate note. Direct in-place upgrades are supported from RHEL 9.6 to 10.0 and from 9.7 to 10.1. Jumping straight from the eighth version to the tenth is impossible; the migration runs in two stages through RHEL 9 using the Leapp utility.

RHEL 9 vs RHEL 10 at a glance

The table below condenses the key differences between the two generations into a single view.

The pattern is clear: the tenth version replaced entire subsystems, from graphics and audio to remote access and cryptography, rather than polishing individual packages. That scale of change is exactly why the migration deserves preparation, which we cover below.

How to try RHEL 10 without a paid subscription

A production subscription costs money, yet getting hands-on with the platform is free through several official and community routes.

The first route is the Red Hat Developer program. A no-cost individual subscription covers up to 16 systems and grants access to the same software a paying customer receives, aimed at development, testing and small-scale use. In 2025 the program grew a business track that raises the ceiling to 25 instances per registered user, which lets corporate teams evaluate the platform without procurement paperwork. For a quick look there is also a 60-day evaluation edition available for download after registration.

The second route, and the most popular one, is the community rebuilds. AlmaLinux 10 and Rocky Linux 10 are distributed free of charge, with no accounts or registration, while remaining binary compatible with the original: an application built for RHEL 10 starts on them unchanged, and security updates arrive within hours to a couple of days. Spinning up a test machine takes minutes, since both systems ship as ready-made templates when you rent a VPS on Serverspace, so a fresh server appears from the control panel without any manual image handling.

Choosing between the two rebuilds is largely a matter of taste. Rocky Linux aims for the closest possible clone of the original, while AlmaLinux allows itself independent fixes and keeps supporting older hardware. The package base and administration commands match on both, so any accumulated experience transfers freely between them.

Cloud hostingCheap cloud hosting for any number of sitesHosting prices

Who gains the most from moving to RHEL 10

Four typical scenarios show where the tenth version pays off quickly.

Greenfield infrastructure. When a project starts today, picking the ninth version with its shorter remaining support window makes little sense. The tenth generation offers a runway until 2035 and postpones the next forced migration far into the future. The same logic applies to the rebuilds: new servers are best provisioned on AlmaLinux 10 or Rocky Linux 10 from day one.

Fleets of identical servers. Once dozens of machines must stay uniform, image mode turns from a fashionable feature into a practical tool. Updates roll out as image swaps, configurations stop drifting, and a rollback takes minutes. Teams with an established CI/CD pipeline benefit most, because the operating system becomes just another build artifact.

Data with a long lifespan. Healthcare, finance and government organizations keep records for decades. For them post-quantum cryptography stops being a theory: traffic intercepted today must remain unreadable fifteen years from now, and the tenth version closes that risk with stock components. Regulators in several industries have already started asking vendors about quantum-readiness roadmaps, so an operating system that answers the question by default saves a round of paperwork.

Web workloads on current runtimes. PostgreSQL 18, PHP 8.4, Python 3.14 and OpenJDK 25 out of the box remove the need for third-party repositories and manual package builds. Before moving live services it is wise to rehearse on a staging environment: a cloud VPS server suits that job well, since the stand exists only for the duration of the tests and gets deleted right after, with no hardware purchased for a one-off task.

Common migration mistakes and how to avoid them

Five missteps come up in migration stories more often than all others combined.

1. Upgrading without checking the processor. An administrator launches the upgrade on a server from 2011, and the machine never comes back after the reboot. Verify the microarchitecture level in /proc/cpuinfo or via ld.so with its help flag before touching anything. For aging hardware, pick the AlmaLinux build for x86-64-v2.
2. Trying to skip a generation. There is no direct path from RHEL 8 to the tenth version. Plan two stages: first an upgrade to the current ninth release, then the move to ten, with proper testing wrapped around each step.
3. Scripts with legacy interface names. The net.ifnames=0 parameter is gone, and the eth0 interface no longer exists. Firewall rules, monitoring checks and automation that hardcode the old name will break after the switch. Search your configuration files ahead of time and move them to current names such as ens3.
4. Carelessness during installation. The installer now grants administrator rights to the first created user by default, with the checkbox pre-ticked. When a contractor sets up the server, a spare account with full privileges becomes a security hole. Untick the box whenever elevated rights are unnecessary.
5. Inflated expectations of the rebuilds. AlmaLinux and Rocky mirror the RHEL package base, yet the proprietary Lightspeed service and the offline assistant are absent from both. If the migration plan leaned on an AI helper, the free builds will not provide one, so keep the familiar diagnostic tools in the kit.

Conclusion

RHEL 10 turned out to be a release about the long horizon: post-quantum protection targets the threats of the coming decade, image mode moves server management onto container-style rails, and support until 2035 gives businesses a rare degree of predictability. The 10.1 and 10.2 updates proved the platform is evolving at speed, especially around tooling for AI workloads.

A pragmatic way to start costs nothing: check your hardware against the x86-64-v3 baseline, rent a VPS with a ready-made template of the tenth generation, run your applications on it, and only then schedule the production move. That order of operations protects both the budget and the on-call rotation.