All manual sections

DocumentationPackages

Packages

A package sets the limits of an account:

  • Space in GB (site files plus databases);
  • number of sites (every site has its own SFTP access, so this is also the limit of SFTP accesses);
  • number of databases;
  • allowed PHP versions (none selected = all the installed ones);
  • files and folders of the sites (at least 1000);
  • PHP processes per site: the most the administrator or the reseller can give a site (PHP processes), up to 200;
  • traffic per month of the sites in GB: at 80% and 100% the account and its reseller get an email, the sites keep working. The traffic is read from the sites' logs, like the statistics, and starts again from zero at the start of the month. With Over the traffic, suspend the sites the sites show the suspension page until the next month, when they come back by themselves; the account can still sign in to the panel.

The value 0 means unlimited.

Who creates packages

  • The administrator creates global packages, for their direct accounts. A direct account may also have no package (no limits).
  • Every reseller creates their own packages, usable only for their accounts. Every package must fit in their quota (for example, with a 100 GB quota they cannot create a 200 GB package) and a reseller's accounts always have a package.

What happens at the limits

With real disk quotas on, the space and the files of the package are also a limit of the disk: over it the account's sites can't write more files (uploads, caches, updates). Without quotas the panel's limits described below apply.

When an account reaches a limit, the panel refuses with a clear message the creation of new sites or databases and the choice of PHP versions not included. Nothing existing is touched. The administrator can go over the limits when creating something for an account.

A package in use cannot be deleted: first assign another package to its accounts.

Included functions

At the bottom of the package window, Included functions lists the functions of the panel the accounts of the package may use (like cPanel's Feature Manager). Untick the ones to leave out, for example mail for a "website only" package or WordPress for an applications-only package:

  • the function disappears from the menu and from the site tabs for the accounts of the package and for the people of their Team;
  • the panel blocks it in the API too, with a message saying the function isn't included in the package;
  • what is already there keeps working: for example the mailboxes already created keep receiving and scheduled backups keep running. Only what the account can manage from the panel changes.

You can leave out WordPress, app installation, the site builder, file manager, SFTP, FTP, MariaDB and PostgreSQL databases, mail, DNS, scheduled tasks, backups, wildcard and uploaded certificates, site rules, application firewall, statistics and logs, antimalware, AI assistant, migration and Team. Sites, HTTPS and PHP versions are always available. Administrators and resellers always have every function.