WordPress is an application responsibility
For an agency client, select a starting VPS only after checking the WordPress, PHP, database, theme and plugin requirements for the intended application. PrivateHostLab does not install, manage or migrate WordPress. A plan allocation is not a visitor-capacity claim or a compatibility guarantee.
Start with a real plan and the full-term budget
| Plan | Starting resources | Monthly base | 6 months paid upfront | 12 months paid upfront |
|---|---|---|---|---|
| Starter | 1 vCPU · 1 GB · 25 GB SSD · 1 TB | $5 USD | $21.60 USD | $30.00 USD |
| Studio | 2 vCPU · 2 GB · 50 GB SSD · 2 TB | $10 USD | $43.20 USD | $60.00 USD |
| Business | 4 vCPU · 4 GB · 80 GB SSD · 3 TB | $20 USD | $86.40 USD | $120.00 USD |
A conditional Studio starting point
Example planning budget: WordPress, PHP and the web process use 350 MB; the database uses 250 MB; plugin or update work is allowed 550 MB of working room; and the operating system is allowed 300 MB. That is 1.45 GB. The application storage budget is 8 GB for files and uploads, 4 GB for database and working files, and 10 GB for update or restore workspace: 22 GB. Add a separate 8 GB allowance for the operating system and its updates, for an illustrative 30 GB storage budget. These are planning assumptions, not WordPress minimums, a tested configuration or a capacity result.
Because the illustrative 1.45 GB memory budget exceeds Starter’s 1 GB allocation and the 30 GB storage budget exceeds Starter’s 25 GB SSD allocation, Studio’s 2 GB RAM and 50 GB SSD is the conditional starting choice for this example. Its base configuration costs $43.20 USD for six months or $60.00 USD for twelve months, paid upfront. If the measured site, plugins, database or update work stays within a different budget, choose the corresponding plan instead.
Before final selection, measure the actual WordPress and PHP requirements, database size, upload growth, scheduled work, cache behavior, administrator access and a separate restore rehearsal; those observations decide the final plan.
Use the table as a budget starting point, then add selected catalog options only after measuring the site’s memory, uploads, database and maintenance needs. The 6- and 12-month totals are paid upfront; domain registration, licences, network fees, agency labour and independent recovery work remain separate.
Record client, payer and domain ownership
Record who owns the client relationship, who authorizes and makes the crypto transfer, who controls the registrar and DNS, and who operates WordPress after launch. The purchase contact email is not a hosted mailbox or a substitute for those ownership records.
Keep files, database and configuration together
A usable WordPress recovery discussion includes application files, uploads, database and configuration. Rehearse a restore in a separate target where appropriate, and decide who can approve a rollback after an accountable update. Staging must prevent unintended production email and payment effects before any test.
Read the WordPress backup checklist, staging-effects guide and failed-update recovery guide. WordPress’s requirements documentation is the primary reference for the application prerequisites; it does not establish PrivateHostLab service capabilities.
Illustrative agency planning path. Validate actual application requirements and the agreed operating responsibilities before selecting a configuration.