Choose your Web Hosting package by matching the applications, websites and email you need to the account's capacity. Always check the current order details for the package you select, including its website allowance and other resource limits.
IN THIS ARTICLE
01 Account for the complete workload
Storage is only one part of the decision. A site with a large image library needs space, while a smaller application with complex database queries can need more processing resources. Email stored in the hosting account also needs to be included in your planning. If several websites share one account, their combined activity matters; giving each website a different domain does not create a separate pool of hosting resources.
Make a short requirements list before ordering.
- The number of websites that will share the account.
- The approximate size of your website files and databases.
- Your mailbox requirements, including the email stored in the hosting account.
- The traffic patterns you expect.
- The required PHP environment and any background jobs.
If your application requires Node.js, Python, Ruby or another specific runtime, confirm that the exact environment is available for your intended package.
An application being downloadable on the internet does not establish that it can run within shared hosting restrictions.
02 Assess growth and the hosting environment
For an existing project, share its current resource measurements and any recurring errors with us. That helps distinguish a need for a larger package from a configuration or application problem. Start with sufficient room for normal growth and monitor real usage after launch. If your project eventually requires server-level administration or services that are outside the shared hosting environment, ask us to assess a more suitable service before committing to that architecture.
03 Example: build a workload inventory before choosing a plan
A business is moving one website and four existing mailboxes. Its current usage is approximately 2 GB of website files, 300 MB of databases and 4 GB of stored mail. These are sample workload figures, not a Nabtech package allowance.
- Add the website, database and mail requirements to the inventory.
- Include the space needed for retained backups and normal growth.
- Record the required PHP version, extensions and scheduled tasks.
- Compare those requirements with the actual selected package, including website count and resource limits.
- Share any recent CPU or memory-limit evidence when requesting a recommendation.
Expected result: the package is assessed against the complete workload. Four mailboxes and several websites sharing one account still consume that account's resources rather than receiving independent allocations.
How do I turn my website requirements into a hosting-plan choice?
- Record the present size of files, databases, mail and retained backups. Allow room for normal growth and maintenance operations.
- Identify periods when visitors experience slow requests and compare them with resource information. Traffic counts alone do not identify the limiting resource.
- Confirm the necessary language runtime, email features, access tools and upgrade route before completing the order.
A plan described as unlimited still operates within its service conditions and technical limits. For a downgrade, check the destination limits before requesting the change; reducing a billing package does not automatically remove excess files, mail or websites safely.