Resource Isolation
Resource Isolation is what makes Panelica multi-tenant safe: it keeps one account's CPU, memory and processes from affecting its neighbors. Two independent layers are controlled here, each a switch with its own behavior.
Panel Settings → Resource Isolationhttps://YOUR-SERVER-IP:8443/panel-settings#resource_isolationThe two layers
Resource Enforcement (cgroups v2) is the core: it caps each account's CPU, memory and process count at the kernel level, per the account's plan. When a site exceeds its CPU it is throttled; when it hits its memory ceiling it is capped; a fork bomb hits the process limit instead of taking down the server. This is the layer that turns a plan's numbers into real, enforced limits. Alert thresholds (default 90% CPU, 95% memory) let you get warned before an account saturates its allocation.
Namespace Isolation adds Docker-style separation on top: PID and mount namespaces so a confined account cannot even see other accounts' processes or files. It only takes effect when the resource engine is also on, and the page warns you if you enable it without cgroups.
Access
This section is behind the resource_isolation_controls license feature and, for saving, ROOT only (others see it read-only). See roles and permissions. For how isolation shows up inside a customer's own SSH session (their own CPU and memory, not the host's), see SSH & SFTP Access.