What my server does

Why not just use Google Drive?

The architecture — how it all connects

Two paths, two purposes

The hardware — it's probably on your shelf

The software stack — everything is free

The cost comparison

Google One 2TB

Home server

Is it reliable?

What's coming in this series I was paying ₹650/month for Google One's 2TB plan. That's ₹6,500 a year — for storage I don't own, on servers I don't control, where my photos could be used to train AI models. Then I looked at the old HP Pavilion x360 collecting dust on my shelf. 1TB hard drive. 8GB RAM. A perfectly good Intel i5 processor doing absolutely nothing. What if I could turn it into my own cloud? Turns out, you can. And the only fixed cost is a domain name — about ₹70/month. Everything else is free, open-source software. Electricity varies by device and local rates, but a laptop sips power compared to a desktop. This is Part 1 of a 5-part series where I'll walk you through the entire setup. In this post, I'll cover the why and the what. The how starts in Part 2. My home server replaces Google Drive, Google Photos, and then some: No monthly storage fees. No upload limits. No one scanning my files. Just my data, on my hardware, under my control. Let me be specific about the problem: Cost compounds. Google One 2TB costs ₹6,500/year today. Over 5 years, that's ₹32,500 — and Google has a history of raising prices. My server's hardware was already paid for. The domain costs ₹850/year. That's it. Storage is capped. Hit 2TB on Google and you're paying ₹16,250/year for 5TB. With my server, I plug in a ₹5,000 external hard drive and I have 5TB. Once. No recurring cost. You don't own the data. Google can change terms of service, lock your account, or discontinue a product (remember Google+, Inbox, Stadia?). My files live on a hard drive in my house. Privacy. Google Photos uses your images for AI model training. Your documents pass through their servers. With a home server, your data never leaves your network unless you explicitly share it. This is the part that took the most thinking. Here's the challenge: most Indian ISPs (Airtel, Jio, ACT) use CGNAT, which means your home doesn't have a public IP address. Nobody on the internet can reach your server directly. I solved this with a two-path architecture: Public path — for when I share a photo album with family. Traffic goes: Internet → Cloudflare → Oracle VPS → encrypted frp tunnel → my home server. This gives me a clean URL (files.yourdomain.com) that anyone can open in a browser. My real home IP is completely hidden behind the VPS. Private path — for my personal use. Tailscale creates a direct WireGuard VPN tunnel between my devices and my server. No middleman. No bandwidth limits. Military-grade encryption. I use this for streaming large videos, syncing files, and SSH access. It's free for up to 100 devices. Why two paths? The public path exists only for sharing. Tailscale is faster and more secure, but it requires the app to be installed on every device. Family members who just want to see wedding photos shouldn't need to install a VPN. You don't need fancy hardware. Any old laptop or mini PC works. A laptop is actually ideal because: Here's what I'm running: A Raspberry Pi 4/5 also works for lighter usage, though I'd recommend a proper laptop or mini PC if you plan to serve media files. This blew my mind when I first set it up. Every single piece of software is open source and free: Not a single subscription. Not a single license fee. The open-source community has built everything you need. Here's why this project was worth a weekend of setup: The hardware? Already paid for — it was gathering dust. Even if you bought a used laptop for ₹10,000, it pays for itself in under 2 years compared to Google One. I've been running this setup for a while now. Here's what I've observed: Uptime is excellent. The server boots automatically after power cuts (BIOS setting), and all services — Docker, Nextcloud, Tailscale, frp — start on their own. After a power outage, everything is back online in 2-3 minutes without me touching anything. WiFi has been the weak link. I've had occasional drops on the WiFi connection. If your server is near the router, use an Ethernet cable. It's noticeably more reliable. Speed is great on the local network. Transferring files via Samba on my home network is as fast as a USB drive. Remote access via Tailscale is limited by your internet upload speed, but perfectly usable for photos and documents. Maintenance is minimal. I check on it maybe once a week — glance at disk space, make sure services are running. Docker makes updates trivial: pull the latest image and restart. This was the why and the what. Starting next, we get into the how — complete, copy-paste-ready tutorials: 📦 Part 2: Setting up Nextcloud with Docker — Install Docker, write the compose file, configure Nextcloud, set up phone auto-backup, and get desktop sync working. Your Google Drive replacement, running in 30 minutes. 📂 Part 3: Turn your server into a NAS with Samba — Configure Samba shares, connect from Mac and Windows, set up auto-mount on startup, and integrate with Nextcloud so both see the same files. 🌐 Part 4: Access your server from anywhere — Set up Tailscale for private access, get an Oracle free VPS, configure frp tunneling, set up Nginx and SSL, and point your custom domain to your home server. 🔒 Part 5: Security hardening + lessons learned — Configure UFW firewall, set up Fail2Ban, harden SSH, add monitoring, and everything I wish I'd known before starting. Each post is standalone — you can jump to whichever part you need. But if you're building from scratch, follow them in order. If you don't want to miss the next part, hit Follow. I'll also be sharing shorter tips and updates on Twitter/X (@ASkully58162) as I keep building. Have questions about the setup? Drop them in the comments — I'll answer everything and it might shape what I cover in the next parts. Got an old laptop collecting dust? It's about to become the most useful device you own. 🖥️ Templates let you quickly answer FAQs or store snippets for re-use. Hide child comments as well For further actions, you may consider blocking this person and/or reporting abuse