Baseline sizing
For simple self-hosting, the real constraint is usually memory, not CPU. A tiny plan can boot, but that does not mean it stays pleasant once you add Docker, monitoring, backups, or browser-adjacent tooling.
| Plan class | Best for | Recommendation |
|---|---|---|
| 1 vCPU / 2GB | Tests and throwaway experiments | Only if cost matters more than comfort |
| 2 vCPU / 4GB | Most practical self-hosted setups | Best default |
| 4 vCPU / 8GB | Heavier automation or multiple services | Upgrade when you know why |
When to upgrade
- Your box swaps under moderate load
- Background jobs slow down interactive work
- You are delaying features because the server feels fragile
Rule of thumb
If you are already asking whether 2GB is enough for your “real” setup, it probably is not the plan you want to commit to.
Practical profiles
A content site with occasional automation can stay lean. A VPS running OpenClaw, reverse proxy, logs, backups, and experiments should start one step above “minimal” so it remains boring to operate.
Common mistakes
- Buying the cheapest plan and then optimizing around pain
- Ignoring backup and storage growth
- Treating bursty CPU as the only metric that matters
Keep the next step obvious.
The point of this archive is not to impress you with complexity. It is to help you pick the right hosting path, with fewer avoidable mistakes.