P
Panelze

Architecture overview

High-level components

Layer Responsibility
Panelze Engine Nginx/Apache/OpenLiteSpeed vhosts, PHP-FPM pools, TLS, BIND DNS, mail stack, quotas
Panel (Laravel) HTTP UI + API: auth, RBAC, Stripe checkout, license verification
Panel database Tenants, sites, service metadata — not customer site databases
Customer DBs MySQL/PostgreSQL created via Engine; backups from the panel

Request path

  1. Operator opens the panel over HTTPS (cookies, optional 2FA).
  2. Actions become Engine calls protected by ENGINE_INTERNAL_KEY / ENGINE_API_SECRET.
  3. Engine performs privileged host changes; audit via panel storage/logs and journalctl.

Licensing

  • Keys may be pasted in Panel → License or validated against a hub (LICENSE_SERVER_URL).
  • Community allows up to 5 sites per server; Pro raises limits and unlocks modules.

See Pro modules and License server hub.

← Back to documentation home