Add the requirements of every website
When several projects share one hosting plan, list each website and the applications it runs. Add their current files, media and databases to a common storage inventory. Compare the total website count, memory requirements and expected data growth with the allowances actually published for each Cloud offer.
Use measurements from existing applications where available. Separate regular usage from heavier work such as imports, exports and maintenance. A plan’s resource figures help you compare configurations; your software and workload determine how those resources are used. WordPress projects also need an inventory of themes, plugins and compatible PHP settings.
Estimate storage across multiple projects · Review WordPress-specific hosting choices
Choose the environment as well as the capacity
Compare the initial application and options available for the offer you select. Website count and memory are only part of the decision: your project also needs a compatible runtime, database workflow and a clear maintenance owner. Record the domain and preparation preferences that belong to this order.
Cloud hosting here is a range of published configurations. If your project needs to administer an operating system, run custom server services or organise containers, review a Linux VPS instead. Establish the required level of server control before choosing a larger website-hosting plan simply because it has more resources.
Compare Cloud hosting and a Linux VPS · Explore the Linux VPS range
Prepare for growth and a controlled change
Set a review point for the measurements that matter to your applications, such as storage use or memory pressure. When requirements change, compare a new configuration with that evidence and check the complete quotation. Record the steps needed to move data and verify the destination before changing visitors’ access.
Keep recovery copies and domain-control details available throughout a change. Several projects need an organised inventory of credentials, DNS records and restoration steps. Review the selected options and the period total before paying. New services and renewals cover at least three months; payment status and service readiness are tracked separately.
Plan recovery before a hosting change · Check the domain records needed for a move