NVMe VPS
4 plans · from $9.95/mo
Enterprise NVMe VPS Hosting
Starter NVMe VPS
1 Core · 2 GB RAM · 20 GB NVMe
$9.95/mo
Rocky Linux 10 arrived in June 2025 with a ten-year lifecycle running
to May 2035. It is a community rebuild of an enterprise distribution —
same package set, same dnf, same SELinux, no licence — built by
the people who did not want a repeat of what happened to CentOS.
$4.95/mo
Billed monthly · 16 plans in 4 ranges
A Rocky Linux VPS from VPS For Life is an unmanaged KVM virtual private server running the current stable Rocky Linux release, with the root account in your hands. Rocky Linux is a free, community-maintained rebuild built for Red Hat Enterprise Linux compatibility, and each major release carries a ten-year lifecycle. Plans run from $4.95 to $69.95 a month across four ranges, every one including a dedicated IPv4 address and a choice of 56 datacenter countries, deployed in about 60 seconds after payment.
dnf, rpm, SELinux and firewalld as standard.Related: AlmaLinux VPS · AlmaLinux vs Rocky Linux · Enterprise VPS hosting · Hardware specifications
Rocky and AlmaLinux sit in the same place on this table for a reason — they are rebuilds of the same upstream. All four distributions are available on every plan.
| Distribution | Current stable | Released | Security support until | Packages | Release model |
|---|---|---|---|---|---|
| Debian view | 13 “Trixie” | August 2025 | August 2028LTS to June 2030 | apt / dpkg | Fixed release, roughly every 2 years |
| Ubuntu view | 26.04 LTS “Resolute Raccoon” | April 2026 | April 2031ESM to April 2036 | apt / dpkg | LTS every 2 years, interim every 6 months |
| AlmaLinux view | 10 | May 2025 | May 203510-year lifecycle | dnf / rpm | RHEL-compatible, tracks RHEL point releases |
| Rocky Linux This page | 10 | June 2025 | May 203510-year lifecycle | dnf / rpm | RHEL-compatible, tracks RHEL point releases |
Both are supported for years yet. The difference that matters on a server is not the dates. It is the CPU baseline.
| Rocky Linux 10 | Rocky Linux 9 | |
|---|---|---|
| Released | June 2025 | July 2022 |
| Active support to | May 2030 | May 2027 |
| Security support to | May 2035 | May 2032 |
| Kernel series | 6.12 | 5.14 |
| Minimum x86 CPU level | x86-64-v3 (AVX2-era CPUs) | x86-64-v2 |
| 32-bit compatibility on x86_64 | Removed | Available |
| Also runs on | ARM64, and RISC-V for the first time | ARM64 |
Check what a CPU supports before you plan a migration to Rocky 10.
On any Linux system with a recent glibc, this lists the x86-64 levels the processor can run.
You need to see x86-64-v3 (supported, searched):
/lib64/ld-linux-x86-64.so.2 --help | grep supported
If a machine you are moving from only reaches v2, Rocky 9 still runs on it until 2032. So does AlmaLinux 10, which publishes a separate x86-64-v2 build. That is one of the few real technical differences between the two rebuilds.
The Rocky project’s own scripts convert a system in place. Which one you need depends on where you start.
| You are on | Route to Rocky |
|---|---|
| CentOS 8, RHEL 8 or another EL8 system | migrate2rocky, in place, to Rocky Linux 8 |
| An EL9 system | migrate2rocky9, in place, to Rocky Linux 9 |
| CentOS 7 | No direct path. A fresh Rocky install and a data move is usually the simpler job |
| Rocky 8 or 9, wanting the next major version | The scripts do not upgrade. Plan a fresh install of the newer release |
Converting an EL8 server — run as root, inside screen or tmux so a dropped SSH session does not interrupt it:
curl -O https://raw.githubusercontent.com/rocky-linux/rocky-tools/main/migrate2rocky/migrate2rocky.sh
chmod +x migrate2rocky.sh
./migrate2rocky.sh -r
Reboot when it finishes. The EL9 script, migrate2rocky9, is in the same
rocky-tools repository.
The project marks these scripts “use with caution”. Take a backup you have tested restoring, because
we hold no copy of your data. Our migration guide walks through the checks before and after.
Including the honest case for picking something else.
Enterprise agents, commercial panels and vendor packages that list RHEL will generally install and run without modification.
Internal runbooks, a client's requirements or a vendor's install guide naming Rocky specifically is the single best reason to pick it over AlmaLinux.
Security updates through 2035 on the release you install today, with no subscription and no entitlement to manage.
In-place conversion means the servers you already built keep running instead of being rebuilt one at a time.
It does not. AlmaLinux offers the same compatibility, the same ten years and the same price here. Pick whichever your documentation names.
The enterprise base is heavier than a minimal Debian install. On the smallest plan that difference is worth counting.
Rocky is compatible with RHEL but is not RHEL and carries no Red Hat support contract. No rebuild satisfies that condition.
No separate enterprise-Linux product line and no surcharge. The entry plan of each range is below.
4 plans · from $9.95/mo
Enterprise NVMe VPS Hosting
Starter NVMe VPS
1 Core · 2 GB RAM · 20 GB NVMe
$9.95/mo
4 plans · from $13.95/mo
Scalable Cloud VPS Solutions
Starter Cloud VPS
1 Core · 2 GB RAM · 30 GB NVMe (triple-replicated)
$13.95/mo
4 plans · from $4.95/mo
Affordable Classic VPS Hosting
Starter Classic VPS
1 Core · 1 GB RAM · 15 GB SAS
$4.95/mo
4 plans · from $24.95/mo
Dedicated Resources, Maximum Performance
Starter VDS (Xeon E3)
2 Cores · 2 GB Dedicated RAM · 50 GB NVMe
$24.95/mo
Every plan includes a dedicated IPv4 address, full root access and open Port 25. See all 16 plans with full specifications.
The RHEL-family way to make a fresh server safe to leave on the internet. Replace
203.0.113.10 with your server’s IP and alice with your username.
ssh root@203.0.113.10
dnf -y upgrade
wheel, not sudo.
useradd -m -G wheel alice
passwd alice
ssh-keygen -t ed25519
ssh-copy-id alice@203.0.113.10
printf 'PermitRootLogin no\nPasswordAuthentication no\n' > /etc/ssh/sshd_config.d/10-hardening.conf
sshd -t && systemctl reload sshd
dnf -y install firewalld
systemctl enable --now firewalld
firewall-cmd --permanent --add-service=ssh
firewall-cmd --reload
/etc/dnf/automatic.conf, set upgrade_type = security and
apply_updates = yes, then start the timer:
dnf -y install dnf-automatic
systemctl enable --now dnf-automatic.timer
getenforce should say
Enforcing. When something is blocked, fix the label or the boolean rather than switching
SELinux off (SELinux basics).
You can reinstall Rocky Linux from the client area at any time. Nothing here is specific to us; these are the same steps on any Rocky server.
From our AlmaLinux & Rocky Linux category, open to read without an account.
dnf, rpm, SELinux and firewalld, both give a ten-year lifecycle per major release, and both cost the same here because neither is a separate product. The real differences are in who governs each project and in how each handles compatibility with upstream RHEL. If your team, your vendor or your documentation already names one, use that one. If not, either is a defensible choice — there is a full breakdown in AlmaLinux vs Rocky Linux, and the AlmaLinux page is here. One concrete difference: Rocky 10 needs an x86-64-v3 CPU, while AlmaLinux 10 also ships a v2 build. migrate2rocky script converts it in place to Rocky Linux 8, and migrate2rocky9 does the same for EL9 systems. Neither upgrades between major versions, and CentOS 7 has no direct path to Rocky. For a CentOS 7 server, a fresh Rocky install and a data move is usually simpler. You hold root on an unmanaged server, so you can run the scripts yourself — the commands are above. Take your own backup first. Current stable release, real root access, a dedicated IPv4 address and your choice of 56 countries — from $4.95 a month, with a 7-day money-back guarantee on first orders.