Docs

Packages and Feature Lists

How to add, edit and delete packages, what each package limit means, and how Feature Lists decide which parts of the client area an account gets.

8 min read Updated From the panel's guide

A package is a named set of limits and features, such as "Starter" or "Business". Every account on a package follows it, and changing the package changes all those accounts at once. An account without a package has no limits. This page covers the admin menu section Packages: Add a Package, Edit a Package, Delete a Package and Feature Lists. To put an account on a package, see Hosting Accounts.

The Package List#

In the admin area, open Packages → Edit a Package or Packages → Delete a Package (Packages). Both open the list of packages. For each package it shows:

  • disk space, websites, databases, FTP logins, mailboxes, mail forwarding and monthly data transfer;
  • Left out, the parts of the client area the package leaves out;
  • Accounts, how many accounts use it.

Each row has an Edit and a Delete button. Add a Package above the list opens an empty form.

Under the list, the page tells you how disk limits are enforced:

  • With user quotas: when quotas are switched on for the filesystem that holds /home, the filesystem itself enforces the disk limit.
  • Without quotas: only the panel enforces it. An account over its limit cannot upload or create anything through the panel, but FTP uploads, incoming mail and files written by websites are not stopped. To have the filesystem enforce the limit, mount the filesystem holding /home with the usrquota option, or use Disk Quota Setup.

Good to know:

  • A server can have up to 200 packages.
  • Packages a reseller makes for itself are named reseller_name and appear in this list too.

Add a Package#

In the admin area, open Packages → Add a Package (Add a Package).

  1. Enter a Name: 1 to 32 letters, digits, spaces, dots, - or _. Saving under the name of an existing package changes that package.
  2. Fill in the limits (see "Package Limits" and "Resource Limits in a Package"). Empty or 0 means no limit.
  3. Under Settings, tick Dedicated IP and Shell access if accounts on this package should have them.
  4. Choose a Feature list, and untick any parts of the client area the package should leave out (see "Features in a Package").
  5. Click Add.

The package is then offered when you create an account, change an account's package, or set up a reseller.

To make a package the one chosen in advance on the New Account page, set it as the default package under Server Preferences.

Good to know:

  • When you create an account with Set the Limits by Hand, or save the Resource limits of this account form on an account page, a package named after the account (such as username_custom) is made for it. You can edit it here like any other package.

Edit a Package#

In the admin area, open Packages → Edit a Package (Packages) and click Edit next to the package. The form shows the package's current values.

  1. Change the limits, settings or features.
  2. Click Save Changes.

The change applies at once to every account on the package. For each of them, the panel:

  • sets the disk quota;
  • applies the processor, memory, disk and process limits and the database limits;
  • gives or takes away shell access;
  • hides or shows the parts of the client area the package leaves out;
  • updates the outgoing mail limits.

The package name cannot be changed. To rename a package, add a new package with the new name, move the accounts to it, and delete the old one.

Good to know:

  • Lowering a limit does not remove anything. An account that already has more databases, mailboxes or websites than the new limit keeps them, but cannot add more until it is under the limit.
  • Exceptions set for one account with Disk Limits per Account, Data Transfer Limits or SSH Shell Access still apply on top of the package.

Delete a Package#

In the admin area, open Packages → Delete a Package (Packages) and click Delete next to the package.

A package can only be deleted when no account uses it. While accounts use it, the Delete button is disabled. To free the package:

  1. Find its accounts in All Accounts: choose Look In: Package, type the package name and click Find.
  2. Tick them, choose another package under the table and click Change package.
  3. Delete the package.

Good to know:

  • Deleting a package does not change any account, because none is on it.
  • A reseller that was allowed the package can no longer choose it.
  • The feature list the package used is not deleted with it.

Package Limits#

These limits are on the Add a Package form. For all of them, empty or 0 means no limit.

  • Disk space (MB): the most the account's files may use (see "The Package List" for how this is enforced).
  • Websites: the main domain, additional domains and subdomains counted together.
  • Databases and FTP logins.
  • Mailboxes and Mail Forwarding (the number of forwarders).
  • Data transfer per month (MB): when an account goes over it, its websites are switched off until the next month.
  • Subdomains allowed, Domain aliases allowed and Additional domains allowed: each limited on its own. -1 means none are allowed.
  • Messages each domain may send per hour: counts the messages each domain's mailboxes send, and separately those the account's websites and scheduled tasks send.
  • Largest size of one mailbox (MB): the most one mailbox may hold.
  • Mailing lists allowed: -1 means none are allowed.

Under Settings:

  • Dedicated IP: gives each account on the package a free IP address of the server for itself, if there is one. If there is no free address, the account stays on the shared address.
  • Shell access: gives the account's system user a login shell. It signs in over SSH with a key in .ssh/authorized_keys, never a password.

Resource Limits in a Package#

The Resource limits part of the Add a Package form limits everything that runs as the account: its PHP, its scheduled tasks and its shell. For all of these, empty or 0 means no limit.

  • Processor (% of one core): 100 is one full core and 200 is two cores. The value must be from 5 to 12800.
  • Memory (MB): at least 64 MB.
  • Disk reads and writes (MB per second).
  • Number of processes: at least 10.
  • Database connections at once, per database user.
  • Database queries per hour, per database user.

The limits apply to the account as a whole. A website that reaches the processor or disk limit is slowed down, not stopped. When an account reaches its memory or process limit, new processes or requests can fail until usage drops.

To see what accounts actually use, open Resource Usage. It shows each account's processor, memory, disk and process use, with a history per account.

Good to know:

  • Set these limits generously at first and lower them after watching the usage. Limits that are too tight make websites slow or show errors at busy times.
  • Whatever runs as the account's system user is put into the account's own control group within a couple of seconds, so one busy website slows down itself, not the server.

Features in a Package#

At the end of the Add a Package form, Feature list: included in the client area lists the parts of the client area. Untick a part to leave it out of every account on the package. The parts are:

  • Domains and subdomains
  • DNS zones
  • Website settings (redirects, aliases, PHP settings ...)
  • WordPress manager
  • File manager
  • Email
  • FTP accounts
  • Backups
  • Databases and phpMyAdmin
  • PHP version
  • SSL/TLS
  • Scheduled tasks
  • Web Applications (Node.js, Python, Ruby)
  • Visitors and logs
  • Virus scanner

A part that is left out is hidden from the client's menu, and its pages are refused.

The Feature list menu above the boxes lets the package use a named list from Feature Lists. An account then gets only what both the boxes and the list include: a part left out by either is left out. Choose None (only the boxes below) to use the boxes alone.

Good to know:

  • The special list disabled applies to every account on the server, whatever its package says.
  • The Left out column in the package list shows only what the package's own boxes leave out, not what its feature list adds.

Feature Lists#

In the admin area, open Packages → Feature Lists (Feature Lists). A feature list says which parts of the client area an account gets. You make a list once and choose it in several packages, instead of unticking the same boxes in each package.

To make a list:

  1. Under New feature list, enter a name (up to 32 characters), for example Starter.
  2. Untick the parts the list should leave out.
  3. Click Create the list.

Each existing list is shown below with its boxes, and the packages that use it. Change the boxes and click Save to update every account on those packages. Click Delete to remove a list. A list that a package still uses cannot be deleted: choose another list for that package first.

To use a list, edit a package under Packages, choose the list under Feature list and click Save Changes.

The disabled list: this list is always shown and cannot be deleted. What you untick in it is switched off for every account on the server, whatever its package and feature list say. Use it for a part of the client area you do not offer at all.

Good to know:

  • A server can have up to 50 feature lists.
  • Changes take effect at once. A client who has the page open sees the change on its next click.
Was this article helpful?

Something missing? Ask in the community or open a ticket.