Proven on five distributions, across twelve OS releases
The same panel, wherever you run it
A control panel is only as trustworthy as the servers it has actually run on. Unit tests are cheap and they miss the things that matter most — the way a package is named on one distribution and split into two on another, the label a security policy silently refuses, the service that starts but never listens. So we do not rely on them alone.
Before a release ships, Nimbopanel is installed from scratch on real, freshly provisioned servers across five Linux distributions and twelve OS releases — Ubuntu, Debian, AlmaLinux, Rocky Linux and CloudLinux, each on its current major versions (Enterprise Linux 8, 9 and 10 included) — and driven through the full job an operator would do. Each run is over 850 live checks, and a release only goes out when every one of them passes.
What "tested end to end" actually means
Each pass is not a page that loads. It is the whole lifecycle, on the box:
- Install and set up from the signed public release, the same one-line command you would use, including the browser setup wizard.
- Create accounts, and prove each one is sealed in its own Linux user with its own PHP — that one site genuinely cannot reach another.
- Mail that authenticates — a real message goes out and comes back signed, with SPF, DKIM and DMARC all passing.
- Authoritative DNS, databases, files, SSL that issues and renews itself.
- Backups and restore, including recovering a single database with binary data intact.
- Resellers and white-label — a reseller's customer resolving publicly on the reseller's own nameservers, with a real certificate, and every admin route refused to them.
- Resilience — services killed and recovering on their own, the clock wound forward to force a certificate renewal, and a genuine reboot with every site still serving afterwards.
When the docs say an OS is "tested end to end," that is what stands behind the words.
CloudLinux, honestly
On CloudLinux, per-account LVE resource limits are honoured where the kernel provides them, so a busy account cannot starve its neighbours. We are also plain about what we do not yet integrate there — CageFS and the PHP Selector are not wired in, and we say so rather than imply more than we ship.
Why it matters to you
It means you can pick the distribution your team already knows and get the same panel, the same features and the same behaviour — not a "supported" checkbox that turns out to be a rough edge in production. And it means when something does need fixing, we find it on a real server first, not on yours.
Read the installation guide for the current list, or see everything the panel includes.