Hardware
How much RAM to self-host 10-15 containers?
How much RAM do I actually need to self-host 10-15 containers?
Short answer
How much RAM do I actually need to self-host 10-15 containers?
16GB is the comfortable real-world target for running 10-15 containers at home. You can absolutely start on 8GB, and many lightweight services barely register — but the moment you add something that carries its own database (a photo library, Nextcloud, anything with Postgres behind it), 8GB starts to feel tight. Buy 16GB if you can; it's the cheapest headroom you'll ever add.
RAM (memory) is the working space your running services occupy at once — separate from disk, which is where they're stored. Containers don't each reserve a fixed slab; they use what they need, so "how much RAM" really means "how much do all my services want at the same time," and that's driven far more by *what kind* of services than by the raw count.
- 16GBcomfortable target for 10-15 mixed containersour own always-on boxes
- 8GBfine until the first database-backed app
- Type > countwhat drives memory use (a DB app dwarfs ten dashboards)
Ask what kind of containers, not how many
The instinct is to multiply: fifteen containers must need a lot of RAM. But containers only use what their service actually wants, and the range is enormous. A DNS blocker, a reverse proxy, and a handful of dashboards are featherweight — you could run a dozen of them and barely notice. A single app that carries its own database is a different animal, because databases like to hold working data in memory. So the real question hiding inside “how much RAM for 15 containers” is “how many of those 15 are heavy,” and usually it’s only two or three.
| RAM | Comfortable with | Where it strains |
|---|---|---|
| 8GB | Many light services (DNS, dashboards, proxies) | The first database-backed app |
| 16GB | 10-15 mixed containers incl. a DB or two | Heavy media AI / multiple big DBs |
| 32GB+ | Everything above with room to spare | Rarely, at home |
16GB is the comfortable minimum I'd aim for. 8GB genuinely works — until you add anything with its own database, like Immich or Nextcloud, and then you feel it. It's the type of container that matters, not the number.
Common questions
Do more containers automatically mean more RAM?
Not really — it's the type that matters. Ten small services like Pi-hole, a reverse proxy, and a few dashboards might use very little together. One app with its own database can use more than all of them combined. Count is a poor predictor; 'does it run a database' is a much better one.
Can I really start on 8GB?
Yes, and lots of people do. A stack of lightweight containers runs happily on 8GB. You'll just meet the ceiling the first time you add a heavier, database-backed service, and the fix — more RAM — is cheap and easy on most mini PCs. Starting on 8GB and upgrading later is a perfectly reasonable path.
What actually happens if I run out?
The system starts using disk as overflow ('swap'), which is much slower, so everything feels sluggish; in a real pinch the OS may kill a container to free memory. Neither is catastrophic, but both are annoying — which is why a little headroom (16GB) is worth the small extra cost up front.