Choosing an Operating System for Your VPS

Every unmanaged VPS from aoitcloud lets you choose the operating system yourself, and choose carefully – because unlike managed hosting, nobody is going to swap it out for you later. This page is the starting point: what each option actually is, who it’s genuinely for, and where to go for the practical detail once you’ve picked one.

“Unmanaged” means exactly that: we provision the server, you own everything above it – updates, users, firewall, the works. If that’s new to you, every guide linked below assumes no prior experience with that specific OS.

The three families

Ten operating systems sounds like a lot to compare, but they really only fall into four groups, and once you know which group you’re in, most of what you need to know about day-to-day administration is shared across the whole group.

RHEL-compatible (dnf, firewalld, systemd)

AlmaLinux, Rocky Linux, Oracle Linux, VzLinux, and Fedora are all built around the same package manager (dnf), the same firewall tool (firewalld), and the same service manager (systemd). Learn one, and you’ve effectively learned all five at the command-line level – what differs between them is support lifecycle, governance, and a handful of distinctive extras.

Debian-based (apt, ufw)

Ubuntu and Debian both use apt for packages and, typically, ufw as a simple firewall front end. Ubuntu is Debian with a fixed release schedule, commercial backing, and a few extra conveniences layered on top.

BSD (not Linux at all)

FreeBSD and OpenBSD share a common Berkeley Unix ancestry, a coherent single-project base system, and package tooling that looks similar on the surface (pkg on FreeBSD, pkg_add on OpenBSD) but isn’t the same command family – don’t assume commands transfer between the two. Neither is Linux, and Linux muscle memory only gets you so far on either.

CoreOS (a category of one)

Fedora CoreOS doesn’t belong in any of the above groups. It’s immutable, configured once at boot via an Ignition file rather than administered afterwards, and built specifically to run containers with near-zero ongoing maintenance. Read its orientation post before you provision it – the usual “create a user, install some packages” mental model genuinely doesn’t apply.

At a glance

OS	Family	Package manager	Pick this if…
AlmaLinux	RHEL-compatible	dnf	You want the default, low-risk RHEL-family choice – long support, huge ecosystem, cPanel/Plesk ready
Rocky Linux	RHEL-compatible	dnf	You want the same as AlmaLinux, with a governance model tracing back to CentOS’s original co-founder
Oracle Linux	RHEL-compatible	dnf	You want a newer optional kernel (UEK), or you already have Oracle Premier Support for Ksplice live patching
VzLinux	RHEL-compatible	dnf	You’re specifically working inside a Virtuozzo-based virtualisation stack
Fedora	Standalone Linux	dnf	You need the newest packages and are prepared to upgrade the OS roughly every year
Ubuntu	Debian-based	apt	You want a predictable, fixed LTS schedule and the largest server Linux community
Debian	Debian-based	apt	You want the most minimal, conservative base – no snap, no commercial layer
Fedora CoreOS	Immutable	none (containers only)	You’re running containerised workloads and want the host OS to need almost no maintenance
FreeBSD	BSD	pkg	You want native ZFS, jails, or a coherent single-project base system for networking/storage roles
OpenBSD	BSD	pkg_add	You want the smallest, most audited attack surface – firewalls, mail servers, DNS, jump hosts

RHEL-compatible: AlmaLinux, Rocky Linux, Oracle Linux, VzLinux, Fedora

AlmaLinux is the default recommendation in this family: free, 1:1 binary-compatible with Red Hat Enterprise Linux, backed by a non-profit foundation, and supported for roughly a decade per major version. Rocky Linux is functionally identical day to day – the real differences are in governance and history, not anything you’ll notice at a terminal. Oracle Linux adds an optional newer kernel and, for Premier Support customers, Ksplice live kernel patching. VzLinux is a genuine but niche option, built for Virtuozzo-based hosting stacks specifically.

Fedora sits apart from the other four: it’s the upstream testing ground RHEL itself is built from, which makes it the newest and least stable of the group – each release is supported for only around 13 months, so it demands a yearly upgrade routine that AlmaLinux and Rocky don’t.

Once you’ve picked one, the day-to-day mechanics are shared across all five: managing packages with dnf, firewalld basics, and managing services with systemd.

Debian-based: Ubuntu and Debian

Ubuntu is almost certainly the OS you’ve already used before, and it’s the safest general default if you’re not sure which family to pick – see what Ubuntu Server is and why you should run its LTS release, not an interim one. Debian is the project Ubuntu is built on – more minimal, more conservative, no snap by default, and a natural pick if you found Ubuntu’s defaults too opinionated.

Both share apt for package management. Ubuntu-specific detail is covered in creating a sudo user, ufw firewall basics, snap vs apt, and automatic security updates. Debian-specific detail, including the sudo-isn’t-installed-by-default gotcha, is in Debian’s setup checklist, creating a sudo user on Debian, and Debian’s stable/testing/unstable branches.

Not Linux: FreeBSD and OpenBSD

FreeBSD is a complete, single-project Unix operating system with a genuine reputation for stability in networking and storage – native ZFS and jails are its standout features. OpenBSD is built by a small team obsessed with security and correctness above all else – it originated OpenSSH, and it’s the natural choice for a firewall, mail server, DNS server, or any box where a minimal, heavily audited attack surface matters more than a huge software ecosystem.

Neither shares Linux’s tooling: FreeBSD uses pkg and the Ports Collection, OpenBSD uses pkg_add, pkg_info, and pkg_delete – a different command family, not the same tool under a different name. Firewalling is native pf on both, originally an OpenBSD project later ported to FreeBSD.

A category of one: Fedora CoreOS

Fedora CoreOS doesn’t fit the “install packages, create users, administer over time” model every other OS on this page follows. It’s immutable – configured once via an Ignition config at first boot, not administered afterwards – built to run containers with Podman, and it updates and reboots itself automatically by default. Read its orientation post before provisioning one; it’s genuinely not a drop-in replacement for a traditional server OS, even though it’s Linux-based.

Still not sure?

If you don’t have a specific reason to pick something else, AlmaLinux and Ubuntu are the two safest general-purpose defaults – both have huge communities, long support windows, and near-universal software compatibility. Everything else on this page earns its place for a specific reason: freshness (Fedora), a particular kernel feature (Oracle Linux), a specific virtualisation stack (VzLinux), storage and networking strength (FreeBSD), security minimalism (OpenBSD), or a container-first, self-maintaining host (CoreOS). Pick the reason that matches what you’re actually building, not the name you’ve heard of most.