OpenPanel

Traditional hosting panels share one Apache, one MySQL, and one PHP runtime across every account on the machine, which is why a single noisy customer can spoil a server. OpenPanel provisions a dedicated Podman context per user instead, so each account gets its own web server container, database container, PHP-FPM containers, private network, and storage volume.

The host itself runs both panels plus Caddy for reverse proxy and TLS, BIND9 for DNS, a shared phpMyAdmin, and MySQL for user metadata. OpenAdmin is the administrator interface for creating users, defining hosting plans, and editing settings, while OpenPanel is what customers log into to manage their own containers, sites, limits, and backups. Installation is one command on a supported VPS or dedicated server.

Isolation changes what a hosting user can do without filing a support ticket.

• Per-user stacks: choose Apache, Nginx, OpenLitespeed, or Openresty with Varnish, and MySQL, MariaDB, or Percona.
• Mixed runtimes: domains on one account can run different PHP versions, or Node.js and Python.
• Resource limits: CPU, memory, and storage are capped per account.
• Self-service: users restart services, read domain logs, and configure their own backups.
• Billing integrations: FOSSBilling, WHMCS, and Blesta connect to the panel, and the interface can be white labeled.
• Migration: cPanel and CyberPanel backups import directly.

Published install tests show passing runs on Ubuntu 24 and 26, Debian 13, AlmaLinux 9 and 10, and CentOS 10. Note the licensing: the panel interfaces ship under a EULA, and only OpenCLI and the configuration files carry an open license.