Account isolation and CPU and memory limits explained

For server administrators · Updated 2026-10-29

On this page
  1. What isolation means
  2. Resource limits per package
  3. What happens at a limit
  4. Good to know
  5. Common questions

On a shared server, one hacked or busy website must not affect the others. Every hosting account is isolated and has its own resource limits. There is nothing to install or turn on.

What isolation means

  • Cron jobs and SSH sessions run in a sandbox. They see only the account's own folder in /home, their own processes, a private /tmp, and their own entry in the user list. The server's configuration, other customers' files, logs, mail, backups and the quarantine are hidden.
  • SFTP is confined. Accounts without shell access get SFTP only, starting in their own folder; they cannot list the other accounts.
  • Website PHP can open only the account's own home folder, /tmp and the shared PHP libraries.
  • Backups are owned by the system, not the customer, and are never visible from the account.
  • Shell access is given per package: Shell (SSH) access in the package settings (administrators only).

Resource limits per package

Set them in the administrator panel (https://<server>:2087) → Packages (section Accounts) → the package:

FieldMeaningDefault for a new package
Processor (% of one core)100 = one full core, 200 = two100
Memory (MB)Memory of all the account's processes together1024
ProcessesNumber of processes at the same time100

Enter 0 for unlimited. Saving the package applies the limits to all its accounts.

What happens at a limit

  • Processor: the account is slowed down. Its websites answer more slowly; other accounts are not affected.
  • Memory: only the account's biggest process is stopped (often one PHP request or a script). Others keep running.
  • Processes: new processes cannot start until others end.

Customers see their processor, memory and process limits in Resource Usage in their control panel.

Good to know

  • The limits are enforced by the operating system for every process of the account: websites, cron jobs, SSH sessions and applications (Node.js, Python, Ruby).
  • Memory has no swap: over the limit, a process is stopped instead of slowing the whole server.

Common questions

A customer's site shows errors under load. Is it the memory limit?

Possibly: the biggest process is stopped when the account goes over Memory (MB). Raise the limit in its package, or move the account to a bigger package, and see if the errors stop.

Can one customer read another customer's files?

No. Websites can open only their own account's files, and cron jobs and SSH sessions do not see other accounts at all.

Was this article helpful?

Still stuck?

Ask the AI about your exact situation — it answers from this knowledge base — or contact us.