Skip to Content
Browse documentation

Add a Reseller Hosting Package

Define all reseller package resource, feature, email and optional CloudLinux fields with validation and inheritance rules.

Open Hosting → Packages → Add Package.

Required package fields

FieldRequirement
Package NameUnique name, maximum 200 characters; letters, digits, underscores, hyphens and periods, without leading/trailing punctuation. Follow the visible name validation.
Disk quota / bandwidthNumeric allowance or Unlimited, in MB.
FTP / email / mailing lists / SQL databasesNumeric count or Unlimited for each.
Quota per email addressNumeric MB allowance or Unlimited.
Subdomains / parked domains / addon domainsNumeric count or Unlimited for each.
Feature listRequired available feature definition.

The name must not collide with an existing package definition, including another owner's name. The saved owner is your reseller. The form forces dedicated-IP and shell flags to no; do not infer these can be enabled by this package editor.

Sending limits

Outgoing recipients per domain per hour accepts a positive whole-number custom limit. Maximum failed/deferred delivery percentage accepts 1–100. Both offer Unlimited / Inherit, which leaves policy inherited rather than bypassing the server ceiling. Invalid modes, missing custom values, excessive limits or an unreadable global policy block validation.

Conditional CloudLinux controls

When available, select Enable LVE and Default or Custom values for CPU speed, RAM, VMEM, entry processes, process count, disk I/O, IOPS, inode soft/hard limits, MySQL CPU and MySQL I/O. Use the displayed units: CPU 100% represents one core, memory is MB, and inode limits are counts. CageFS offers Enabled/Disabled separately and can remain configured even when LVE limits are off.

Custom values must be numeric; use Default rather than leaving an explicitly submitted LVE limit blank. CPU cannot exceed detected cores × 100%, RAM/VMEM cannot exceed detected RAM, and a numeric inode soft limit cannot exceed a positive numeric hard limit.

Save and verify

Review the entire definition and submit the creation control, following any confirmation. Inspect validation/I/O messages and reload the package list to verify its limits and feature assignment. A saved package does not itself provision a customer account.

Review the offered capacity

Do not promise unlimited physical resources because a package field says Unlimited. Plan customer usage against reseller/server capacity and verify how inherited mail and CloudLinux policy apply. The add view has no explicit demo guard.