HostPanel Get 2.2.0

HostPanel 2.2.0 · Linux hosting control panel

A control panel runs as root. This is everything ours may do.

Sixty-nine verbs, each with validated arguments, in one audited file. No generic sudo rule, no shell escape, no plugin that quietly widens the surface. Anything not on the list is refused — including by us.

Ubuntu 22.04 / 24.04 · Debian 12 / 13 · Rocky 9 / 10 · AlmaLinux 9 / 10 · one script · no agent, no phone-home

01 / Why

Feature parity is table stakes. The question is what happens when something gets in.

Every panel lists the same features. Fewer can tell you what an attacker reaches after compromising one customer's PHP — or one panel account. Three answers HostPanel is built around.

Finite root surface

One doorway, written down

The panel process is not root. Privileged work goes through a single wrapper with an enumerated verb list and validated arguments. A rule like sudo certbot * is root by another name — --deploy-hook runs whatever it is handed — so those rules do not exist here.

Tenant isolation

One site cannot read another

Each account gets its own PHP-FPM pool running as its own user, its own directory tree, and database grants scoped to its own databases. There is no server-wide GRANT ALL to hand out, and remote database access is never opened by default.

Tamper-evident record

The log notices edits

Administrator actions are written to a hash-chained audit log that can be verified from the panel. Least-privilege profiles narrow what each administrator may do at the API boundary, and API tokens carry scopes rather than full authority.

02 / What it runs

A full hosting stack, managed from one place.

Linux only, on purpose. Windows hosting is not included and is not planned.

Web

  • nginx, Apache or OpenLiteSpeed
  • Engine set per domain, not per server
  • .htaccess honoured on Apache and hybrid
  • Multiple PHP versions, per-account FPM pools
  • Extensions, limits and settings per site
  • Node, Python and Ruby app services
  • Git deploy and staging copies
  • Let's Encrypt, wildcards, custom CSRs

Mail

  • Postfix or Exim, with Dovecot
  • DKIM, SPF and DMARC records
  • rspamd filtering, per-domain policy
  • Sieve rules and vacation replies
  • Mailing lists, aliases, catch-all
  • Queue and log inspection

Data

  • MariaDB / MySQL and PostgreSQL
  • Redis for object caching
  • Database users with named grant sets
  • Browser for tables and queries
  • Backups, offsite copies, restores
  • Disaster-recovery drills

DNS

  • BIND zones with full record editing
  • DNSSEC signing
  • Cluster peers with signed transfers
  • Dynamic DNS endpoints

Security

  • Firewall with allow and deny lists, in the panel
  • Temporary blocks that expire on their own
  • A protected window: a rule that locks you out undoes itself
  • ModSecurity with the OWASP core rules
  • fail2ban, with jails visible in the panel
  • Two-factor, passkeys, OIDC and SAML
  • Scoped API tokens, hash-chained audit
  • Signed extensions, Ed25519 only

Operations

  • Resellers, hosting plans and quotas
  • Support sessions with a hard time limit
  • Cluster placement across nodes
  • Status pages for your customers
  • Prometheus metrics endpoint
  • Ten interface languages

03 / Migrating

Built to take over from a panel you already run.

Accounts, sites, mail and databases import from cPanel, DirectAdmin and Plesk. The comparison below is about architecture, not feature counts — everyone has the features.

How the privileged surface is arranged
  HostPanel Typical panel
Panel process Unprivileged service account Often root, or root-capable
Root actions 69 enumerated verbs Broad sudo rules or a daemon
Extensions Ed25519 signature required Frequently unsigned archives
Admin authority Least-privilege profiles Usually all-or-nothing
Audit trail Hash-chained, verifiable Plain log file
Firewall In the panel, cannot lock you out A separate tool, usually CSF
Licence Unlicense — public domain Per-account fee, and rising

04 / Billing

Your billing system provisions accounts. It never gets a panel password.

Modules for the systems below turn an order into a signed event. Events enter the same audited job queue as every other provisioning action, so a failed signup is a job you can read, retry and explain — not a silent gap between two systems.

WHMCS module ↓ Blesta module ↓ ClientExec plugin ↓ HostBill signed webhook Upmind signed webhook Paymenter signed webhook Anything else HMAC-SHA256 contract

Install it on a spare server and try to break out of it.

One script on a clean Ubuntu 22.04/24.04, Debian 12/13, Rocky Linux 9/10 or AlmaLinux 9/10 machine. It selects APT or DNF, UFW or firewalld, AppArmor or SELinux, the correct service names and the correct PHP/vhost layout from the detected platform. Existing firewall policy is preserved.

# download, read it, then run it — in that order curl -fsSLO https://github.com/1-vps/hostpanel/raw/refs/heads/main/hostpanel-linux-parity-v2.2.0.tar.gz tar -xzf hostpanel-linux-parity-v2.2.0.tar.gz cd hostpanel-linux-parity-v2.2.0 less install.sh # see what it would do, before it does anything sudo bash install.sh --check --role control,web,mail,dns # then, for real sudo bash install.sh --role control,web,mail,dns