A Ryzen 5 5600G is genuinely enough to run a modern homelab for the first year — Docker with 10-15 containers, a Proxmox host with 3-4 VMs, or a bare-metal Ubuntu box with Jellyfin, Home Assistant, Nextcloud, and a Pi-hole all humming along on its 6 cores and 12 threads. Where it starts to fall short is when you add machine-learning services (Ollama, Immich face recognition, Frigate NVR) or when you scale past 5-6 heavy VMs. This piece walks through a first-month homelab build with a 5600G at its core, real resource-use data, and where you'll want the upgrade path to go.
The setup: what a first-month homelab actually looks like
Roughly one month in, the r/homelab weekly threads show a common starter shape:
- CPU: Ryzen 5 5600G — chosen for integrated Radeon graphics (no discrete GPU needed for boot/console) and low idle power (~12W package).
- RAM: 32GB DDR4-3200 in dual-channel.
- Storage: 1x NVMe boot drive for OS + hot data, 1x 1TB SATA SSD for containers, plus one or two spinning-rust drives (2-4TB WD Red or Seagate IronWolf) for media.
- Motherboard: B550 or A520 mATX — modest, one M.2 slot, one PCIe x16, four SATA ports.
- Case: Fractal Node 304 or Silverstone DS380 — small-form-factor with 8 drive bays.
- Software: Proxmox VE 8 on the metal, or Ubuntu Server 24.04 with Docker + Portainer.
Total build cost with used-part sourcing: $650-800.
Key takeaways
- A 5600G comfortably runs 10-15 containers or 3-4 VMs on 32GB RAM. That's already a legitimate homelab.
- The 5600G's Vega 7 iGPU is enough for a boot display but not for Jellyfin/Plex GPU transcoding. That's the first place the ceiling shows.
- Idle power sits at 25-35W for the whole system, roughly $30-45/year at $0.13/kWh — genuinely affordable to leave on 24/7.
- The real upgrade path is more RAM before more CPU. DDR4-3200 in 4x16GB or 2x32GB opens up 4-6 more VMs without changing the CPU.
- The 5600G's ceiling shows up on ML workloads. Adding Ollama, Immich, or Frigate pushes you toward a discrete GPU or a stronger CPU with more cores.
Real-world resource usage: a typical month-one loadout
Below is a common stack from active r/homelab first-month posts, with observed baseline resource use on a 5600G + 32GB rig. Numbers are steady-state after warm-up.
| Service | CPU (avg) | RAM | Notes |
|---|---|---|---|
| Proxmox host | ~2% | ~2GB | Baseline hypervisor overhead |
| Ubuntu VM (Docker host) | ~1% | ~1.5GB | Idle guest OS |
| Jellyfin (2 streams, direct play) | ~5% | ~800MB | GPU transcode disabled |
| Home Assistant + Node-RED | ~3% | ~1.2GB | 15-20 integrations |
| Nextcloud + PostgreSQL | ~2% | ~800MB | Personal sync, ~10GB storage |
| Pi-hole + Unbound | ~1% | ~200MB | 50k queries/day |
| Portainer + Watchtower | <1% | ~150MB | Container management |
| AdGuard Home (alt to Pi-hole) | ~1% | ~200MB | If chosen instead of Pi-hole |
| Grafana + Prometheus + Loki | ~4% | ~1.5GB | System monitoring |
| Uptime Kuma | <1% | ~150MB | Service health checks |
| Total steady-state | ~20% | ~9GB | Plenty of headroom |
That's 10 running services on a 5600G with ~80% CPU headroom and 23GB RAM headroom. Solidly within budget.
Where the 5600G starts to strain
Add these to the same rig and the picture changes:
| Service | CPU spike | RAM | Notes |
|---|---|---|---|
| Immich (photo library + ML) | 60-80% (during scan) | 4-6GB | Face recognition is CPU-heavy without GPU |
| Frigate (2-4 cameras) | 40-70% | 2-4GB | Needs Coral TPU or GPU for real perf |
| Ollama (Llama 3.1 8B Q4) | 100% (single query) | 8GB | CPU inference at ~5 tok/s — usable but slow |
| Nextcloud AI + Recognize | 30-60% | 3GB | ML-heavy backend jobs |
| Whisper transcription | 100% (during job) | 4GB | CPU-only transcription is slow |
Any two of these together and you're pinning the CPU during peak. That's the point where a 5600G stops feeling comfortable.
The RAM lever vs the CPU lever
The first upgrade a first-month homelabber typically makes isn't a CPU swap — it's more RAM. The 5600G supports up to 128GB DDR4 (4x32GB DIMMs on most B550 boards), and going from 32GB to 64GB or 96GB unlocks 4-6 more VMs without touching anything else.
Jumping to 64GB with two G.SKILL RipJaws V 32GB kits or an A-Tech 2x32GB kit costs ~$120-140 in 2026 and buys you dramatically more capacity for concurrent VMs than the CPU upgrade would.
The CPU-upgrade path — 5600G → Ryzen 7 5800X or 5700X — adds 2 more cores but costs $200+ and requires losing the iGPU. If your rig has a discrete GPU already (or you're happy with headless), the 5800X is the right upgrade. If not, add RAM first.
What the 5600G actually fails at
Three specific workloads where a 5600G isn't enough:
- GPU-accelerated video transcoding. Vega 7 has hardware H.264/HEVC decode but limited encode. Jellyfin/Plex will fall back to software transcode, pegging the CPU. If you have multiple simultaneous remote streams that need transcoding, you want a discrete GPU (any RTX 3060 or Intel Arc A310 works) or a switch to a CPU with Intel Quick Sync (i5-12400 class).
- Serious ML workloads. Ollama at ~5 tok/s on CPU is usable for occasional questions but not for daily use. A Raspberry Pi 4 or Mini PC like the GEEKOM A6 sitting alongside for lightweight edge inference is a common workaround.
- Multiple concurrent VMs each running services. Once you're at 6+ VMs, the 12 threads on a 5600G start to matter. Move to a 5700X (8C/16T) or 5900X (12C/24T) to open that ceiling.
Common month-one homelab mistakes with a 5600G
- Undersizing RAM. 16GB is not enough for anything beyond 2-3 containers plus a media server. Start at 32GB; plan for 64GB.
- Buying enterprise storage before consumer NVMe. A $50 Crucial BX500 SATA SSD is 10x cheaper than a used enterprise SAS drive and does the job for container mount points.
- Trying to run Windows VMs. Windows Server 2022 in a VM eats a full core for background tasks. If you can, keep everything on Linux; use LXC containers over full VMs when possible.
- Ignoring backups. A month-one homelab isn't a homelab if the data isn't backed up. Add rclone + a cheap cloud tier or a second box in another room.
- Buying a GPU "for future ML." If you don't need it today, hold off. The GPU market and inference stack are moving fast; whatever you buy today will be surpassed at the same price in 12 months.
Alternative: skip the 5600G, buy a mini PC
If DIY-assembly appeal is low, a GEEKOM A6 Mini PC with Ryzen 7 6800H at ~$550 delivers 8 cores (vs 6), 16GB DDR5 (upgradeable to 64GB), integrated Radeon 680M (stronger than Vega 7), and roughly 30% higher single-thread perf than the 5600G. It's a legitimate all-in-one homelab node.
The tradeoff: less upgrade headroom. No spare PCIe slot for a discrete GPU, fewer SATA ports for spinning drives, and the mini-PC form factor limits future storage expansion.
For a first homelab where you value quiet, low power, and no assembly, the mini-PC route is legitimate. For a homelab where the joy is in the tinkering, the DIY 5600G build is the answer.
The 6-month checkpoint
If your homelab is running well at month one on a 5600G, six months in you'll typically want one of three things:
- More RAM — cheapest, most impactful upgrade.
- A discrete GPU — for transcoding or ML.
- A second node — cluster your first, get high-availability, learn Kubernetes.
None of these require replacing the 5600G. It scales sideways surprisingly well.
When NOT to start with a 5600G
- You want ML from day one. Skip straight to a Ryzen 7 or 9 with an RTX 3060 12GB in the same case.
- You need high-throughput file storage. The 5600G is fine for CPU-side; ZFS with 20+ drives asks more of the motherboard than the CPU.
- You want ECC RAM. The 5600G supports it but not all B550 boards do; verify carefully.
Networking gear pairing (often the actual bottleneck)
The single most common month-two mistake on a fresh homelab is realizing the network is the constraint, not the box. A 5600G rig on a $30 unmanaged Netgear switch and a stock ISP router will run into throughput and reliability walls that make the CPU look bad.
Suggested networking upgrades in priority order:
- A managed gigabit switch — TP-Link TL-SG108E or Netgear GS308E ($30-40) — gives you VLANs, port mirroring, and traffic monitoring. Absolutely worth it once you have 3+ services on the box.
- A router capable of static routes and DNS overrides — replace the ISP router or run OPNsense/pfSense on a spare mini PC.
- A separate wifi AP — a Unifi U6-Lite or TP-Link EAP245 ($90-120) beats a consumer wifi router for reliability if you host Wi-Fi-sensitive services like Home Assistant.
- A UPS — CyberPower CP1500PFCLCD ($150-180) — protects your homelab from ISP-side surges and gives clean shutdown on a power blip. This one alone has saved more first-month homelabs than any other single upgrade.
Backup strategy for month one
Every homelab is one power spike or one wrong rm -rf away from starting over. A working month-one backup plan looks like:
- Daily automated Proxmox/VM snapshots to a second internal drive (the Crucial BX500 works well for this).
- Weekly rsync/rclone to cloud — Backblaze B2 or Storj for encrypted off-site backups (~$5-10/month for 500GB).
- Monthly restore drill — actually verify you can restore a snapshot. Backups nobody has tested are hopes, not backups.
- Docker Compose files in git — the actual service config lives in git (private repo), not just on disk.
- A written recovery playbook — a text file describing how to rebuild the whole homelab from scratch. Update it every time you change something material.
The whole scheme is roughly $8/month recurring plus one Saturday afternoon of setup. Cheap insurance.
Bottom line
A Ryzen 5 5600G with 32GB RAM, a boot NVMe, and a SATA SSD is a legitimate month-one homelab. It handles the core services (Jellyfin, Home Assistant, Nextcloud, monitoring stack) with headroom to spare. The ceiling shows up on GPU-accelerated transcoding and ML workloads — plan those upgrades for month 3-6 if they become priorities. For the majority of first-time homelabbers, six cores and twelve threads is enough for the first year.
What most first-month homelab plans miss
Three underappreciated pieces of first-month planning:
- Cable labeling. Every cable — power, SATA, USB, network — should have a printed label at both ends. Fifteen minutes with a label printer saves hours during any future rebuild.
- Photo the build. Take clear photos of every internal cable route and screw location during assembly. If a component fails in six months and you need to swap it, the photos will remind you what went where.
- A separate admin machine. If your only machine is the homelab and something breaks, you can't SSH in from itself. Even a $20 used ThinkPad running Debian is fine as a fallback admin box.
None of these are exciting, but they're the difference between "my homelab is a hobby" and "my homelab is a job." First-month builders who skip them almost always regret it inside a year.
Related guides
- How Many CPU Cores Does a Local-LLM Rig Actually Need?
- Raspberry Pi 4 vs Pi 5 Homelab (2026)
- Raspberry Pi 4 NVMe Jellyfin Homelab
- Silent Pi 4 NVMe Homelab Cooling
Citations and sources
- AMD — Ryzen 5 5600G product page
- Proxmox — VE administration guide
- Jellyfin — hardware acceleration docs
This piece is editorial synthesis based on publicly available information. No independent first-party benchmarking is reported.
