Most people who rent a server rent an Ubuntu one. It is the default image at nearly every provider, it is what your team already knows, and it has the deepest pool of answers when something goes wrong at two in the morning. Unicorn Panel now runs on it.
This guide covers what you get, what the requirements are, how the install works, and where Ubuntu differs from Alpine Linux in practice. If you have no existing preference between the two, read why the panel is built on Alpine as well and pick deliberately.
Why run a control panel on Ubuntu
Familiarity is a real operational advantage. Your runbooks, your monitoring agents, your team's muscle memory and almost every third-party install script assume a Debian-family system. On Ubuntu, apt works the way you expect, the paths are where you expect, and a problem you have not seen before has almost certainly been written up by someone else.
Long-term support releases have long support windows. Ubuntu LTS releases get five years of standard security maintenance, which matters for a hosting box you would rather not rebuild every year.
Hardware and provider coverage is excellent. Every VPS provider offers an Ubuntu image, most offer it as the default, and arm64 images are as well maintained as amd64 ones.
Which Ubuntu releases are supported
Unicorn Panel supports Ubuntu 24.04 LTS and Ubuntu 26.04 LTS. These are the two releases we test against, so they are the two we support. The installer detects the host and takes the right path on its own: there is no separate build to download and no flag to pass.
Interim (non-LTS) releases are not supported. On a hosting server you want the five-year support window, not the nine-month one.
You can mix Alpine and Ubuntu in one fleet
Unicorn Panel is a multi-server panel, and the fleet does not have to be uniform. An Alpine Primary with Ubuntu secondaries works. So does the reverse. So does a fleet where the mail server is Ubuntu because that is what your mail admin knows, and everything else is Alpine because it is smaller.
Nothing about the panel's cross-server model changes. Each host keeps its own state, the Primary mirrors it, and the hosts talk over the panel's own authenticated API rather than shared SSH keys. The architecture guide covers that model in full.
How Unicorn Panel is built on Ubuntu
A container per site, on Podman
Every website gets its own Podman container with its own unprivileged user, its own PHP-FPM pool, its own Redis and Memcached if you enable them, and its own CPU and memory caps. A tenant cannot read another tenant's files, and a runaway site cannot starve its neighbours. This is the same model on both operating systems, and it is covered in depth in container-per-site hosting.
One binary, not a runtime stack
The panel ships as a static unicorn binary plus its container images. There is no Python or Java runtime underneath it to break on a distribution upgrade, which is the usual way a panel install rots over a few years.
A native nftables firewall and Unicorn Shield
The firewall is nftables, driven from the panel's own database. Unicorn Shield's ban daemon tails the logs and writes bans straight into the live ruleset. The security guide covers the whole surface.
Per-site PHP from 5.6 to 8.6
Thirteen major PHP versions, each packaged as a swappable role, switchable per site without rebuilding the container. A legacy customer on 5.6 and a modern one on 8.6 run side by side on the same host. See multiple PHP versions per site.
Where Ubuntu differs from Alpine in practice
Most of the panel is identical. Three things follow the host:
Package management. apt rather than apk. You will rarely touch it directly, because roles are container images, but it matters for the next point.
Vulnerability scanning. Unicorn Shield's Vulnerabilities tab reads the host's pending updates and cross-references them against that distribution's own security database plus OSV. On Ubuntu that means apt and Ubuntu's security data; on Alpine it means apk and Alpine's. You get the same screen either way, with CVE identifiers and severity scores that are accurate for the host you are actually running.
Footprint. Ubuntu's base install is larger than Alpine's, and uses glibc rather than musl. The panel's 500 MB floor still holds, but on a very small box Alpine leaves you more room for the sites themselves. If you are deliberately running a 512 MB VPS, Alpine is the better choice.
Requirements and sizing
| Requirement | Minimum |
|---|---|
| Operating system | Ubuntu 24.04 LTS or 26.04 LTS |
| Server | A blank VPS or bare-metal server with no other software installed |
| Memory | 500 MB RAM (enable swap on low-memory servers) |
| Storage | 5 GB |
| Architecture | amd64 or arm64 |
A blank server really does mean blank. If the box already has a web server, a database or another panel on it, the install will collide with them.
Where data lives. Everything is stored under /opt/upcp, with customer containers under /opt/upcp/containers, so either path can be its own partition. Mailboxes from the Hermes role live under the mail service's own data directory, and a server with the backup role writes to /backups, which can be a partition, a network mount or external storage.
Sizing advice. 500 MB runs the panel and a small site. For real customer workloads, size memory to the sites you plan to host, give the mail and database roles more headroom, and pick a provider with snapshots so you have a recovery point underneath the panel's own backups.
Firewall ports
The installer opens what the panel needs, and each role opens its own. If your provider runs a network-level firewall in front of the server, these need opening there too.
| Purpose | Ports |
|---|---|
| Panel | 8727 TCP |
| Websites | 80 TCP, 443 TCP and UDP, 22 TCP for SSH |
| Databases | 3306, 3307, 3308 TCP (MariaDB / MySQL), 5432 TCP (PostgreSQL) |
| DNS | 53 TCP and UDP |
| 25, 143, 465, 587, 993 TCP, plus 4190 TCP for ManageSieve |
Only open the database, DNS and mail ports if that server actually runs those roles. ManageSieve on 4190 is only needed if people manage their own mail filters from a desktop or phone client.
Installing Unicorn Panel on Ubuntu, step by step
- Create a blank Ubuntu 24.04 or 26.04 server and log in as root.
- Run the installer:
wget -qO- https://unicornpanel.com/install | sh
- Wait for it to finish. It ends by printing the panel URL, the admin email address and a generated password.
- If that link does not open, check that your firewall allows port 8727.
- Log in, then open My Account and change the password. Turn on 2FA or a passkey under Login Security while you are there.
- Set a control panel domain under Settings > Control Panel Domain so your customers do not have to type a port number, and so passkeys work.
- Add your SMTP details under Settings > SMTP Settings so password resets and notifications can send.
The same details are written to /root/upcp-installer.log, so closing the terminal before you copy them is not a problem.
The first server you install on becomes the Primary Control Panel. To add another, open Servers > Add server and paste the command it gives you into the new box. That server can be Ubuntu or Alpine.
What it costs
Nothing, for two servers and two accounts, with everything else unlimited: as many websites, databases, mailboxes and DNS zones as those servers will carry, with every engine and role available. No license key is needed to run it. A key raises the server and account limits when you outgrow them. See pricing for the current rates.
Things to know before you install
- It wants the whole server. This is not something you add to an existing box alongside other software.
- Interim Ubuntu releases are not supported. 24.04 LTS and 26.04 LTS only.
- Do not install on a desktop image. Use the server image.
- Plan the data partition early. Moving
/opt/upcpafter you have customers on the box is more work than deciding up front.
Frequently asked questions
Does the panel run differently on Ubuntu than on Alpine? The panel itself is the same. Package management and vulnerability scanning follow the host, and Ubuntu's base footprint is larger. Everything else, including the container model, the roles and the cross-server behavior, is identical.
Can I mix Alpine and Ubuntu servers in one fleet? Yes. The Primary can be either, and secondaries can be either.
Can I migrate an existing fleet from Alpine to Ubuntu? You can add Ubuntu servers to an existing fleet and move sites onto them with the panel's own move-to-another-server action. There is no in-place conversion of an Alpine host into an Ubuntu one.
Which should I pick for a new fleet? Alpine, if you have no existing preference. Ubuntu, if your team already runs it everywhere and that familiarity is worth more to you than the smaller footprint.
Is Ubuntu support a beta? No. It is a supported install target on 24.04 LTS and 26.04 LTS.
Put a real control panel on your Ubuntu server
One command, no license key, and a free tier that covers two servers and two accounts with unlimited everything else. Read the install guide or try the live demo first.