Create a package
Open Hosting Packages → Create Package with hosting:manage. Enter a recognisable name, resource values and permitted tools, review the summary and submit once. The source posts to POST /v1/packages; package values are maximum limits, with guarantee_cpu, guarantee_memory and guarantee_io false. A cap is not a reserved capacity promise.
Resource field reference
| Field | Meaning and verification |
|---|---|
storage_bytes |
Hard byte quota for the registered account UID on the protected private/public ext4 filesystem. |
storage_inodes |
Hard file-count quota on that same supported filesystem. |
website_limit, database_limit, mailbox_limit |
Maximum reserved/managed resource counts; service capability is checked separately. |
transfer_limit |
Additional scoped transfer users; zero permits none. |
bandwidth_allowance_bytes |
Policy allowance; complete network transfer enforcement is not provided by filesystem or HTTP-log counters. |
cpu_quota_percent |
CPU bandwidth maximum; not a guaranteed core allocation. |
memory_max_bytes |
Memory maximum, effective only when the cgroup controller verifies it. |
memory_swap_max_bytes |
Swap cap; zero means no swap when a memory maximum is set. |
tasks_max |
Process/task maximum verified by the account slice. |
io_read_bytes_per_sec, io_write_bytes_per_sec |
I/O caps requiring a supported device and controller. |
The interface presents memory inputs in MB with conversion guidance. Empty optional CPU/memory/process/I/O package fields normalize to no package cap; do not interpret a blank or missing observation as an enforced zero.
Available tools and overrides
The exact feature vocabulary is websites, files, databases, email, dns, backups, applications, scheduled_tasks and transfers. Selecting a feature authorizes eligible new resources and Customer configuration; it does not install its service. Existing recovery/download/manual-backup policy is separate. Account creation and package changes can apply deliberate resource and feature overrides; inspect the resulting effective account values.
Read enforcement and usage correctly
Account detail separates configured, effective and observed values. Active cgroups require live_verified; a suspended slice can report configured_stopped and is not presented as live enforcement. Storage coverage excludes mail/database storage or separate transfer UIDs on other ownership/filesystems. Project counters are untrusted diagnostics. Review the observation time; a historical read-back is not continuous health.
Remove and retain history
Removal requires the installed versioned catalogue capability and a current package revision. Active accounts or pending operations block it. Unused records can be deleted; referenced history is retired and cannot be chosen for new accounts. Show archived package history appears only when supported. Batch removal reviews at most 25 selected packages and stops on permission or uncertain-delivery failure; check each result. Removing a package does not terminate accounts or data. Existing-package editing and standalone named feature-list editors are not implemented in this interface.