Back to Blog

Private Cloud vs Public Cloud: When to Self-Host and When Not To

Understand when self-hosting makes sense and when public cloud is better. A practical guide to choosing between private cloud homelab and AWS/GCP/Azure services.

Posted by

Private cloud vs public cloud comparison

Not Everything Should Be Self-Hosted

Self-hosting evangelists sometimes go too far. While a private cloud offers privacy and cost savings, some services are better left to public cloud providers. Let's be practical about when to self-host.

Self-Host These (Private Cloud Wins)

  • File Storage: Nextcloud beats Dropbox on cost at scale
  • Password Manager: Vaultwarden - your passwords, your server
  • Media Server: Jellyfin/Plex - no subscription, unlimited storage
  • Photos: Immich - privacy for family memories
  • DNS/Ad-blocking: Pi-hole - network-wide, always works
  • Home Automation: Home Assistant - local, fast, private

Don't Self-Host These (Public Cloud Wins)

  • Email: Deliverability is a nightmare - use Fastmail/Proton
  • Video Conferencing: Jitsi works but Zoom/Meet are more reliable
  • Production Databases: Use managed services for critical apps
  • Global CDN: Cloudflare - can't compete with their network
  • SMS/Push Notifications: Twilio, Firebase - infrastructure you can't replicate

The Decision Framework

Ask yourself:

  • Is this data sensitive? → Self-host
  • Do I need 99.99% uptime? → Public cloud
  • Am I the only user? → Self-host
  • Do I need global distribution? → Public cloud
  • Is the subscription cost high? → Self-host
  • Is the service complex to maintain? → Public cloud

The Hybrid Approach

Most homelabbers end up with a hybrid setup: sensitive data on private cloud, critical infrastructure on public cloud, and everything connected through a VPN. This gives you the best of both worlds.

Continue Reading