Simple answer
For a normal self-hosted setup, start at 4GB if you can. It is the smallest tier that usually leaves enough room for a web service, a reverse proxy, logs, and the next thing you will add later.
RAM tiers
- 2GB: testing, experiments, low tolerance for mistakes
- 4GB: best default for small but real deployments
- 8GB: safer once Docker stacks or automation get involved
Practical note
People often blame CPU because it feels technical. In small self-hosting, RAM pain usually shows up first.
Common sizing mistakes
- Budgeting only for today’s container list
- Ignoring memory used by the OS and monitoring
- Treating “it booted” as proof that it is sized correctly
What to read next
If you are choosing a host, pair this with the VPS sizing guide. If you already have a server, the next good step is the hardening checklist.
Frequently asked questions
Is 2GB enough for self-hosting?
It is enough for experiments, but 4GB is a more realistic baseline for a durable small self-hosted setup.
Why does RAM matter so much?
Because logs, background services, reverse proxies, databases, and containers all consume memory even when the server looks idle.
When should I move to 8GB?
Move up when you are running multiple services, using Docker heavily, or already seeing swap and operational drag.
Next practical step.
Use this page as a decision shortcut, then move into the related implementation guide or checklist instead of stopping at theory.