Reverse proxy: hardware requirements
Expose services with TLS — Nginx Proxy Manager, Traefik or Caddy.
Hardware tiers
| Tier | CPU | RAM | Storage | GPU | VRAM | Network |
|---|---|---|---|---|---|---|
| Minimum sensible | 1 cores | 1 GB | 0 TB (ssd) | None | — | 1 GbE |
| Recommended | 2 cores | 2 GB | 0 TB (ssd) | None | — | 1 GbE |
| Comfortable | 4 cores | 4 GB | 0 TB (ssd) | None | — | 2.5 GbE |
| Overkill | 7 cores | 7 GB | 0 TB (ssd) | None | — | 2.5 GbE |
- Minimum sensible: The smallest build that genuinely works — tight, focused, no fluff.
- Recommended: The sweet spot: handles the service plus the usual side-services.
- Comfortable: Real headroom — this service will never be the bottleneck.
- Overkill: More than you will ever use for this service alone — spend the money elsewhere.
Beyond Comfortable — 4 cores, 4 GB RAM, 0 TB: headroom you will never use for this service alone.
Needs no bulk storage — a small boot SSD is enough.
Runs well with
Router / gateway, Firewall
Frequently asked questions
How much RAM does Reverse proxy need?
1 GB is the sensible minimum, 2 GB covers most real setups, and 4 GB gives comfortable headroom.
How many CPU cores does Reverse proxy need?
1 cores are the minimum, 2 cores the sweet spot, and 4 cores comfortable when shared with other services.
Can I run several services on one machine?
Yes — most services share resources. Use the planner and select several services; the engine sums and overlaps the requirements instead of stacking them.
What if I already have hardware?
Register it in My hardware and the analysis shows exactly which services your current system can comfortably run — including an honest “do nothing”.