Building a Private Home Server Network with Tailscale

2026-09-13T00:00:00+00:00

When I tried setting up a homelab with a bunch of self-hosted services using Docker containers or otherwise, network access started becoming one of my biggest operational challenge. I needed to be able to manage these services from anywhere — whether that’s from another room in your house, a coffee shop, or halfway across the world — without exposing everything to the public internet.

That’s when I understood why every r/selfhosted or r/homelab subreddit I visited consider Tailscale to be one of the most GOAT-ed software service.

The Problem: Network Access Without Compromise

Before Tailscale, I had a few options:

Open ports on my router (terrible for security)
Use a traditional VPN (more setup overhead, performance trade-offs)
Only access services locally (too limiting)
Use individual reverse proxies for each service (complexity explosion)

None of these felt right for a personal infrastructure project. I wanted:

Easy remote access without managing firewall rules for every service
Point-to-point connections that didn’t require a centralized VPN server running 24/7
Seamless access to all my services under one cohesive network
A privacy-first approach where my traffic isn’t being routed through someone else’s servers unnecessarily

How Tailscale Fits My Stack

My homelab runs on Ubuntu with Docker, Home Assistant, and various other services. Tailscale sits at the network layer, creating a secure tunnel that lets me access everything as if I’m on the same local network.

The real win: every machine in my homelab — the main server, GPU machines, my development box — can be on the same private network without any of the traditional VPN complexity. When I connect from my laptop or phone, I’m part of that network too.

A Day in the Life

Here’s what this looks like in practice:

I’m away from home and want to check on a running service. I open my browser, connect to my Tailscale network, and access my internal dashboards exactly as if I were sitting at my desk at home.
I’m developing a feature that needs to talk to my self-hosted Ollama instance for testing. Through Tailscale’s MagicDNS, I just reference it by name, no IP juggling needed.
A new service needs debugging. I SSH into the machine using its Tailscale address, bypassing the need to configure port forwarding or expose SSH to the world.

Key Benefits I’ve Experienced

Privacy and Security: Tailscale uses WireGuard under the hood, which is modern, audited, and performant. My infrastructure doesn’t need to be exposed to the public internet at all. Everything stays private.

Simplicity: No complex firewall rules. No port forwarding nightmares. I define access once in Tailscale’s control plane, and it works consistently.

Point-to-Point Connections: Where possible, Tailscale establishes direct connections between devices. This means less latency and no central server bottleneck for the traffic.

MagicDNS: Instead of remembering IPs or managing /etc/hosts files, I can address machines by name. This especially helps when IPs might change or when I’m adding new devices.

Flexibility: Whether I’m on my home WiFi, at a coffee shop on public WiFi, or on a mobile hotspot, the experience is identical. My network is always available.

What I Don’t Expose

This setup has let me be more thoughtful about what actually needs public access:

Internal dashboards and monitoring tools stay private
SSH access is restricted to the Tailscale network
Development services don’t need reverse proxy configurations
No open ports for service access (only things like a public-facing web service if I choose to run one)

This is genuinely quieter from a security perspective. There’s no constant background noise of scanning attempts and exploitation probes aimed at random ports.

Is There a Cost? The Free Tier Reality

One of the best parts about Tailscale is that the free Personal plan is available indefinitely with no time limit. For my homelab use case, it covers everything I need.

The free tier includes up to 6 users, unlimited user devices, and 50 tagged resources. Let me break down what that actually means for a homelab:

User Devices (Unlimited): These are machines you personally own—your laptop, desktop, phone, tablet, etc. You can connect as many of these as you want to your Tailscale network at no cost. This is perfect for accessing your homelab from any of your devices.

Tagged Resources (50 included): These are servers, containers, and shared infrastructure pieces—the actual services in your homelab. With 50 tagged resources on the free tier, you have plenty of room. Even with Docker containers, a Kubernetes cluster, Home Assistant, Ollama, and various other services, I’m nowhere close to hitting that limit for a personal setup.

Users (6 included): The free tier lets you add up to 6 people to your network. For a solo homelab, this isn’t a constraint at all. If you want to grant a friend or family member access to something, you’ve got room for that too.

Additional Features: The free plan also includes access to nearly all Tailscale features, including SSH, Kubernetes features, MagicDNS, subnet routing, and exit nodes. You’re not missing out on core functionality.

When you might consider upgrading to a paid plan depends on your specific needs: more users on your network, more tagged resources, or advanced features like just-in-time access controls. But for a personal homelab, the free tier is genuinely generous.

The Tailscale Philosophy

What appeals to me about Tailscale is its approach: a private, personal network that you control, built on solid cryptographic foundations. It’s not trying to be everything—it’s laser-focused on being a reliable, performant way to connect your devices securely.

For a homelab, that focus is exactly what you want. Your infrastructure becomes a genuine private network, not a collection of exposed services behind ad-hoc security measures.

Next Steps

If you’re running a homelab and haven’t explored Tailscale yet, I’d suggest trying it out. Start with just accessing one service, get comfortable with the workflow, then expand from there.

The best part? Once it’s set up, it kind of disappears into the background and just works—which is exactly what you want from infrastructure.

Have you integrated Tailscale into your homelab setup? I’d be curious to hear how others are using it. Reach out if you’ve got questions or a different approach that’s worked well for you.

Hello, scrapbook

2026-08-27T00:00:00+00:00

This is the first entry. If you’re reading this on a public website, the whole chain worked: Zola built this from Markdown, and an nginx container is serving the static output.

I plan to document life experiences, things I’ve learned, and whatever I think others might find useful. Some content may be highly opinionated, both technically and socially — so be aware of that…

More to come….

Scrapbook for my thoughts