A plan is more than a number.
Comparison notes, not a hosting service or a promise of uptime. Verify current product limits with the provider you choose.
| Approach | Useful for | What you still own |
|---|---|---|
| Static hosting | Documentation, portfolios, guides | Content, domain, access to publishing |
| Managed application | A small web application | Application updates, secrets, data recovery |
| Virtual server | A project needing system control | Operating system, network policy, all services |
Separate publishing from administration
A content change should not need unrestricted server access. Keep deployment credentials scoped to their job and remove unused access.
Know the recovery path
Write down where the files and data live, how a backup is made and how long a restore takes. A backup that has never been restored is an assumption.
Measure the real workload
Traffic and storage estimates help choose a starting point. They do not predict peak concurrency, CPU demand or database latency. Test the actual application before relying on a capacity claim.