If you run more than one hosting server, you already know the routine. One browser tab per box, one login per box, one set of updates per box, and a spreadsheet somewhere that tells you which customer lives where. Most hosting control panels were designed for a single machine, and every server you add multiplies the work instead of sharing it.
Unicorn Panel was built the other way around. It is a self-hosted, multi-server hosting control panel where one Primary panel manages every website, database, mailbox and DNS zone across any number of servers. And for small fleets it costs nothing: two servers and two accounts are free, with unlimited sites, databases, mailboxes and zones.
This guide explains what a multi-server control panel is, how Unicorn Panel's fleet architecture works under the hood, what you get for free, and how to have your first two servers running from one panel in about ten minutes.
What is a multi-server hosting control panel?
A multi-server hosting control panel is software that manages websites, databases, email and DNS across several servers from a single interface and a single login. Instead of installing a separate panel on every machine, you install one control point and attach the other servers to it as managed workload hosts.
The difference matters more than it sounds. With a single-server panel, "multi-server" usually means one of three workarounds:
- A second install per box, with a separate login and a separate set of accounts on each.
- A remote database or mail node only, where one service can live elsewhere but websites still cannot.
- A paid add-on or cluster product, often with a shared central database you now have to run, back up and scale.
A panel that is multi-server by design treats every host as a first-class object. You can create a website on server three while logged into server one, open server five's database admin without giving it a public address, and update all of them in one action.
Why single-server panels struggle with fleets
The classic panels were built when a hosting company meant one big server. They grew sideways from there, and it shows in a few predictable places.
Every server is an island. Customer accounts, backups and settings live on the box they were created on. Moving a site between servers is a migration project, not a dropdown.
Isolation is an upsell. On many panels, per-site resource limits and filesystem isolation arrive through an extra product layered on top. Without it, one busy or compromised site can starve or reach its neighbors.
Updates are a chore that scales linearly. Ten servers means ten update sessions, ten sets of release notes to check and ten chances to forget one.
Backups stop at the server's edge. A backup that only exists on the server it came from is not much of a backup. Getting it somewhere else often means FTP scripts or a separate tool.
When we checked cPanel v138, Plesk 18.0.81, DirectAdmin 1.711 and Virtualmin 8.2.0 in September 2026 for our comparison, none of the four could run sites, databases, mail and DNS across a fleet from one panel. Their multi-server support covered a mail node or remote databases, not the whole workload. (These products update often, so check current versions before you decide. Our cPanel alternatives guide goes through the comparison line by line.)
How Unicorn Panel's fleet architecture works
Unicorn Panel uses a simple two-tier model that you can understand in ten seconds and scale as far as you like. The full detail is on the architecture page; here is what matters for day-to-day operation.
The Primary: one panel for everything
The first server you install becomes the Primary. It runs the operator-facing panel, the operator API, and keeps a mirror of the whole fleet's state. This is the only URL you and your customers ever need to log into.
Secondaries: workload hosts with assigned roles
Every other server is a Secondary. Each one runs whichever roles you assign it from the Primary: web, database, mail, DNS, backup storage, or any mix. A typical small fleet might look like this:
| Host | Roles | What it serves |
|---|---|---|
| Primary | Panel, web | The control panel plus a handful of sites |
| web-01 | Sleipnir or NGINX, PHP | Customer websites |
| db-01 | Mimir, MariaDB or PostgreSQL | Customer databases |
| mail-01 | Hermes mail suite | Mailboxes and webmail |
| dns-us, dns-eu | Heimdall DNS | Authoritative nameservers in two regions |
| backup-01 | Backup storage | Off-host backup copies |
You do not need that many boxes to start. Two servers, one Primary and one Secondary, is a perfectly good fleet, and it is exactly what the free tier covers.
One small daemon per host
Each host runs a single small daemon that does the privileged work: creating containers, writing configs, issuing certificates. The panel itself never needs the run of the machine. It is the same binary on every host, so there is nothing to assemble per server.
No central database to babysit
This is the design choice that makes Unicorn Panel scale cleanly. Each host keeps its own state, and the Primary mirrors it. There is no shared database in the middle to tune, replicate or lose, and no cluster to stand up before your second server. Every action on a Secondary's resource echoes back to the Primary so the panel's view stays current, while health, CPU and memory are polled on a schedule.
API keys between hosts, not shared SSH
The Primary talks to each Secondary over HTTPS using that server's own API key, with its own scope. A Secondary answers only the calls it recognizes. There is no shared root SSH key, no agent forwarding and no shared filesystem across the fleet, which removes one of the most common ways a single compromised server turns into a compromised fleet.
Fails soft, not shut
The license check runs only when a key changes, when the panel upgrades, and when a role is installed. It does not run on every request. If Unicorn's servers are ever unreachable, your panel keeps working on the paid plan for 30 days before falling back to the free tier, and your customers see no difference.
Adding a server takes one command
Attaching a new Secondary is a single line. The Primary gives you a register URL, and you run this on a fresh Alpine Linux box:
wget -qO- https://unicornpanel.com/install | sh -s register <register-url>The installer enables the Alpine community repository, sets up disk quotas, installs the Unicorn core, configures an nftables firewall, installs Podman and Unicorn Shield, and registers with the Primary. There is no key to copy onto the box and no config file to hand-edit. The Primary's own secret is never copied around the fleet.
Once the new server appears in your Servers list, you pick its roles from the Primary. The Secondary fetches each role, installs it in the background and reports back. The panel stays responsive while a role builds. (Because the whole platform is built on Alpine, we wrote a separate guide on why Alpine Linux makes such a good hosting base.)
Running the fleet day to day
Once servers are attached, the fleet management screens are where the multi-server design pays off.
Live server health. CPU, memory, disk, network, container status, role versions, OS and kernel for every host at once. A host that stops answering is flagged rather than quietly ignored.
Per-host logs without a terminal. Web, database, mail, DNS, panel, proxy, firewall and SSH logs for any server, from the browser. You only see tabs for what that host actually runs.
Cross-server admin tools. Open a Secondary's database admin, webmail or terminal through the Primary's own URL. The Secondary never needs a public address of its own for those tools.
Bulk updates. When a role has a new version, update it on every host that runs it in one action. Bring the panel itself up to date across the whole fleet from one screen. Ten boxes take the same effort as one.
Global settings that replicate. Set a preference once on the Primary and it is pushed to every Secondary. Your fleet stays consistent because it is configured in one place, not copied by hand.
Reboot-safe tenants. A host coming back from a reboot brings its tenant containers up patiently, retrying slow starters instead of giving up and leaving sites down.
Graceful decommissioning. Retire a server from the panel when you are done with it, and your bill follows the new count.
Every workload, on any host
A multi-server panel is only useful if every kind of workload can live anywhere. In Unicorn Panel, all eight feature areas are fleet-aware and driven by the same REST API.
Websites
The provisioning wizard checks the domain as you type, lets you choose which server the site lands on, and builds the container, files, web server config and Let's Encrypt certificate there. You pick the web engine and the PHP version per site, and both can be changed later. Twelve PHP versions are available, from 5.6 through 8.5.
Day-to-day tools include a WordPress toolkit (update core, manage plugins, search-and-replace URLs, log into wp-admin as any admin), per-site analytics with a year of history, AI-crawler and bad-bot blocking, password protection, a browser terminal, a cron editor, and Redis or Memcached alongside the site. Deleting a site on another server cleans up there too, with checkboxes for its DNS records, databases and backups.
Databases
MariaDB, MySQL, PostgreSQL and Unicorn's own lightweight Mimir engine can all run on the same host on non-conflicting ports. You get per-database users, live queries-per-second, a process list with kill, one-click optimize, detection of tables missing primary keys or indexes, and import/export with a real progress bar so multi-gigabyte dumps never look hung. Adminer, phpMyAdmin and phpPgAdmin install with the role and open through single sign-on. See the databases page.
The Hermes mail suite handles SMTP, IMAP, Sieve filtering, per-domain DKIM keys, spam scoring and attachment virus scanning, with Roundcube webmail that opens already signed in. Spam thresholds are set per domain rather than per server, and resellers can serve all of it from their own mail hostname. More in the email features.
DNS
Heimdall is Unicorn's built-in authoritative DNS server. It replicates zones across multiple hosts so your customers get answers from geographically separate nameservers, stamps A records automatically when you create a site, and supports optional DNSSEC. See DNS.
Backups
Backups are split by resource: websites, databases, mailboxes and panel config each back up separately and restore separately. You can restore one file, one database table or one mail folder, and mailbox restores merge by default so nothing received since the backup is lost. Backups can be stored on another server in the fleet or pushed to S3-compatible storage, SFTP or rsync. Our granular backup guide covers this in depth.
Isolation by default: a container per site
Every website in Unicorn Panel runs in its own Podman container, with its own Linux user, its own ports, its own PHP-FPM pool and its own limits on CPU, memory, disk and processes. Nothing is shared between tenants.
On a multi-server fleet this matters twice. First, one noisy site cannot starve its neighbors on the same host. Second, a compromised site is a contained problem rather than everyone's problem. And unlike panels where this level of isolation requires a paid add-on, it is simply how every site is built here, including on the free tier. We explain the approach in detail in container-per-site hosting explained.
A first-party stack, or the engines you already know
Unicorn Panel ships its own implementation of every core hosting service, named after figures from Norse and Greek mythology:
| Engine | Replaces or sits alongside | Role |
|---|---|---|
| Sleipnir | NGINX, Apache, OpenLiteSpeed | Web server, designed to sit behind the panel's proxy |
| Hermes | Postfix, Dovecot, rspamd, ClamAV | One privilege-separated mail server written in C |
| Mimir | MariaDB, MySQL, PostgreSQL | A lighter SQL server for WordPress, WooCommerce and similar sites |
| Heimdall | External DNS software | Authoritative DNS with multi-host replication |
Because all four are built to integrate with the panel, they share uniform logging, uniform metrics and uniform restart semantics. Operating the stack feels like operating one product.
You are never forced onto it, though. NGINX, Apache, OpenLiteSpeed, MariaDB, MySQL and PostgreSQL remain fully supported, and you choose per host and per site.
Built for resellers from the start
The fleet model carries straight through to reselling. Accounts follow a three-tier structure: operator, reseller, customer. Each reseller gets a slice of your fleet to sell, and their customers only ever see their own sites.
White-label support goes further than a logo swap. Each reseller can have their own panel domain, logo, colors and favicon, their own SMTP for transactional mail, and their own mail hostname that customers use for IMAP, SMTP and webmail. Anything a reseller has not customized falls back to your defaults rather than breaking. All of this is included in the standard pricing, not sold as an add-on. If you are thinking of starting a hosting brand, read our guide to starting a white-label hosting reseller business.
Automate the whole fleet
Nearly every action in the panel is also a documented REST endpoint, because the panel itself is built on that API. Keys are per account and carry exactly the access that account has in the panel. One API call can reach a resource on any server in the fleet, and none of it sits behind a premium tier.
For the panel owner, a unicorn CLI binary sits on every host with subcommands that mirror the panel: websites, databases, backups, emails, DNS, host and proxy. Upgrades are a single unicorn upgrade, and every upgrade snapshots state before it starts. Our API and CLI automation guide has worked examples.
How Unicorn Panel compares
Here is a condensed view of Unicorn's own comparison table, checked in September 2026. Several competitor cells depend on the edition you buy; the full table and notes are on the compare page.
| Capability | Unicorn Panel | cPanel | Plesk | DirectAdmin | Virtualmin |
|---|---|---|---|---|---|
| Sites, databases, mail and DNS across the fleet from one panel | Yes | Mail node only | Remote databases only | Remote databases only | Remote DB, DNS in Pro |
| Every site in its own container with its own limits | Yes | Needs paid CloudLinux | Per-account cgroups, Web Pro+ | Per-account cgroups | Per-account cgroups, Pro |
| Restore a single database table | Yes | No | No | No | No |
| Backups can land on another server in the fleet | Yes | No | No | No | Webmin peer, manual |
| Passkey sign-in | Yes | TOTP only | Free extension | TOTP only | TOTP only |
| First-class arm64 builds | Yes | No | Ubuntu 22.04 only | Yes | Yes |
| No usage telemetry | Yes | Some is mandatory | Partly opt-out | Not documented | None found |
What "free" actually means
Plenty of software is "free" until the moment it becomes useful. Unicorn Panel's free tier is deliberately generous, and the paid tier is deliberately simple. The full breakdown is on the pricing page.
Free, forever: 2 servers and 2 panel accounts, with unlimited websites, databases, mailboxes and DNS zones. Support comes through the community forum.
Paid, from $5 a month: covers 3 servers and 10 accounts. Past that it is $1 per extra server and $0.30 per extra account, per month, excluding tax. Paid plans add private ticket support.
| Fleet size | Monthly price |
|---|---|
| 2 servers, 2 accounts | Free |
| 3 servers, 10 accounts | $5 |
| 5 servers, 25 accounts | $11.50 |
| 10 servers, 50 accounts | $24 |
| 25 servers, 100 accounts | $54 |
| 50 servers, 250 accounts | $124 |
A few details make the pricing easier to trust:
- Only servers and accounts are counted. Websites, databases, mailboxes and DNS zones are never counted or limited, at any tier.
- The $5 rate is launch pricing, locked in. If prices rise later, existing subscribers keep the rate they signed up at for as long as the subscription stays active.
- Going over never breaks anything. Extra servers and accounts are simply added to the next invoice.
- Short-lived servers are not a trap. Billing follows the count the panel reports, so a server added for a short job and removed does not keep costing you.
- Canceling is not a hostage situation. You keep running until the end of the paid period, then the panel drops back to the free tier. Nothing is locked or deleted.
- There is a 30-day money-back guarantee on the first invoice.
For larger operators, Enterprise options include SLAs, a named technical contact, white-glove migration, volume licensing, air-gapped offline licensing and managed upgrades.
Your data stays on your servers
Unicorn Panel is fully self-hosted. Sites, databases, mailboxes and customer accounts live on your servers, never on Unicorn's. The panel has no usage telemetry.
Only two small calls ever leave your fleet. One is a billing signal carrying the current server count, account count, a timestamp and a random install ID, sent when you add or remove a server or account plus a daily catch-up. The other is the license check described above. Nothing about your sites, domains, database contents, mailboxes, customers, traffic or resource usage is sent. The FAQ spells this out in full.
Who Unicorn Panel is for
Unicorn Panel is a strong fit if you are:
- A small hosting company or agency outgrowing one server and tired of juggling separate panels.
- A reseller or aspiring hosting brand who needs real white-labeling without paying extra for it.
- A freelancer or developer hosting client sites who wants isolation and per-site PHP versions without building it by hand.
- A homelab or ARM enthusiast running Graviton, Ampere, a Raspberry Pi or a Mac mini, since every binary ships for both amd64 and arm64.
A few honest caveats, so you can plan around them. The built-in import wizard for cPanel, Plesk, DirectAdmin, Enhance and Duplicator archives is still being finished; check the releases page for what has landed. Hermes is a mail server, not a bulk sender, so keep a dedicated provider for newsletters or high-volume transactional mail (Hermes can relay outbound through a smarthost if you prefer). And because the product is new and moving quickly, some documentation sections are still being updated.
Get your fleet running in about ten minutes
- Start two fresh Alpine Linux servers (3.20 or newer, at least 500 MB RAM and 5 GB disk each). A VPS provider with snapshots is a good idea.
- Install the Primary by running
wget -qO- https://unicornpanel.com/install | shas root on the first server. You get a login link and admin credentials at the end. - Open port 8727 if your provider has a network firewall, then log in.
- Secure the admin account under My Account: change the password and enable 2FA or passkeys.
- Set a control panel domain under Settings so the panel gets a free SSL certificate and passkeys work.
- Add your Secondary from Servers → Add server, and paste the register command onto the second box.
- Assign roles to each server, then create your first site on whichever host you like.
Prefer to look around first? The live demo is a sandboxed, read-only account on the real panel.
Frequently asked questions
Is Unicorn Panel really free? Yes. Two servers and two panel accounts are free with unlimited websites, databases, mailboxes and DNS zones, for as long as you like. You only pay when you go past either limit.
How many servers can one Primary manage? There is no fixed limit on Secondaries. Because each host keeps its own state and there is no central database, the architecture is designed to grow with your fleet.
Do my servers need public IP addresses for the admin tools? No. Database admin, webmail and terminals on a Secondary open through the Primary's URL via the cross-server proxy.
Can I mix Unicorn's engines with NGINX, MariaDB or PostgreSQL? Yes. The first-party engines are the default, but the familiar engines are fully supported and chosen per host and per site.
What operating system does it need? Alpine Linux 3.20 or newer, on amd64 or arm64. Read why we built on Alpine.
What happens if I stop paying? Your panel returns to the free tier at the end of the paid period. Your servers, sites, databases and mailboxes stay exactly where they are.
Run your whole fleet from one panel
Most hosting panels were built for one server and have been apologising for it ever since. Unicorn Panel starts from the fleet: one Primary, any number of Secondaries, a container per site, a complete first-party stack, and pricing that stays honest as you grow.
Install it free on your first two servers today:
wget -qO- https://unicornpanel.com/install | shOr explore the live demo first. When your fleet outgrows the free tier, the $5 launch price is yours to keep.