Create a hosting package template
Define the resources, applications, mailboxes, domains, backups and technical features offered to a customer.
Where Settings โ Packages โ Add package
What this is for
- Create a named customer-facing package.
- Set finite or unlimited resource allowances.
- Control which tools customers may use.
Before you start
- Agree the commercial limits and customer features before entering them in Enhance.
- Decide which values are finite, unlimited or deliberately disabled with zero.
Take care
Package changes affect customer capability and capacity. Keep descriptions, commercial promises and technical limits aligned.
Steps
-
1
Choose a clear customer-facing package name.
-
2
Set website, staging, disk, page-view, bandwidth, database and FTP allowances; use zero only to disable a resource intentionally.
-
3
Choose which applications customers may install and whether WordPress components are pre-installed.
-
4
Set mailbox, forwarder, addon-domain, subdomain and alias limits.
-
5
Choose backup visibility, manual backup and self-restore permissions.
-
6
Review SSL, SSH, cloning, php.ini, supported PHP versions and Redis access.
-
7
Add the package, then subscribe a neutral test customer and verify the effective limits.
Check it worked
- The package list shows the new package with the intended allowances.
- A subscribed demo customer sees only the resources, PHP versions and tools promised by that package.
What the controls do
| Control | What it means |
|---|---|
| Finite / Unlimited | Applies a numeric allowance or removes the configured limit. |
| Allowed applications | Controls which current and future installers customers can run. |
| Default PHP version | The initial runtime used by new websites on the package. |
| Customer feature switches | Show or hide sensitive tools such as SSH, SSL installation and php.ini. |