Define a hosting package
As an authorised administrator, open Packages and choose New package. Set the supported storage, memory, process and service allowances, review them and submit. The API must accept the package before it becomes available for an account.
The forms describe memory in MB using MiB, and GB using GiB. Check the saved exact allowances; zero, inheritance and unlimited values have distinct meanings. A package definition does not itself create a Linux account or prove kernel resource enforcement.
Create one test account
Open Accounts → Create hosting account. Choose the accepted package and supply the requested customer identity, contact details and initial password. Capabilities determine which fields are supported; a primary-domain reservation does not automatically create a website or DNS zone.
Review the request and explicitly submit. Record the returned operation reference and follow its real progress. Do not interpret a saved form or metadata row as proof of provisioned hosting.
Check the result
Test access as that Customer, verify ownership and the intended allowances, and compare expected versus observed service state. Account creation depends on current administrator permission/freshness, the licence boundary, agent availability and supported quotas.
Suspension, reactivation and termination are separate actions. Termination requires its current impact/recovery safeguards; do not remove backup requirements or bypass a hold to make an evaluation succeed.